Bug 198431

Summary:	Fedora Core 6 - Test 1 - Windows XP Guest Install Hangs
Product:	[Fedora] Fedora	Reporter:	andrew78 <alseat>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	bstein, katzj
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-03-08 22:48:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description andrew78 2006-07-11 12:13:15 UTC

Description of problem:

I'm running Fedora Core 6 - Update 1 and trying to install a Windows XP Pro VT
guest.  The install of the Windows XP guest starts normally but after the
drivers load, I get the message "Setup is Starting Windows".  I get nothing
after this no matter how long I wait.  A xm-list shows the VT guest is gainining
cpu time rapidly so if must be in a infinite loop.  I have installed several FC6
VT guest and that works great.  The Windows XP VT guest is the only problems I'm
having.


Version-Release number of selected component (if applicable):
xen is xen-3.0.2.10
kernel is kernel-xen-2.6.16-1.2289_FC6

How reproducible:


Steps to Reproduce:
1. Attemp to install a Windows Xp VT guest from either CD or a disk image file.
2. Use VNC as the console for the Window XP guest install
3.
  
Actual results:
Successful install of Windows XP Pro VT guest

Expected results:
Install of Windwosn XP PRO guest loops after "setup is starting Windows" message

Additional info:
My platform is a Dell 380N platorm with dual-core 3.0 MHz processors and VT support.

Comment 1 Brian Stein 2006-10-09 15:19:08 UTC

Please confirm this issue still exists with rawhide.

Comment 2 Stephen Tweedie 2007-03-08 22:48:38 UTC

Closed for lack of response; please reopen if the bug can still be confirmed.