Description of problem: When installing WinXP 32bit HVM, the installer hangs when it goes to start Windows; xentop shows the domain running, but it's using 0% cpu, and can't be connected to. If, at the begining of the install, I press 'F5', I can select 'Standard PC with C-Step i486', (or something similar referencing i486), and the installation continues just fine. Version-Release number of selected component (if applicable): Not sure where this lies; perhaps in the qemu-dm portion of xen. Here's the details that may be relevant: - xen-3.0.3-8.el5 - kernel-xen-2.6.18-1.2747.el5 Hardware: - Dell Optiplex 745 w/ Core-Duo, 4G ram, onboard Intel video How reproducible: 100% for me. :-/ Steps to Reproduce: 1. Use any given tool (virt-install, virt-manager) to start a Win XP install 2. I used an LVM logical volume and iso file, 512M ram, 1 VCPU Actual results: When the installer went to start windows, it hung Expected results: A normal install Additional info: Note that in beta testing of XenEnterprise 3.1.0 on the same hardware, I didn't need to use this workaround.
Is the same workaround required for the XS 3.0.3 release?
It looks like the RHEL5 xen build uses the XS 3.0.3 tarball, not sure what you'd like me to test. I took a look at the xen version shipped w/ XenEnt. 3.1.0 beta, which appears to be a couple of weeks newer. What I might do is try rebuilding the RHEL5 rpm with the newer tarball.
The bits we ship are based on 3.0.3, but forward ported to 2.6.18. The question was wrt behavior being identical to the upstream 2.6.16 3.0.3 vs. our build.
Ok, it doesn't look like I'll be able to test this: - I tried the XS rpms on RHEL5b2; after pounding them in with a large mallet, xm create WinXP always fails with 'Error: Device 768 (vbd) couldn not be connected. Hotplug scripts not working.' - I tried to start a RHEL4 install on that box, but as soon as the kernel loads, it sets a display mode that the Dell 1907FP LCD doesn't like. Sorry. Just FYI - I'm otherwise very happy with RHEL5 xen; I've had good success w/ RHEL5, FC6 & RHEL4 PV's (converted from HVM w/ packages from jbaron). That's what we'll be using for production servers anyway.
Could you please try with the xen-3.0.3-8.el5.0.1.sct packages from http://people.redhat.com/sct/packages/xen/ please? That includes a fix for bootup which might well impact the XP install.
Thanks, I'll try these Monday when I return to the office. Happy Thanksgiving.
Ok, I tried the sct packages; no joy. Symptoms the same - I run the XP installer, it copies all the files, and then reboots. The SDL screen changes shape as if XP is setting boot resolution. Whenever I run 'xm create WinXP', I get a /var/log/xen/qemu-dm.$PID.log; e.g: <log> domid: 4 qemu: the number of cpus is 1 shared page at pfn:1ffff, mfn: 97c7e buffered io page at pfn:1fffd, mfn: 97c80 xs_read(): vncpasswd get error. /vm/49092b73-6bc9-3f7d-3b13-25f399d7ea9e/vncpasswd. False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0 </log> The end of 'xm dmesg' looks like this: <log> (XEN) (GUEST: 4) Booting from Hard Disk... (XEN) (GUEST: 4) unsupported PCI BIOS function 0x0E (XEN) (GUEST: 4) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) (GUEST: 4) *** int 15h function AX=E980, BX=00F2 not yet supported! (XEN) hvm_vioapic_write_indirect: version register read only (XEN) hvm_vioapic_write_indirect: version register read only (XEN) hvm_vioapic_write_indirect: version register read only (XEN) This hvm_vlapic is for P4, no work for De-assert init </log> Let me know if you want any other debugging output.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
(In reply to comment #7) Could you retry the install with RHEL5-GA and report back findings. TIA.
Using virt-manager and a standard winxp-pro CD it won't install with the RHEL5-GA release. It appears to hang in the same place indicated above.
Confirmed to be fixed in 5.1, so setting to MODIFIED. Chris Lalancette
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2007-0635.html