VM failing to start

[andreviana]

Hello guys,

I'm getting this errors when I'm trying to start a vm.
Proxmox 7

Use of uninitialized value in addition (+) at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 496.
Use of uninitialized value $data in print at /usr/share/perl5/PVE/Tools.pm line 254.

Any idea?Thanks in advance.

pveversion -v output:
proxmox-ve: 7.0-2 (running kernel: 5.11.22-7-pve)
pve-manager: 7.0-14 (running version: 7.0-14/a9dbe7e3)
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-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.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-12
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-13
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.13-1
proxmox-backup-file-restore: 2.0.13-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.1.0-1
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-18
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve1

 

[pascal33]

Hi,
same problem after resizing hardware parameters of a cloud-init template full clone.
seems to be a disk attachment problem.

1. path?
2. rights?
3. corrupted raw device ?

I don't have yet the solution. Instead , I have fully parametered a new full clone resizing all before first boot

 

[andreviana]

Hello @pascal33,
Thanks for your reply.
I tried to download my OS image template from another computer, and it worked.
For me seems like the template got corrupted during the download.

 

[kwoot]

Using pve 7.1. I always get this error using any Ubuntu 20.04 and 18.04 cloud-init image when I try to start the vm.
Any hint would be highly appreciated.

 

[kwoot]

Ah, so my create-vm script stored the disk image in lvm pool local, and in 7.1 that should be local-lvm. Changed in my script.

 

[Byron McCollum]

I have the same issue. They are Ubuntu 18.04 VMs. If I try starting them after initially failing, it seems to work.

Failed:

Use of uninitialized value in addition (+) at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 496.
Use of uninitialized value $data in print at /usr/share/perl5/PVE/Tools.pm line 254.
failed to stat '/mnt/pve/xpenology-nfs/images/501/vm-501-cloudinit.qcow2'
TASK ERROR: disk image '/mnt/pve/xpenology-nfs/images/501/vm-501-cloudinit.qcow2' already exists

Start After Failing:

Use of uninitialized value in addition (+) at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 496.
Use of uninitialized value $data in print at /usr/share/perl5/PVE/Tools.pm line 254.
generating cloud-init ISO
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.movbe [bit 22]
TASK OK

 

[Byron McCollum]

Regenerating the Cloud-Init image seems to have fixed the above TASK ERROR. Still getting the errors about uninitialized value, but at least the VM starts up the first time.

 

[godfather007]

Regenerating the Cloud-Init image seems to have fixed the above TASK ERROR. Still getting the errors about uninitialized value, but at least the VM starts up the first time.

TASK viewer:

Use of uninitialized value in addition (+) at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 496.
Use of uninitialized value $data in print at /usr/share/perl5/PVE/Tools.pm line 254.

Having the same