Re: [win-pv-devel] winpv drivers update still don't works correctly and domUs unable to boot on next reboot

[RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx>]

On 2015-10-23 16:49, Paul Durrant wrote:
>> -----Original Message-----
> [snip]
>>
>> I now retried with same domU when I had the latest problem reported (I
>> returned to status before the winpv update with disk snapshot), I
>> removed the winpv drivers from windows control panel (in this case I
>> didn't try additional manual clean) and reboot.
>> Next boot windows fails to boot and from qemu log winpv things are still
>> present and used but boot fails (I suppose because partial as uninstalled).
>> Full qemu log with trace in attachment.
>> Seems very strange that similar thing happen only to me and in 80-90% of
>> my tests with winpv, as already wrote tested on many domUs, W7/8/10,
>> different builds of winpv, different versions of dom0 kernel, xen, qemu
>> ecc...
>>
> 
> The XENVBD you have installed is missing this fix:
> 
> commit 59797d160517e47a249e67f030bb5d2943f8177a
> Author: Paul Durrant <paul.durrant@xxxxxxxxxx>
> Date:   Thu Sep 3 17:36:43 2015 +0100
> 
>     Clear unplug requests from co-installer
> 
>     When XENVBD is uninstalled there is no suitable notification in kernel
>     which can be used to clear any remaining unplug requests. This leads to
>     a certain 0x7B bugcheck on reboot. This patch therefore does the job
>     from the co-installer since this seems to be the only way.
> 
>     Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx>
> 
> This means, when you try to remove it, the unplug registry remains set. So, 
> to remove the old driver you have you will need to hack the registry manually 
> after removing the driver but before rebooting (or go into safe mode after 
> reboot). The thing you need to shoot is the "DISKS" value under 
> HKLM/System/CurrentControlset/Services/Xen/Unplug.
> BTW, it is expected that the XEN export driver and the XENFILT filter will 
> still re-load after boot even after removing all driver packages... Windows 
> never truly removes drivers. From the log though it looks like you've also 
> got an old XENBUS hanging around in DriverStore since XEN, XENFILT and XENBUS 
> now have a version of 8.1.0 and a date of 7th August so you should probably 
> do a 'pnputil -e' and then 'pnputil -d' on any remaining oemX.inf files you 
> find.
> 
>   Paul
> 
> 
Yeah, I'm doing all my testing on an image cloned from a "template" so
it's essentially fresh every time. It takes more time but ensures there
are no residues of some previous driver versions.

-- 
RafaÅ WojdyÅa
Qubes Tools for Windows developer
https://www.qubes-os.org/

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel