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

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       win-pv-devel
Subject:    Re: [win-pv-devel] winpv drivers update still don't works correctly and domUs unable to boot on next
From:       Fabio Fantoni <fabio.fantoni () m2r ! biz>
Date:       2015-10-26 10:06:47
Message-ID: 562DFB37.1010903 () m2r ! biz
[Download RAW message or body]

Il 23/10/2015 16:49, Paul Durrant ha scritto:
> > -----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@citrix.com>
> 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@citrix.com>
> 
> 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.

I suppose this is the mainly problem :(
I tried the winpv remove on domU created only one week ago and still 
boot correctly after drivers uninstall from windows control panel and 
reboot.
After I also tried to install the latest build and on reboot is still 
working and seems that use all newer components in this case.
Big thanks for all your work.
I suppose that update should be never used and remove->reboot->new 
install is the only options, is it right?
About complete and safe winpv remove I suppose is not possible and I 
must "delete and recreate" any domUs with older winpv builds, is it right?

> 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.

I also tried pnputil many times, long time ago was useful but in latest 
months never showed winpv drivers after uninstall from control panel 
even if was still present in registry, windows folder and in trace after 
reboot (and in many cases with domUs not bootable).

> 
> Paul
> 
> 
> > If you need more informations/tests tell me and I'll post them.
> > 
> > Thanks for any reply and sorry for my bad english.
> > 
> > > > > > > In my latest test:
> > > > > > > Dom0:
> > > > > > > Wheezy (debian 7) 64 bit with xen 4.6.0 plus some small additional
> > > > > patches:
> > > > > > > https://github.com/Fantu/Xen/commits/rebase/m2r-testing-4.6
> > > > > > > kernel is custom build of 4.1.8 with .config in attachment
> > > > > > > Qemu 2.4 with some small additional patches:
> > > > > > > https://github.com/Fantu/qemu/commits/rebase/upstream
> > > > > > > Seabios 1.8.2
> > > > > > > 
> > > > > > > DomU:
> > > > > > > windows 10 pro 64 bit
> > > > > > > xl cfg in attachment
> > > > > > > 
> > > > > > > I updated all winpv components to latest build without saw errors
> > > > > > > but on
> > > > > > > reboot windows fails to boot, in qemu log I saw a trace about and
> > > > > > > also
> > > > > > > the still use older build of at least one component.
> > > > > > > Full qemu log with trace in attachment.
> > > > > > > I had similar problem many time with different versions of xen, qemu,
> > > > > > > seabios, winpv, windows ecc...
> > > > > > > I also already did at least one other report about time ago if I
> > > > > > > remember good.
> > > > > > > 
> > > > > > > 
> > > > > > > If you need more informations/tests tell me and I'll post them.
> > > > > > > 
> > > > > > > Thanks for any reply and sorry for my bad english.
> > > > > > > 

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

[prev in list] [next in list] [prev in thread] [next in thread] 