Live migration targetstorage not working

[Gumby]

Hi all,

I am trying to do a migration of a few virtual disks however the --targetstorage option is being ignored and the original storage path is being used (albeit on the destination node). Anyone have any idea why this might be?

root@node0:~# grep vm-119-disk /etc/pve/qemu-server/119.conf
virtio0: node0_ssd:119/vm-119-disk-1.raw,size=100G

root@node0:~# qm migrate 119 node2 --targetstorage node2_sata_raid --online --with-local-disks
2018-06-07 10:57:13 starting migration of VM 119 to node 'node2' (172.30.0.44)
2018-06-07 10:57:13 found local disk 'node0_ssd:119/vm-119-disk-1.raw' (in current VM config)
2018-06-07 10:57:13 copying disk images
Formatting '/disks/node0_ssd/images/119/vm-119-disk-1.raw', fmt=raw size=107374182400


node0 packages (source node)
proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-2
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.4.128-1-pve: 4.4.128-111
pve-kernel-4.4.6-1-pve: 4.4.6-48
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-32
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

node2 packages (destination node)
proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-2
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-32
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

 

[wolfgang]

Hi,

this happened if your storage does not support the content type of the volume.
In the case of KVM guest, it has to support 'images'.

 

[Gumby]

Unfortunately this is not the case (in my situation). Directly from /etc/pve/storage.cfg

dir: node2_sata_raid
path /disks/sata_raid
content images
nodes node2
shared 1

 

[wolfgang]

This is a bug
please open a bug ticket on
https://bugzilla.proxmox.com/

the bug should have as information the migration output, the storage config and the pveversion of the sender.
After creation please send the link here

 

[Gumby]

Here you go

https://bugzilla.proxmox.com/show_bug.cgi?id=1804

 

[wolfgang]

Tanks for the report.

Side Node If you have a local storage what is not a shared storage does not mark it as shared.