Bugzilla – Bug 564427
xen kernel crash when using GPLPV driver on Windows 2003 guest and physical partition
Last modified: 2009-12-15 10:45:26 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 I have an odd problem, but, easy to replicate. Xen 3.4 + GPLPV + Windows 2003 (x32) guest. I've tried this on both GPLPV 0.10.0.138 and 0.10.0.142 drivers. If the hard drive is an image file using the file: directive in the xen config file, Windows 2003 guest boots and runs great with the GPLPV drivers. If the hard drive is a physical drive or partition using the phy: directive in the xen config file, Windows 2003 guest boots and runs fine with the QEMU drivers. If the hard drive is a physical drive or partition using the phy: directive in the xen config gile, Windows 2003 guest boots and runs with the GPLPV drivers for about 3-5 minutes. At the time, the entire machine locks up and I have to power cycle machine to recover (no mouse, or keyboard response). I even took the crashed Windows 2003 partition, dd copied to a file, setup xen to point to the image file using the file: directive. The Windows 2003 guest came up with the GPLPV drivers and ran great. Reproducible: Always Steps to Reproduce: 1. Run Xen 2. Load Windows 2003 guest as phy: device. 3. Load GPLPV 0.10.0.142 drivers on Windows guest. 4. Reboot Windows guest. 5. Do some disk activities in Windows 2003 (like error checking or defragment). 6. After 3-5 minutes, the Xen and entire computer locks up. Actual Results: The computer locked up. Expected Results: The computer should run without locking up.
Does the same also happen with file:/ backed disks? Also, we'll need the full kernel log in order to determine whether this is simply a duplicate of several other bugs that got reported earlier.
Created attachment 332511 [details] log file
This does not happen when I use file: images stored on the Linux drive.
(In reply to comment #2) > Created an attachment (id=332511) [details] > log file This doesn't help, as it doesn't include any indication on the reasons for the crash. But this (In reply to comment #3) > This does not happen when I use file: images stored on the Linux drive. makes it rather certain that this is a duplicate. *** This bug has been marked as a duplicate of bug 553690 ***