> AFAIK this is default Windows2008 behaviour in case S3 is supported by > the platform. But KVM supports S3 for Windows2008 guests only with QXL > display, so this raises the question: what is qemu command line on > the machine that it happens to and on the host where it does not happen. machine with the problem: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name vmtop09 -S -machine pc-i440fx-1.4,accel=kvm,usb=off -m 4096 -smp 1,sockets=1,cores=1,threads=1 -uuid 1a858074-e30d-11e2-b1d7-002590968776 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmtop09.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-hpet -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vgshared/vmtop09-1,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=18,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:16:3e:18:09:00,bus=pci.0,addr=0x3 -device usb-tablet,id=input0 -vnc 0.0.0.0:24109 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 macine without the problem: (please note that there's currently newer qemu there, but it was OK even with 1.4.0) /usr/bin/qemu-system-x86_64 -machine accel=kvm -name vmwts02 -S -machine pc-i440fx-1.5,accel=kvm,usb=off -m 4096 -smp 1,sockets=1,cores=1,threads=1 -uuid 1e501300-dc48-11df-a690-00304834195b -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vmwts02.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vgshared/vmwts02-1,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,cache=none -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=27,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:16:3e:61:01:00,bus=pci.0,addr=0x3 -device usb-tablet,id=input0 -vnc 0.0.0.0:30802 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 > That does look like S3 suspend. Can you run "info status" command on > qemu monitor when it happens? I'll check, however I don't have it in this state atm, so I'll report in few hours.. BR nik > > > -- > Gleb. > -- ------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28.rijna 168, 709 00 Ostrava tel.: +420 591 166 214 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@xxxxxxxxxxx -------------------------------------
Attachment:
pgp9B8owc00LM.pgp
Description: PGP signature
