KVM (Windows) Backup in stop mode

giner

Member
Oct 14, 2009
239
0
16
41
Tokyo
Hello everybody,

I have a problem with backup in stop mode. Windows XP and 2003 hangs on stop. By the way shutdowning machine from the web interface works only if I press shutdown twise (press one time and later press again). Linux in KVM and OpenVZ works perfectly.

Log Windows 2003:
Oct 14 02:00:01 INFO: Starting Backup of VM 101 (qemu)
Oct 14 02:00:01 INFO: status = running
Oct 14 02:00:02 INFO: starting first sync /var/lib/vz/images/101 to /var/tmp/vzdumptmp6374
Oct 14 03:42:15 INFO: Number of files: 3
Oct 14 03:42:15 INFO: Number of files transferred: 2
Oct 14 03:42:15 INFO: Total file size: 58161405952 bytes
Oct 14 03:42:15 INFO: Total transferred file size: 58161405952 bytes
Oct 14 03:42:15 INFO: Literal data: 58161405952 bytes
Oct 14 03:42:15 INFO: Matched data: 0 bytes
Oct 14 03:42:15 INFO: File list size: 72
Oct 14 03:42:15 INFO: File list generation time: 0.001 seconds
Oct 14 03:42:15 INFO: File list transfer time: 0.000 seconds
Oct 14 03:42:15 INFO: Total bytes sent: 58168505903
Oct 14 03:42:15 INFO: Total bytes received: 54
Oct 14 03:42:15 INFO: sent 58168505903 bytes received 54 bytes 9483737.83 bytes/sec
Oct 14 03:42:15 INFO: total size is 58161405952 speedup is 1.00
Oct 14 03:42:15 INFO: first sync finished (6133 seconds)
Oct 14 03:42:15 INFO: stopping vps
Oct 14 03:52:15 INFO: wait failed - got timeout
Oct 14 03:53:38 ERROR: Backup of VM 101 failed - command 'qm shutdown 101 && qm wait 101 600' failed with exit code 255

Log Windows XP:
Oct 14 04:20:02 INFO: Starting Backup of VM 103 (qemu)
Oct 14 04:20:03 INFO: status = running
Oct 14 04:20:03 INFO: starting first sync /var/lib/vz/images/103 to /var/tmp/vzdumptmp6374
Oct 14 04:23:01 INFO: Number of files: 2
Oct 14 04:23:01 INFO: Number of files transferred: 1
Oct 14 04:23:01 INFO: Total file size: 1705930752 bytes
Oct 14 04:23:01 INFO: Total transferred file size: 1705930752 bytes
Oct 14 04:23:01 INFO: Literal data: 1705930752 bytes
Oct 14 04:23:01 INFO: Matched data: 0 bytes
Oct 14 04:23:01 INFO: File list size: 56
Oct 14 04:23:01 INFO: File list generation time: 0.001 seconds
Oct 14 04:23:01 INFO: File list transfer time: 0.000 seconds
Oct 14 04:23:01 INFO: Total bytes sent: 1706139108
Oct 14 04:23:01 INFO: Total bytes received: 35
Oct 14 04:23:01 INFO: sent 1706139108 bytes received 35 bytes 9558202.48 bytes/sec
Oct 14 04:23:01 INFO: total size is 1705930752 speedup is 1.00
Oct 14 04:23:01 INFO: first sync finished (178 seconds)
Oct 14 04:23:01 INFO: stopping vps
Oct 14 04:33:01 INFO: wait failed - got timeout
Oct 14 04:33:02 ERROR: Backup of VM 103 failed - command 'qm shutdown 103 && qm wait 103 600' failed with exit code 255

Cheers,
Stas
 
for XP:
check it an appliation prevents shutdown?

for win2003:
check it the policies allows shutdown (anonymous).

just test the 'shutdown' button on the web interface but make that you are not logged in on the windows.

also, I assume you installed default (acpi)? post your /etc/qemu/VMID.conf files.
 
for XP:
check it an appliation prevents shutdown?

for win2003:
check it the policies allows shutdown (anonymous).

just test the 'shutdown' button on the web interface but make that you are not logged in on the windows.

also, I assume you installed default (acpi)? post your /etc/qemu/VMID.conf files.
1. check it an appliation prevents shutdown? - I checked it without logon
2. Shutdowning machine from the web interface works only if I press shutdown twise (press one time and later press again).
3. acpi isn't disabled in the web interface
 
Unfortunately problem wasn't resolved. Machine normaly shutdown from Web-interface but backup in stop mode doesn't work anyway:

Code:
Oct 17 04:33:01 INFO: Starting Backup of VM 103 (qemu)
Oct 17 04:33:02 INFO: status = running
Oct 17 04:33:02 INFO: starting first sync /var/lib/vz/images/103 to /var/tmp/vzdumptmp28796
Oct 17 04:36:00 INFO: Number of files: 2
Oct 17 04:36:00 INFO: Number of files transferred: 1
Oct 17 04:36:00 INFO: Total file size: 1707044864 bytes
Oct 17 04:36:00 INFO: Total transferred file size: 1707044864 bytes
Oct 17 04:36:00 INFO: Literal data: 1707044864 bytes
Oct 17 04:36:00 INFO: Matched data: 0 bytes
Oct 17 04:36:00 INFO: File list size: 56
Oct 17 04:36:00 INFO: File list generation time: 0.001 seconds
Oct 17 04:36:00 INFO: File list transfer time: 0.000 seconds
Oct 17 04:36:00 INFO: Total bytes sent: 1707253356
Oct 17 04:36:00 INFO: Total bytes received: 35
Oct 17 04:36:00 INFO: sent 1707253356 bytes  received 35 bytes  9618328.96 bytes/sec
Oct 17 04:36:00 INFO: total size is 1707044864  speedup is 1.00
Oct 17 04:36:00 INFO: first sync finished (178 seconds)
Oct 17 04:36:00 INFO: stopping vps
Oct 17 04:46:00 INFO: wait failed - got timeout
Oct 17 04:46:01 ERROR: Backup of VM 103 failed - command 'qm shutdown 103 && qm wait 103 600' failed with exit code 255

There is a strange thing: then I open console (by web-interface) on windows machine after unsuccessful backup it immediatly goes shutdown.
 
vzdump just waits 5 minutes.
Oh, I got it!
No, problem isn't in vzdump. Problem was in ScreenSaver (at least for Windows XP and Windows Server 2003). I've solved it by disable logon ScreenSaver (it was enabled by default for the both systems).

[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"ScreenSaveActive"="0"
 
Oh, I got it!
No, problem isn't in vzdump. Problem was in ScreenSaver (at least for Windows XP and Windows Server 2003). I've solved it by disable logon ScreenSaver (it was enabled by default for the both systems).

[HKEY_USERS\.DEFAULT\Control Panel\Desktop]
"ScreenSaveActive"="0"

More information is here:
http://support.microsoft.com/kb/910617
Problem was fixed in SP3 for Windows XP and SP2 for Windows 2003.
 
I had the issue on a win 2003 srv 32bit sp2, so there are doubts that the problems is resolved by sp2.
proxmox 1.8 here, btw.

IIRC last time I had the problem a few months ago, I also did the windows policy fix and disabled the screensaver, but it didn't help.

So I ended up with doing the "double shutdown button click" via cron-script:

one shutdown command is issued via the normal backup routine (see the error message you get via mail).
i added the same command qm --skiplock shutdown 100 in a cron script and just run it 2 minutes before the backup kicks in.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!