unable to clone VMs

Sylvain.D

New Member
May 15, 2023
5
0
1
Hello everybody,

Maybe someone can help me.

I have an hypervisor Proxmox 7.4-3 connected to a SCSI SAN by ISCSI (LVM).
Since few days i encounter a problem to clone VMs, every VMs are Windows 10, and clone opérations are clean.
But all cloned VMs cannot boot (UEFI boot crash, system seems to be not able to view system volume).
if i attach disk cloned to a clean VM, i can see the volume but it in dirty state.

I checked SAN log ans all is OK.
I have make the same test with internal server storage storage (local-thin) and clone boot properly.

i post pveversion :

proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph: 17.2.5-pve1
ceph-fuse: 17.2.5-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.6
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-2
pve-firewall: 4.3-1
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

Thank you in advance for your help.

Sylvain
 
Hi,
did you change anything a few days ago (e.g. upgrade)? Do you have the guest agent installed in the VM and enabled? Otherwise the file system might not be in a clean state when finishing the clone. Does it work if you clone while the VM is offline? Is there anything in /var/log/syslog around the time of the operation?
 
Nothing have been changed or updated, it's a fresh install of 7.4-3.
Guest agent is installed ans enable in proxmox ans guest VM.
Clone test have been made with offline VMs.
No error found in /var/log/syslog

I post clone task result :
Task viewer: VM 112 - Clone
create full clone of drive efidisk0 (local-thin:vm-112-disk-0)
Rounding up size to full physical extent 4.00 MiB
Logical volume "vm-105-disk-0" created.
create full clone of drive sata0 (local-thin:vm-112-disk-1)
Wiping gpt signature on /dev/vg-iscsi/vm-105-disk-1.
Wiping gpt signature on /dev/vg-iscsi/vm-105-disk-1.
Wiping PMBR signature on /dev/vg-iscsi/vm-105-disk-1.
Logical volume "vm-105-disk-1" created.
transferred 0.0 B of 100.0 GiB (0.00%)
transferred 1.0 GiB of 100.0 GiB (1.00%)
transferred 2.0 GiB of 100.0 GiB (2.00%)
transferred 3.0 GiB of 100.0 GiB (3.01%)
transferred 4.0 GiB of 100.0 GiB (4.01%)
transferred 5.0 GiB of 100.0 GiB (5.01%)
transferred 6.0 GiB of 100.0 GiB (6.01%)
transferred 7.0 GiB of 100.0 GiB (7.01%)
transferred 8.0 GiB of 100.0 GiB (8.02%)
transferred 9.0 GiB of 100.0 GiB (9.02%)
transferred 10.0 GiB of 100.0 GiB (10.02%)
transferred 11.0 GiB of 100.0 GiB (11.02%)
transferred 12.0 GiB of 100.0 GiB (12.02%)
transferred 13.0 GiB of 100.0 GiB (13.03%)
transferred 14.0 GiB of 100.0 GiB (14.03%)
transferred 15.0 GiB of 100.0 GiB (15.03%)
transferred 16.0 GiB of 100.0 GiB (16.03%)
transferred 17.0 GiB of 100.0 GiB (17.03%)
transferred 18.0 GiB of 100.0 GiB (18.04%)
transferred 19.0 GiB of 100.0 GiB (19.04%)
transferred 20.0 GiB of 100.0 GiB (20.04%)
transferred 21.0 GiB of 100.0 GiB (21.04%)
transferred 22.0 GiB of 100.0 GiB (22.04%)
transferred 23.0 GiB of 100.0 GiB (23.04%)
transferred 24.0 GiB of 100.0 GiB (24.05%)
transferred 25.0 GiB of 100.0 GiB (25.05%)
transferred 26.0 GiB of 100.0 GiB (26.05%)
transferred 27.0 GiB of 100.0 GiB (27.05%)
transferred 28.0 GiB of 100.0 GiB (28.05%)
transferred 29.1 GiB of 100.0 GiB (29.06%)
transferred 30.1 GiB of 100.0 GiB (30.06%)
transferred 31.1 GiB of 100.0 GiB (31.06%)
transferred 32.1 GiB of 100.0 GiB (32.06%)
transferred 33.1 GiB of 100.0 GiB (33.06%)
transferred 34.1 GiB of 100.0 GiB (34.07%)
transferred 35.1 GiB of 100.0 GiB (35.07%)
transferred 36.1 GiB of 100.0 GiB (36.07%)
transferred 37.1 GiB of 100.0 GiB (37.07%)
transferred 38.1 GiB of 100.0 GiB (38.07%)
transferred 39.1 GiB of 100.0 GiB (39.08%)
transferred 40.1 GiB of 100.0 GiB (40.08%)
transferred 41.1 GiB of 100.0 GiB (41.08%)
transferred 42.1 GiB of 100.0 GiB (42.08%)
transferred 43.1 GiB of 100.0 GiB (43.08%)
transferred 44.1 GiB of 100.0 GiB (44.09%)
transferred 45.1 GiB of 100.0 GiB (45.09%)
transferred 46.1 GiB of 100.0 GiB (46.09%)
transferred 47.1 GiB of 100.0 GiB (47.09%)
transferred 48.1 GiB of 100.0 GiB (48.09%)
transferred 49.1 GiB of 100.0 GiB (49.10%)
transferred 50.1 GiB of 100.0 GiB (50.10%)
transferred 51.1 GiB of 100.0 GiB (51.10%)
transferred 52.1 GiB of 100.0 GiB (52.10%)
transferred 53.1 GiB of 100.0 GiB (53.10%)
transferred 54.1 GiB of 100.0 GiB (54.11%)
transferred 55.1 GiB of 100.0 GiB (55.11%)
transferred 56.1 GiB of 100.0 GiB (56.11%)
transferred 57.1 GiB of 100.0 GiB (57.11%)
transferred 58.1 GiB of 100.0 GiB (58.11%)
transferred 59.1 GiB of 100.0 GiB (59.12%)
transferred 60.1 GiB of 100.0 GiB (60.12%)
transferred 61.1 GiB of 100.0 GiB (61.12%)
transferred 62.1 GiB of 100.0 GiB (62.12%)
transferred 63.1 GiB of 100.0 GiB (63.12%)
transferred 64.1 GiB of 100.0 GiB (64.12%)
transferred 65.1 GiB of 100.0 GiB (65.13%)
transferred 66.1 GiB of 100.0 GiB (66.13%)
transferred 67.1 GiB of 100.0 GiB (67.13%)
transferred 68.1 GiB of 100.0 GiB (68.13%)
transferred 69.1 GiB of 100.0 GiB (69.13%)
transferred 70.1 GiB of 100.0 GiB (70.14%)
transferred 71.1 GiB of 100.0 GiB (71.14%)
transferred 72.1 GiB of 100.0 GiB (72.14%)
transferred 73.1 GiB of 100.0 GiB (73.14%)
transferred 74.1 GiB of 100.0 GiB (74.14%)
transferred 75.1 GiB of 100.0 GiB (75.15%)
transferred 76.1 GiB of 100.0 GiB (76.15%)
transferred 77.1 GiB of 100.0 GiB (77.15%)
transferred 78.1 GiB of 100.0 GiB (78.15%)
transferred 79.1 GiB of 100.0 GiB (79.15%)
transferred 80.2 GiB of 100.0 GiB (80.16%)
transferred 81.2 GiB of 100.0 GiB (81.16%)
transferred 82.2 GiB of 100.0 GiB (82.16%)
transferred 83.2 GiB of 100.0 GiB (83.16%)
transferred 84.2 GiB of 100.0 GiB (84.16%)
transferred 85.2 GiB of 100.0 GiB (85.17%)
transferred 86.2 GiB of 100.0 GiB (86.17%)
transferred 87.2 GiB of 100.0 GiB (87.17%)
transferred 88.2 GiB of 100.0 GiB (88.17%)
transferred 89.2 GiB of 100.0 GiB (89.17%)
transferred 90.2 GiB of 100.0 GiB (90.18%)
transferred 91.2 GiB of 100.0 GiB (91.18%)
transferred 92.2 GiB of 100.0 GiB (92.18%)
transferred 93.2 GiB of 100.0 GiB (93.18%)
transferred 94.2 GiB of 100.0 GiB (94.18%)
transferred 95.2 GiB of 100.0 GiB (95.19%)
transferred 96.2 GiB of 100.0 GiB (96.19%)
transferred 97.2 GiB of 100.0 GiB (97.19%)
transferred 98.2 GiB of 100.0 GiB (98.19%)
transferred 99.2 GiB of 100.0 GiB (99.19%)
transferred 100.0 GiB of 100.0 GiB (100.00%)
transferred 100.0 GiB of 100.0 GiB (100.00%)
TASK OK
 
Guest agent is installed ans enable in proxmox ans guest VM.
You don't need to install the guest agent in Proxmox VE directly, it's only intended for the guests. The only case you need it, would be if Proxmox VE itself runs as a VM ;)

Clone test have been made with offline VMs.
That shouldn't lead to broken disks of course (if the source disk is not already broken).

Can you post the output of qm config 112 and cat /etc/pve/storage.cfg?
 
qm config 112 :
bios: ovmf
boot: order=ide2;sata0;net0
cores: 4
efidisk0: DATA-DEVOPS:vm-112-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: none,media=cdrom
machine: pc-i440fx-7.2
memory: 16382
meta: creation-qemu=7.2.0,ctime=1683803561
name: Copy-of-VM-111
net0: e1000=4A:0A:7B:5F:AB:3C,bridge=vmbr0,link_down=1
numa: 0
ostype: win10
sata0: DATA-DEVOPS:vm-112-disk-1,backup=0,size=100G,ssd=1
smbios1: uuid=43a5aa03-1a5e-48ad-b483-ba03e135d099
sockets: 2
vmgenid: c7dd4b45-4b44-47e9-9458-480eb65e0f06

cat /etc/pve/storage.cfg :
dir: local
path /var/lib/vz
content iso,backup,images,vztmpl
shared 0

lvmthin: local-thin
thinpool data
vgname pve
content images,rootdir

dir: ramDisk
path /media/ramDisk
content images
prune-backups keep-all=1
shared 0

lvm: DATA-DEVOPS
vgname vg-iscsi
content rootdir,images
shared 1
 
Since few days i encounter a problem to clone VMs, every VMs are Windows 10, and clone opérations are clean.
But all cloned VMs cannot boot (UEFI boot crash, system seems to be not able to view system volume).
Try downgrading the pve-edk2-firmware package or use a different CPU Type than host or disable memory hotplug. I could not find information about your VM configurations or your host system, so I'm just guessing.
 

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!

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!