http://bugzilla.novell.com/show_bug.cgi?id=564427 http://bugzilla.novell.com/show_bug.cgi?id=564427#c0 Summary: xen kernel crash when using GPLPV driver on Windows 2003 guest and physical partition Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas@novell.com ReportedBy: kcobler@coblercorp.com QAContact: qa@suse.de Found By: --- Blocker: --- 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. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.