[PVE-User] Proxmox 4.2 : Online Migration Successful but VM stops

Kevin Lemonnier lemonnierk at ulrar.net
Fri Sep 30 16:28:19 CEST 2016


Hi,

Firstly thanks, I had no idea that existed. I've been hoping for memory hotplug in proxmox for months,
if not years, and was starting to get very surprised that this feature didn't exist. Turns out it does,
for some reason it's just hidden.

I just enabled it on a VM to test and it works great, I didn't have the VM stopping after a few live migrations.
Maybe it's your kernel version ? I have 3.16.36-1+deb8u1 inside the VM I use to test this, and the disks are
on GlusterFS.


On Fri, Sep 30, 2016 at 12:52:47PM +0000, Dhaussy Alexandre wrote:
> Hello,
> 
> Here's the log of a successfull LIVE migration, but the VM stops afterwards and just before resuming. At this point, the service fails, and is restarted by HA services.
> 
> * sept. 30 14:13:12 starting migration of VM 463 to node 'proxmoxt32' (x.x.x.x)
> * .... * sept. 30 14:13:19 migration speed: 1024.00 MB/s - downtime 65 ms * sept. 30 14:13:19 migration status: completed * sept. 30 14:13:20 ERROR: VM 463 not running * sept. 30 14:13:20 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' root at x.x.x.x<mailto:root at x.x.x.x> qm resume 463 --skiplock --nocheck' failed: exit code 2 * sept. 30 14:13:24 ERROR: migration finished with problems (duration 00:00:12) * TASK ERROR: migration problems
> 
> By chance i tested migrating another VM, which had memory hotplug disabled, and it worked ! So i tried on VM 463, after disabling memory hotplug, and live migration works fine !
> 
> * sept. 30 14:14:27 starting migration of VM 463 to node 'proxmoxt20' (x.x.x.x) * .... * sept. 30 14:14:35 migration speed: 1024.00 MB/s - downtime 34 ms * sept. 30 14:14:35 migration status: completed * sept. 30 14:14:39 migration finished successfully (duration 00:00:12) * TASK OK
> 
> So it seems that any VM which has memory hotplug enabled won't resume after successfull live migration.. Anyone have the same issue ?
> 
> Here are the VM parameters :
> 
> acpi: 1 bootdisk: virtio0 cores: 12 hotplug: disk,network,usb,cpu keyboard: fr kvm: 1 memory: 2048 name: mazoutvin net0: virtio=54:52:00:0A:91:60,bridge=vmbr1,tag=36 net1: virtio=54:52:00:0A:91:61,bridge=vmbr2,tag=3 net2: virtio=54:52:00:0A:91:62,bridge=vmbr2,tag=6 numa: 1 onboot: 1 ostype: l26 smbios1: uuid=96d6ad50-6e28-4ece-b936-0b6e87e90c5f sockets: 1 unused0: isilon:463/vm-463-disk-1.vmdk vcpus: 1 virtio0: san_storage:vm-463-disk-1,size=40G
> 
> And pveversion:
> 
> root at proxmoxt31:~# pveversion -v 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.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: not correctly installed criu: 1.6.0-1 fence-agents-pve: 4.0.20-1 openvswitch-switch: 2.5.0-1
> 
> Cheers !
> 
> Alexandre.
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-- 
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://pve.proxmox.com/pipermail/pve-user/attachments/20160930/5f274a06/attachment-0015.sig>


More information about the pve-user mailing list