Bug 198431 - Fedora Core 6 - Test 1 - Windows XP Guest Install Hangs
Summary: Fedora Core 6 - Test 1 - Windows XP Guest Install Hangs
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 6
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-11 12:13 UTC by andrew78
Modified: 2008-08-02 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-08 22:48:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.