[PVE-User] cloud-init drive prevents offline migration

Zhuoyun Wei wzyboy at wzyboy.org
Fri Feb 15 16:23:07 CET 2019


proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-5 (running version: 5.3-5/97ae681d)
pve-kernel-4.15: 5.2-12
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1
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.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-33
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1


It's a vanilla installation using 5.3 iso. But I am not sure it's 5.3-1 iso or 5.3-2 iso.

-- 
Zhuoyun Wei

On Fri, Feb 15, 2019, at 23:13, Dietmar Maurer wrote:
> > It seems that PVE considers the cloud-init drive as a local resource that cannot be moved. After removing the cloud-init drive from the VM, the migration succeeded.
> > 
> > IMHO, the cloud-init drive could be treated just like a normal disk image that could be dd'ed and copied to another node.
> > 
> > Is this a bug or by design? If so, I could file a report at Bugzilla.
> 
> AFAIK this bug is already fixed - maybe you run an old version? What is 
> the output of
> 
> # pveversion -v
> 
>


More information about the pve-user mailing list