Windows VM hang after Live Migration

P

pixelpeter

Renowned Member
Proxmox Subscriber
Aug 5, 2015
174
4
83
57
Chemnitz
Hallo,

We have a problem after live migration of a windows vm (server 2003 or Server 2008)
Linux vm has no problems!!

Cluster hardware:
HP BL460 C Gen9 128 GB RAM
Network:
6 x 10 GBit NIC
eth0+eth1 bond -> Clusterkommunikation
eth2+eth3 bond -> Storage via NFS Default Setting
eth4+eth5 OVS bond -> VM's

Software:
root@pve2:~# pveversion -v
proxmox-ve: 4.2-56 (running kernel: 4.4.13-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-83
pve-firmware: 1.1-8
libpve-common-perl: 4.0-70
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-70
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80

The migration exit without errors. Ping to the vm is ok. The vm is very slow. restart or shutdown is does not work.
Windows is a clean install.
HD:IDE - Network: E1000 -> not migrate
HD:virtio - Network: virtio -> not migrate
In windows syslog we have no errors!!!

In the testcluster other hardware, same software we have the same problems!!

Where should i look?

Sorry for my english

Peter
 
Hi Dominik,

what do you mean with:
pixelpeter said: ↑
HD:IDE - Network: E1000 -> not migrate
HD:virtio - Network: virtio -> not migrate
Click to expand...
Test with ide and network e1000 migrate fails
Test with virtio -> migrate fails

Here is the migrate log:
Jul 15 06:23:03 starting migration of VM 123 to node 'pve2' (10.6.9.202)
Jul 15 06:23:03 copying disk images
Jul 15 06:23:03 starting VM 123 on remote node 'pve2'
Jul 15 06:23:05 start remote tunnel
Jul 15 06:23:06 starting online/live migration on unix:/run/qemu-server/123.migrate
Jul 15 06:23:06 migrate_set_speed: 8589934592
Jul 15 06:23:06 migrate_set_downtime: 0.1
Jul 15 06:23:06 set migration_caps
Jul 15 06:23:06 set cachesize: 429496729
Jul 15 06:23:06 start migrate command to unix:/run/qemu-server/123.migrate
Jul 15 06:23:08 migration status: active (transferred 211949549, remaining 2381725696), total 4312604672)
Jul 15 06:23:08 migration xbzrle cachesize: 268435456 transferred 0 pages 0 cachemiss 0 overflow 0
Jul 15 06:23:10 migration status: active (transferred 418689699, remaining 259149824), total 4312604672)
Jul 15 06:23:10 migration xbzrle cachesize: 268435456 transferred 0 pages 0 cachemiss 0 overflow 0
Jul 15 06:23:12 migration speed: 682.67 MB/s - downtime 8 ms
Jul 15 06:23:12 migration status: completed
Jul 15 06:23:16 migration finished successfully (duration 00:00:14)
TASK OK
Click to expand...
And the vm config
bootdisk: ide0
cores: 2
ide0: nfs_nosnap:123/vm-123-disk-1.qcow2,size=30G
ide2: none,media=cdrom
keyboard: de
memory: 4096
name: test
net0: e1000=32:61:37:31:37:66,bridge=vmbr0,tag=305
numa: 1
ostype: win8
smbios1: uuid=e1b699b8-a2ff-44d5-8390-49f102c114f6
sockets: 2
vga: std
TASK OK
Click to expand...

Peter
 
if you haven't already, please deactivate the powersaving options in your bios.
windows is prone to crash when using those options and using live migration
 
this depends on your hardware, often you have to press "del" or one of the "f" keys during boot to enter the bios
also the power saving options are named differently on different mainboards
 
mm, i thought it was on the seabios (vm bios). not the host bios... i will try it.
 
Hello,
I have exactly the same problem.

Same hardware for node A and node B.
Drbd for shared storage. Tested with NFS on a synology. Same result.

Only node B is up to date with those settings.
I can't stop VM on node A at this moment.

Linux Guest can migrate without problems, but Windows Guest hang sometime.
I can do without crashing, 6 live migration and 2 with crash (for exemple). It's random.

Motherboard :
supermicro X9DAX-HFT, bios version 3.2.

In BIOS, Advanced, CPU Configuration, CPU Power Management Configuration :
Power Technology : Disable
Override OS energy performance : Enabled (default)
Energy / performance Bias : Performance (default)
Worldload configuration : I/O Sensitive (default)

Other menu :
Intel VT-d : Enabled.

CPU : 2x Intel Xeon CPU E5-2687W @ 3,1 Ghz

VM Config :
Code: 
bootdisk: virtio0
cores: 2
cpu: host
ide2: none,media=cdrom
memory: 8192
name: WINDOWS-DC
net0: virtio=4A:CE:73:27:63:3A,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
scsihw: virtio-scsi-single
smbios1: uuid=d386d76e-8fec-4591-a9cc-503d4a59338e
sockets: 1
startup: order=2,up=40,down=30
vga: std
virtio0: drbdr0:vm-101-disk-1,cache=writethrough,size=50G
virtio1: drbdr0:vm-101-disk-2,backup=0,cache=writethrough,size=350G
virtio2: syno-vol1:101/vm-101-disk-2.raw,backup=0,size=500G

pveversion :
Code: 
proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.15-1-pve: 4.4.15-60
lvm2: 2.02.116-pve2
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-72
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-72
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.3-4
lxcfs: 2.0.2-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80
 
i had updated the two node with last kernel, apply bios settings with powersaving option disabled.
I had done 6 live migration without problem. Next hang.
VM is a Win2012r2.
Thank you.
 
Last edited:
Can anyone to explain what has the hostbiossettings to do with windows live migrations?

Thanks
 
whitewater said:
Hello Fireon, it's seem CPU powersaving disturb Windows time synchronisation.
Click to expand...
Strange. But good to know now. So it is right when i say in bios for example "high performance" so that the cpu frequenzy goes never down? Or did you mean other options?

Thanks
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back