windows 2008 "falling asleep" under KVM

windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 922 bytes --]

Hello,

I'm trying to solve strange issue with windows2008 VM under KVM.
It seems to be somehow "falling asleep" after some time, becoming unreachable
over network. However connecting to qemu VNC immediately makes windows
reachable again...

I wonder whether this is the same issue? 

http://lists.nongnu.org/archive/html/qemu-devel/2013-03/msg02278.html

I've tried disabling HPET, same result. I'm using qemu-kvm 1.4.0, seabios
1.7.2.2, kernel 3.0.82 with kvm-kmod-3.8, x86_64 centos6.

Any idea what should I check?

Thanks a lot in advance

with best regards

nikola ciprich

-- 
-------------------------------------
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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Thu, Jul 11, 2013 at 01:23:48PM +0200, Nikola Ciprich wrote:
> Hello,
> 
> I'm trying to solve strange issue with windows2008 VM under KVM.
> It seems to be somehow "falling asleep" after some time, becoming unreachable
> over network. However connecting to qemu VNC immediately makes windows
> reachable again...
> 
> I wonder whether this is the same issue? 
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2013-03/msg02278.html
> 
> I've tried disabling HPET, same result. I'm using qemu-kvm 1.4.0, seabios
> 1.7.2.2, kernel 3.0.82 with kvm-kmod-3.8, x86_64 centos6.
> 
> Any idea what should I check?
> 
> Thanks a lot in advance
> 
Is Window configured to suspend itself after a timeout?

--
			Gleb.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

Hello Gleb,

well, I'm not windows expert at all, but it  shouldn't be.
same instalation on different host works without problem...
what could be worth noting is that CPU usage of qemu process drops
to zero when this happens, otherwise windows guests eat quite a lot
of CPU time even when "idle". Maybe I should somehow check what the
process is doing? (how?)

BR

nik


> Is Window configured to suspend itself after a timeout?
> 
> --
> 			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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Thu, Jul 11, 2013 at 03:06:19PM +0200, Nikola Ciprich wrote:
> Hello Gleb,
> 
> well, I'm not windows expert at all, but it  shouldn't be.
> same instalation on different host works without problem...
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.

> what could be worth noting is that CPU usage of qemu process drops
> to zero when this happens, otherwise windows guests eat quite a lot
> of CPU time even when "idle". Maybe I should somehow check what the
> process is doing? (how?)
That does look like S3 suspend. Can you run "info status" command on
qemu monitor when it happens?


--
			Gleb.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]

> 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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

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.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

> This is cirrus, not qxl. This makes my S3 theory to be highly unlikely.

OK, finally I got it hung again:

virsh # qemu-monitor-command vmtop09 --hmp "info status"
VM status: running

nik


> 
> --
> 			Gleb.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Fri, Jul 12, 2013 at 02:08:31PM +0200, Nikola Ciprich wrote:
> > This is cirrus, not qxl. This makes my S3 theory to be highly unlikely.
> 
> OK, finally I got it hung again:
> 
> virsh # qemu-monitor-command vmtop09 --hmp "info status"
> VM status: running
> 
So confirmed, this is not S3, but still possible that Windows disabled
the device to save power. Can you try do the following steps and see if
it helps (they are for windows 7 but 8 should be similar)

Disable device powersave:
- Control Panel -> Network & Internet -> Network Connections
- Right-click on desired interface, and select "Properties"
- Click the "Configure" button on the interface properties
- Under the "Advanced" tab, look for power-saving related options and
  set to "Disabled"
- Under the "Power Management" tab, uncheck "Allow computer to turn off
  this device to save power"
- Save & Reboot

In addition:
- Control Panel -> Hardware & Sound -> Power Options
- Select "High performance"
- By the selected power profile, select "Change Plan Settings"
- In the "Edit Plan Settings", select "Change advanced power settings"
- See if there is something relevant to network connection there and if
  yes change it to not sleep
- Save & Reboot


--
			Gleb.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

Hello Gleb,

please note, it's windows 2008, not windows8, not sure whether there's
some significant difference, though..

> Disable device powersave:
> - Control Panel -> Network & Internet -> Network Connections
> - Right-click on desired interface, and select "Properties"
> - Click the "Configure" button on the interface properties
> - Under the "Advanced" tab, look for power-saving related options and
>   set to "Disabled"
> - Under the "Power Management" tab, uncheck "Allow computer to turn off
>   this device to save power"
> - Save & Reboot

I forgot to mention that, I'm using virtio network driver, and it
doesn't seem to support any power managemt (which is not surprising
I guess)


> 
> In addition:
> - Control Panel -> Hardware & Sound -> Power Options
there's no sound card there..

> - Select "High performance"
done already.

> - By the selected power profile, select "Change Plan Settings"
> - In the "Edit Plan Settings", select "Change advanced power settings"
> - See if there is something relevant to network connection there and if
>   yes change it to not sleep
everything was already disabled...
> - Save & Reboot


maybe I should try using realtek network device instead of virtio?

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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Mon, Jul 15, 2013 at 10:56:41AM +0200, Nikola Ciprich wrote:
> Hello Gleb,
> 
> please note, it's windows 2008, not windows8, not sure whether there's
> some significant difference, though..
> 
Heh, indeed. I wonder where I get this windows8 thing from. Windows 2008
is a server OS so much less tuned to save power, so probably it is not
power related after all.

> > Disable device powersave:
> > - Control Panel -> Network & Internet -> Network Connections
> > - Right-click on desired interface, and select "Properties"
> > - Click the "Configure" button on the interface properties
> > - Under the "Advanced" tab, look for power-saving related options and
> >   set to "Disabled"
> > - Under the "Power Management" tab, uncheck "Allow computer to turn off
> >   this device to save power"
> > - Save & Reboot
> 
> I forgot to mention that, I'm using virtio network driver, and it
> doesn't seem to support any power managemt (which is not surprising
> I guess)
> 
> 
> > 
> > In addition:
> > - Control Panel -> Hardware & Sound -> Power Options
> there's no sound card there..
It is sound and _hardware_ not sure why MS separated sound from HW :)

> 
> > - Select "High performance"
> done already.
> 
> > - By the selected power profile, select "Change Plan Settings"
> > - In the "Edit Plan Settings", select "Change advanced power settings"
> > - See if there is something relevant to network connection there and if
> >   yes change it to not sleep
> everything was already disabled...
> > - Save & Reboot
> 
> 
> maybe I should try using realtek network device instead of virtio?
> 
Try it and see if it changes anything. When you say it becomes
unreachable over network what does it mean? Network share disappears or
you could ping it before but cannot any more?

--
			Gleb.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hi,

> It is sound and _hardware_ not sure why MS separated sound from HW :)
OK, I'll check it

> Try it and see if it changes anything. When you say it becomes
> unreachable over network what does it mean? Network share disappears or
> you could ping it before but cannot any more?
OK, I'll report the results. unreachable means I'm not even able to ping it
unless I open VNC connection which causes "waking" the machine..

we'll see whether changing network device changes something..

so far thanks for Your time!

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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Peter Kieser]

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

Does the host system support constant_tsc? Check /proc/cpuinfo. It could 
be that too many ticks are being lost in the guest.

-Peter

On 2013-07-15 4:54 AM, Nikola Ciprich wrote:
> Hi,
>
>> It is sound and _hardware_ not sure why MS separated sound from HW :)
> OK, I'll check it
>
>> Try it and see if it changes anything. When you say it becomes
>> unreachable over network what does it mean? Network share disappears or
>> you could ping it before but cannot any more?
> OK, I'll report the results. unreachable means I'm not even able to ping it
> unless I open VNC connection which causes "waking" the machine..
>
> we'll see whether changing network device changes something..
>
> so far thanks for Your time!
>
> BR
>
> nik
>
>
>> --
>> 			Gleb.
>>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Wed, Jul 17, 2013 at 07:22:38PM -0700, Peter Kieser wrote:
> Does the host system support constant_tsc? Check /proc/cpuinfo. It
> could be that too many ticks are being lost in the guest.
> 
Window2008 will not use TSC as a time source while running as a guest.

> -Peter
> 
> On 2013-07-15 4:54 AM, Nikola Ciprich wrote:
> >Hi,
> >
> >>It is sound and _hardware_ not sure why MS separated sound from HW :)
> >OK, I'll check it
> >
> >>Try it and see if it changes anything. When you say it becomes
> >>unreachable over network what does it mean? Network share disappears or
> >>you could ping it before but cannot any more?
> >OK, I'll report the results. unreachable means I'm not even able to ping it
> >unless I open VNC connection which causes "waking" the machine..
> >
> >we'll see whether changing network device changes something..
> >
> >so far thanks for Your time!
> >
> >BR
> >
> >nik
> >
> >
> >>--
> >>			Gleb.
> >>
> 
> 



--
			Gleb.

Re: windows 2008 "falling asleep" under KVM

[Nikola Ciprich]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

Hi,

just to let You know, with realtek instead of virtio-net, it seems
to be reachable for almost three days.. I'd give it another day, then we
can be pretty sure it's virtio related...

BR

nik

-- 
-------------------------------------
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@linuxbox.cz
-------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: windows 2008 "falling asleep" under KVM

[Gleb Natapov]

On Thu, Jul 18, 2013 at 08:55:25AM +0200, Nikola Ciprich wrote:
> Hi,
> 
> just to let You know, with realtek instead of virtio-net, it seems
> to be reachable for almost three days.. I'd give it another day, then we
> can be pretty sure it's virtio related...
> 
Thanks. Interesting. Copying virtio-net expert.

--
			Gleb.