Re: [Qemu-devel] qemu 1.3: windows 2003 SP2 x64 boot crash with hpet enabled (was ok with qemu-kvm 1.2)

[Jason Baron <jbaron@redhat.com>]

On Tue, Dec 11, 2012 at 08:02:12AM +0100, Alexandre DERUMIER wrote:
> seem to be related to seabios update:
> 
> seabios: q35 update
> http://lists.gnu.org/archive/html/qemu-devel/2012-12/msg00113.html
> 

This is most likely due to SeaBIOS commit:

commit d9f5cdbdf55d61aef9a1a534d9123ef734427478

Which I believe was pulled into qemu-1.3, so that probably explains why
you are seeing this on 1.3.

SeaBIOS recently committed a fix (revert) for this. So, if its possible to pull
the latest SeaBIOS, and pass -bios <seabios patch>/bios.bin. We can
verify that.

Thanks,

-Jason



> 
> 
> ----- Mail original -----
> 
> De: "Alexandre DERUMIER" <aderumier@odiso.com>
> À: "qemu-devel" <qemu-devel@nongnu.org>
> Envoyé: Mardi 11 Décembre 2012 07:30:58
> Objet: Re: [Qemu-devel] qemu 1.3: windows 2003 SP2 x64 boot crash with hpet enabled (was ok with qemu-kvm 1.2)
> 
> My bsod screenshot was not full, here a new one:
> 
> this seem to hang on acpi.sys
> 
> ACPI.SYS address F735EE64 base at F7352000)
> 
> I have tested xith host kernel 3.2,26,27 and 2.6.32 from rhel6, same problem.
> 
> 
> 
> ----- Mail original -----
> 
> De: "Alexandre DERUMIER" <aderumier@odiso.com>
> À: "qemu-devel" <qemu-devel@nongnu.org>
> Envoyé: Lundi 10 Décembre 2012 19:08:37
> Objet: [Qemu-devel] qemu 1.3: windows 2003 SP2 R2 x64 boot crash with hpet enabled (was ok with qemu-kvm 1.2)
> 
> Hi list,
> 
> I have a bsod when booting windows 2003 SP2 R2 x64 with hpet enabled, with qemu 1.3. (screenshot attached)
> 
> /usr/bin/kvm -id 99999 -chardev socket,id=qmp,path=/var/run/qemu-server/99999.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/99999.vnc,x509,password -pidfile /var/run/qemu-server/99999.pid -daemonize -name win2003-32bit-proxmox2 -smp sockets=2,cores=1 -nodefaults -boot menu=on -vga cirrus -k fr -m 4000 -usbdevice tablet -drive if=none,id=drive-ide2,media=cdrom,aio=native -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -drive file=/dev/disk/by-id/scsi-3600144f0f62f0e0000004f6ec6fe00ba,if=none,id=drive-virtio0,aio=native,cache=none -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -netdev type=tap,id=net0,ifname=tap99999i0,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=BA:BD:4F:AE:DF:FD,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -netdev type=tap,id=net1,ifname=tap99999i1,script=/var/lib/qemu-server/pve-bridge,vhost=on -device virtio-net-pci,mac=4E:68:E9:4B:57:7C,netdev=net1,bus=pci.0,addr=0x13,id=net1,bootindex=301 -rtc driftfix=slew,base=localtime
> 
> 
> it's booting fine with adding -no-hpet to above command line.
> 
> 
> above command line works fine with qemu-kvm 1.2.
> 
> 
> One proxmox user report also win2003 R2 SP2 X32 high cpu usage with smp guest and hpet enabled. (qemu-kvm 1.2 or qemu 1.3)
> 
> 
> Maybe it's in-kernel irqchip related ?
> 
> Any advise about enabling or disabling hpet on win2003 with in-kernel irqchip.
> 
> 
> Best Regards,
> 
> Alexandre