Hi,
we have an strange effect. On an new migrated VM to an pve8-node, the offline migration of the VM-disk from ceph to local-zfs destroy the target disk.
The VM arent boot, because the partitiontable are gone and only the content of /boot are on sda.
But we do the same with nine VMs before, and all other work without trouble. But with the failed one, i can reproduce the issue.
If I do the storage-migration online, all work like excepted.
pve-servion:
VM-config
On the Screenshot is sdc the source disk and sda the target after offline-migration - and partitiontable loop looks wrong ;-)
I've tested without iothread but with the same result.
Udo
we have an strange effect. On an new migrated VM to an pve8-node, the offline migration of the VM-disk from ceph to local-zfs destroy the target disk.
The VM arent boot, because the partitiontable are gone and only the content of /boot are on sda.
But we do the same with nine VMs before, and all other work without trouble. But with the failed one, i can reproduce the issue.
If I do the storage-migration online, all work like excepted.
pve-servion:
Code:
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph: 17.2.7-pve2
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.2
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.0
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
openvswitch-switch: 3.1.0-2+deb12u1
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.4
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.4
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
Code:
agent: 1
boot: c
bootdisk: scsi0
cicustom: network=nfs:snippets/vfe02-xxx.xyz-hosting.net-network.yaml,user=nfs:snippets/vfe02-xxx.xyz-hosting.net-user.yaml
cores: 16
cpu: kvm64,flags=+aes
hotplug: disk,network,usb,memory,cpu
ide0: none,media=cdrom
memory: 2048
metaxyz: creation-qemu=7.2.0,ctime=1720021331
name: vfe02-xxx.xyz-hosting.net
net0: virtio=42:50:F3:5D:42:53,bridge=vmbr0,tag=2200
numa: 1
onboot: 1
ostype: l26
scsi0: pve-ceph:vm-645-disk-0,aio=threads,discard=on,iothread=1,size=20G
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=98bbea21-72dc-4751-8241-16ee7981ecfc
sockets: 1
tablet: 0
tags: v-450xx
vcpus: 2
vga: std
vmgenid: 5ee583c6-1856-4628-ad3a-3ea04b62712cI've tested without iothread but with the same result.
Udo
