Search results

Booting into the lastest kernel of Proxmox 7.0 solves it for me, but I do not know if there are dependencies. I don't know how to make that older kernel the default boot kernel...

Same for me... If I reduce the number of vCPU's to one in my case, the VM boots...

I've forgot to mention that my problems arose when upgrading from 7.0 to 7.1...

I'm running an Intel i3-9100...

Same for me. When I reduce the number of vCPU's to 1 (it were 3), then the VM does not freeze anymore and runs. I would like to believe it's the new kernel, but I don't know how to test the previous/latest 7.0 supplied kernel (5.11?)

I just reduced the numbers of vCPU's from 3 to 1 and the type from host to KVM64 for the VM, and it runs fairly stable right now... I just do need the vCPU type of host...

Hi all, I'm quite new to Proxmox so please bear with me. I'm running a couple of LXCs and a couple of VMs. After upgrading to 7.1 from the latest 7.0 this morning, my Home Assistant VM refuses to keep running for longer than 30 seconds because of the following error: Nov 18 13:41:08 pve...

Hmm, no, my apoligies for hijacking this topic then :( I was triggered by the 'upgrading pve-qemu-kvm' and the command failed in syslog... Shall I open a new topic?

I've got the same problem with one of my VM's, after upgrading to 7.1: Nov 18 13:41:08 pve pvestatd[1139]: VM 117 qmp command failed - VM 117 qmp command 'query-proxmox-support' failed - unable to connect to VM 117 qmp socket - timeout after 31 retries I tried host CPU and KVM64, but that does...