From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: windows 2008 "falling asleep" under KVM Date: Thu, 11 Jul 2013 16:44:44 +0300 Message-ID: <20130711134444.GN8575@redhat.com> References: <20130711112348.GA28871@pcnci.linuxbox.cz> <20130711124437.GL8575@redhat.com> <20130711130619.GR8440@pcnci.linuxbox.cz> <20130711131952.GM8575@redhat.com> <20130711133120.GS8440@pcnci.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT Cc: KVM list To: Nikola Ciprich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55352 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755123Ab3GKNor convert rfc822-to-8bit (ORCPT ); Thu, 11 Jul 2013 09:44:47 -0400 Content-Disposition: inline In-Reply-To: <20130711133120.GS8440@pcnci.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Jul 11, 2013 at 03:31:20PM +0200, Nikola Ciprich wrote: > > 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,v hostfd=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 > This is cirrus, not qxl. This makes my S3 theory to be highly unlikely. -- Gleb.