After upgrade to PVE 7.0-14+1 not able to start any VM [solved]

M

MaLe

Active Member
Proxmox Subscriber
Jul 26, 2021
63
19
28
56
Hi,

I just upgraded our test environment (currently no subscription) to 7.0-14+1 and after rebooting the host it's not possible to start any VM. The task is running forever without any error message. I tried from UI and console. Anyone a similar issue?

Regards
Martin
 
@MaLe - There is an issue that is related to the pve-qemu-kvm package.

Revert using apt install pve-qemu-kvm:amd64=6.0.0-3

This started for me with 6.0.0-4 and has not been resolved with 6.1.0-1 (which is the latest update)

I have not seen any information with regard to a fix on this.

You can tail -f /var/log/syslog when you start your VM and you'll probably see an emulation failure.
 
@djgraff209 - Many thanks for your reply. I just checked the tail -f /var/log/syslog

Nov 11 08:09:07 pve00000 pvedaemon[498213]: start VM 100: UPID:pve00000:00079A25:002E31A7:618CC193:qmstart:100:root@pam: Nov 11 08:09:07 pve00000 pvedaemon[1843]: <root@pam> starting task UPID:pve00000:00079A25:002E31A7:618CC193:qmstart:100:root@pam:
That seems to be another issue. There are no error messages, the task seems to hang and nothing happens.
 
I have to apologize, it was my mistake. After running the task for 5 minutes there came an error message:

Nov 11 08:14:06 pve00000 pvedaemon[498213]: timeout: no zvol device link for 'vm-100-disk-0' found after 300 sec found.

The reason was, the ZFS pool is encrypted where the VM is located. I didn't unlocked it correctly after starting the host. I double checked this and after unlocking everything is now working.

Sorry for that. I marked this thread as solved.
 
MaLe said:
I have to apologize, it was my mistake. After running the task for 5 minutes there came an error message:

Nov 11 08:14:06 pve00000 pvedaemon[498213]: timeout: no zvol device link for 'vm-100-disk-0' found after 300 sec found.

The reason was, the ZFS pool is encrypted where the VM is located. I didn't unlocked it correctly after starting the host. I double checked this and after unlocking everything is now working.

Sorry for that. I marked this thread as solved.
Click to expand...
Ah - you obviously have a much more advanced setup that me!

Glad that worked out for you!
 
You must log in or register to reply here.
Top Bottom