Search results

cpu: host,flags=+hv-tlbflush Apr 4 02:25:41 ns3192824 kernel: [ 155.026189] kvm_hv_flush_tlb.isra.0+0x116/0x540 [kvm] Try removing the +hv-tlbflush flag (using the gui, or remove the ,flags=+hv-tlbflush from the cpu: line in the config file) and see if that makes a difference.

Do you have iothread enabled for the drive? In my case removing the iothread=1 allowed the vm to boot without having to change the caching mode.

With the latest kernel update pve-kernel-5.13/stable 7.1-7 there are no more boot, network or shutdown/reboot issues with the amdgpu (in my case) so as far as I'm concerned this issue is solved on my end.

There shouldn't be any problems upgrading other software as long as it doesn't depend on some new kernel capability/abi/api (which generally shouldn't change for the 5.13 branch). Personally I've never had any problems on debian. The only problem could be related to new kernel fixing potential...

I've tried the 5.15 kernel and can confirm that it solves the problems. However 5.15.5 has some problems related to drive cache https://bugzilla.kernel.org/show_bug.cgi?id=215137 so I'll wait for at least 5.15.6. As I see it there are 3 options to solve these problems: Use kernel 5.15 with apt...

Yeah my hardware is pretty similar to yours (down to the unused WiFi nic) so I suspect that it is related to the AMD gpu (see the following thread https://forum.proxmox.com/threads/proxmox-wont-boot-with-latest-kernel-5-13-19-2-pve.100825/ ). One Intel nuc has no problem, masking the service...

Hi, Since kernel 5.13.19-2-pve one of the pve hosts hangs on boot for 2 minutes while starting ifupdown2-pre.service and systemd-udev-settle.service . When booted system has no networking and has to be started with systemctl start networking.service . Also when issuing a restart command system...