RE: [Xen-users] WinXP domU lockup

[Art Fore <art.fore@xxxxxxxxx>]

On Mon, 2006-11-06 at 14:25 +0100, Petersson, Mats wrote:
>  
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Art Fore
> > Sent: 06 November 2006 13:12
> > To: Steven Smith
> > Cc: xen-users@xxxxxxxxxxxxxxxxxxx; sos22@xxxxxxxxxxxxx
> > Subject: Re: [Xen-users] WinXP domU lockup
> > 
> > Here is all of the info in one email that I have been able to acquire.
> > If anyone has any other suggestions, please let me know. 
> > Tried figuring
> > out from the files, but no success. Seems as though another person on
> > the list has identical problem with Presario Pentium D.
> > 
> > Fowwlowing the instructions
> > http://www.xensource.com/files/xen_install_windows.pdf
> > 
> > During WinXP install, it gets to the Personalize your 
> > settings, I enter
> > by name, then lockup of domU.
> > 
> > This is Xen 3.0.3 with FC6 running 2.6.18xen kernel on Intel 
> > 2 core duo
> > 7600.
> > 
> > One thing in the pdf above, it says to set acpi=0. If I do 
> > this, Windows
> > does not even start. 
> 
> For "vcpus != 1" I expect ACPI to be necessary. For a single-cpu when
> installing, it should work fine with ACPI=0. 
> 
> 
> > 
> > The screen before the lockup where you enter time zone, etc, there are
> > two cursors, a white and block. The white, winxp, follows the black,
> > linux, but at variable distances. On the lockup screen, after entering
> > my name and it locks up (At least it does not lockup the whole machine
> > as in Suse 10.1) The windows cursor is frozen and no longer 
> > follows the
> > linux cursor. This is really strange. Any suggestions on what the
> > problem might be?
> > 
> > Here are the outputs from xm list, xm info and xm dmesg.
> > xm info
> > 
> > host : localhost.localdomain
> > release : 2.6.18-1.2798.fc6xen
> > version : #1 SMP Mon Oct 16 14:59:01 EDT 2006
> > machine : x86_64
> > nr_cpus : 2
> > nr_nodes : 1
> > sockets_per_node : 1
> > cores_per_socket : 2
> > threads_per_core : 1
> > cpu_mhz : 2327
> > hw_caps : 
> > bfebfbff:20000800:00000000:00000140:0000e3bd:00000000:00000001
> > total_memory : 2046
> > free_memory : 126
> > xen_major : 3
> > xen_minor : 0
> > xen_extra : .3-rc3-1.2798.f
> > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p 
> > hvm-3.0-x86_64
> > xen_pagesize : 4096
> > platform_params : virt_start=0xffff800000000000
> > xen_changeset : unavailable
> > cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)
> > cc_compile_by : brewbuilder
> > cc_compile_domain : build.redhat.com
> > cc_compile_date : Mon Oct 16 14:35:13 EDT 2006
> > xend_config_format : 2
> > 
> > xm list
> > 
> > Name                                      ID Mem(MiB) VCPUs State
> > Time(s)
> > Domain-0                                   0     1489     2 r-----
> > 741.0
> > winxp                                      4      500     2 ------
> > 386.2
> > 
> > xm dmesg
> > 
> > (XEN) (GUEST: 4) HVM Loader
> > (XEN) (GUEST: 4) Detected Xen v3.0.3-rc3-1.2798.f
> > (XEN) (GUEST: 4) Writing SMBIOS tables ...
> > (XEN) (GUEST: 4) Loading ROMBIOS ...
> > (XEN) (GUEST: 4) Creating MP tables ...
> > (XEN) (GUEST: 4) Loading Cirrus VGABIOS ...
> > (XEN) (GUEST: 4) Loading ACPI ...
> > (XEN) (GUEST: 4) Loading VMXAssist ...
> > (XEN) (GUEST: 4) VMX go ...
> > (XEN) (GUEST: 4) VMXAssist (Oct 17 2006)
> > (XEN) (GUEST: 4) Memory size 500 MB
> > (XEN) (GUEST: 4) E820 map:
> > (XEN) (GUEST: 4) 0000000000000000 - 000000000009F000 (RAM)
> > (XEN) (GUEST: 4) 000000000009F000 - 00000000000A0000 (Reserved)
> > (XEN) (GUEST: 4) 00000000000A0000 - 00000000000C0000 (Type 16)
> > (XEN) (GUEST: 4) 00000000000F0000 - 0000000000100000 (Reserved)
> > (XEN) (GUEST: 4) 0000000000100000 - 000000001F3F0000 (RAM)
> > (XEN) (GUEST: 4) 000000001F3F0000 - 000000001F3FA000 (ACPI Data)
> > (XEN) (GUEST: 4) 000000001F3FA000 - 000000001F3FD000 (ACPI NVS)
> > (XEN) (GUEST: 4) 000000001F3FD000 - 000000001F3FE000 (Type 19)
> > (XEN) (GUEST: 4) 000000001F3FE000 - 000000001F3FF000 (Type 18)
> > (XEN) (GUEST: 4) 000000001F3FF000 - 000000001F400000 (Type 17)
> > (XEN) (GUEST: 4) 00000000FEC00000 - 0000000100000000 (Type 16)
> > (XEN) (GUEST: 4) 
> > (XEN) (GUEST: 4) Start BIOS ...
> > (XEN) (GUEST: 4) Starting emulated 16-bit real-mode: ip=F000:FFF0
> > (XEN) (GUEST: 4)  rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
> > (XEN) (GUEST: 4) Remapping master: ICW2 0x8 -> 0x20
> > (XEN) (GUEST: 4) Remapping slave: ICW2 0x70 -> 0x28
> > (XEN) (GUEST: 4) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50
> > vruppert Exp $
> > (XEN) (GUEST: 4) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date:
> > 2005/05/07 15:55:26 $
> > (XEN) (GUEST: 4) 
> > (XEN) (GUEST: 4) ata0-0: PCHS=16383/16/63 translation=lba
> > LCHS=1024/255/63
> > (XEN) (GUEST: 4) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10200
> > MBytes)
> > (XEN) (GUEST: 4) ata0  slave: Unknown device
> > (XEN) (GUEST: 4) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
> > (XEN) (GUEST: 4) ata1  slave: Unknown device
> > (XEN) (GUEST: 4) 
> > (XEN) (GUEST: 4) Booting from CD-Rom...
> > (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
> > (XEN) This hvm_vlapic is for P4, no work for De-assert init
> > (XEN) This hvm_vlapic is for P4, no work for De-assert init
> > (XEN) (file=hvm.c, line=661) AP 1 bringup suceeded.
> > (XEN) vmx_do_launch(): GUEST_CR3<=00fd77a0, HOST_CR3<=6886d000
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate c1
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 53
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> > (XEN) (file=x86_emulate.c, line=1152) Cannot emulate 2b
> 
> Strange - there is a fix for 2B for xen/arch/x86/hvm/platform.c (which
> refers to HVM Windows XP SP2 in SMP PAE mode, but no such opcode in
> x86_emulate.c (at least not in unstable changeset 11884). The former is
> used for MMIO operations, the latter for page-table updates. Not sure if
> this is caused by some windows version difference or something else... 
> 
> You could try PAE=0 - that will prevent NX/XD mode of the OS from
> working, but it would be a good proof to see if it works or not...  
> 
Set vcpus to 1 and PAE to 0. No change. This all from starting with 
virt-manager. However, I cannot save machine, always have to dor File, New 
machine, and fillinallof the blanks again. Gets to be a real pain, but changing 
the winxp hvm file does affect it.
Also tried acpi=0, etc, it does not like that at all.

When I try to execute xm create winxp, it starts up, then gets to a
point and asks to please install GLOBAL/DEVICES/CDROM. Even setting the
"cdrom='/dev/hdc'" or "cdrom='/media/VX2PFPP'" where the auto mounter
mounts it, it still cannot find it. (cat /dev/hdc starts the cdrom to
spinning and puts giberish on the screen) 

If I change vnc and vncunused to 0 and sdl to 1, the windows screen
comes up much faster than with the vnc, and windows runs about 10 times
faster, up until it cannot find the cdrom.

Went to bed, then had some thoughts, got up and tried them.
In the above condition, executing xm dmesg, the
(XEN) (GUEST: 4) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 4) ata1  slave: Unknown device 
do not show up.

If I modify the disk = [ 'file:/home/afore/VM_images/WinXP,hda,w', ]
to disk = [ 'file:/home/afore/VM_images/WinXP,hda,w', ',hdc:cdrom,r'] and
remove the cdrom='/dev/hdc, windows then has a message about inserting
the winxp disk, so at least it is finding it, but cannot read it.
xm dmesg then shows the
(XEN) (GUEST: 4) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 4) ata1  slave: Unknown device 
again.

Art

> > 
> > Here is the hvm file the virt-manager made. Also tried with vcpus=1,
> > same thing. Also tried with apic=0, then nothing works. Tried with
> > acpi=0, also nothing works.
> 
> --
> Mats
> > 
> > # Automatically generated xen config file
> > name = "winxp"
> > builder = "hvm"
> > memory = "500"
> > disk = [ 'file:/home/afore/VM_images/WinXP,hda,w', ]
> > vif = [ 'type=ioemu, mac=00:16:3e:5d:4e:3f, bridge=xenbr0', ]
> > uuid = "f9060b49-92c7-1038-d13c-0a050d480475"
> > device_model = "/usr/lib64/xen/bin/qemu-dm"
> > kernel = "/usr/lib/xen/boot/hvmloader"
> > vnc=1
> > vncunused=1
> > apic=1
> > acpi=1
> > pae=1
> > vcpus=2
> > serial = "pty" # enable serial console
> > on_reboot   = 'restart'
> > on_crash    = 'restart'
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> > 
> > 
> > 
> 
> 


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users