[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] WinPV BSOD on Win2008R2

  • To: "'Peter Gansterer'" <peter.gansterer@xxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxxx>
  • From: "Nathan March" <nathan@xxxxxx>
  • Date: Wed, 12 Oct 2016 10:19:54 -0700
  • Delivery-date: Wed, 12 Oct 2016 17:21:24 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=ztghuY/g77dHV1hcjiv wTST7CU0taBo5C7pzO9/TzaAI9KZwuPLnmjtobKXfkdPg9ucZp82LpJcK/eO4mwj kkt8qAjdjcIbTCvaIuUw3tVG39OA4/rTiOtSmcCr8mcsY3uGplXpCL1ph2u44XrE kUjpkmoy5CfL7B7TTopXadqo=
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Thread-index: AQIF0XmYUU//GEsaPBORY3/M1cvuq6A9tMUQ

My upgrade procedure:

1. Uninstall all EJB + xen drivers via uninstall, DO NOT REBOOT
2. Run uninstall.bat, DO NOT REBOOT
3. Install the new ones, then you can reboot
4. Make sure device manager shows the xen nic and not the emulated realtek 
(depends if your config has vif emulation turned on or not). If realtek, 
unisntall the device in device manager, and reboot

This has worked almost flawlessly on a couple dozen machines ranging from 2003 
- 2012, although I did once have to clean up some registry entries manually. 
Unfortunately I can't find where I saved the path, but try the above and if 
you're still stuck let me know and I can dig it up for you.

- Nathan

> -----Original Message-----
> From: Xen-users [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Peter
> Gansterer
> Sent: Sunday, October 9, 2016 9:46 AM
> To: xen-users@xxxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] WinPV BSOD on Win2008R2
> Hi,
> I am desperately trying to "convert" a gplpv'ed Win2008R2 domU to winpv
> 8.1.0 with no success so far.
> (Xen 4.7 on gentoo, qemu 2.4.1)
> What I do:
> - (take an LVM snapshot)
> - uninstall gplpv driver (2 steps: uninstall via windows, then uninstall.bat)
> - reboot
> - reboot again (changes were made)
> - cleanup "HKLM/System/CurrentControlSet" using:
>   psexec -i -d -s c:\windows\regedit.exe
>   -> remove all traces of xen
> - reboot
> The system is stable at this point. I reboot a few times to make sure I didn't
> miss anything.
> (tested Disk and Net IO, no crashes)
> Then I install winpv drivers:
> - When I install all drivers, it _usually_ crashes upon reboot (first or 
> second)
> - When I omit Net & VIF, it lasts longer (last time it was until machine
> recreation, but I can't tell for sure)
> BSOD on boot is always "Stop: 0x1E (0,0,0,0)"
> A few days ago I did some extensive "reboot testing":
> - once crashed, it continues crashing
> - safe mode usually works
> - Removing the Xen PV NIC _usually_ makes the next boot possible
> - When booted, the NIC doesn't work in _most cases_
> (As you can see, I couldn't find reliable patterns)
> For comparison I set up a new win2008 with current updates.
> Installing and running winpv works fine there!
> When comparing the registries I saw a difference in
> HKLM/System/CCS/Enum/PCI/VEN_5853*:
> - The stable domU has 2 Entries there (ending on &18 and &10).
> - The unstable domU has only 1 Entry (ending on &10).
> I am attaching the xl.cfg and the dm logfile (this is a boot to BSOD with
> bus/interface/vbd installed).
> I would appreciate any hints how I can get this running...
> - peter.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.