Search results

proxmox-boot-tool is a handy option proxmox-boot-tool kernel list to list available kernels proxmox-boot-tool kernel pin 5.13.19-6-pve to choose 5.13.19-6-pve for example.

It is very strange to hear about problems on 5.13.19-6-pve kernel. Maybe it is also CPU specific. I can confirm that VMs do not crash with this Kernel on a number of hosts with Xeon E3-1275 v6 and i9-9900K CPUs. Near a month ago I have tried running some test versions of 5.15 pve kernel on...

5.13.19-6-pve kernel works absolutely stable in my case. Also I have not faced any guest crashes with 5.15.35-1-pve kernel if nested virtualization on Proxmox host is disabled (cat /sys/module/kvm_intel/parameters/nested replies N). But I have not tested for a long time, only 24h, as I need...

Hello everyone! As far as I examined, the above problem appeared with 5.15 Proxmox kernel after update to Proxmox 7.2. With enabled nested virtualization (cat /sys/module/kvm_intel/parameters/nested replies Y) on Proxmox host. With Windows guests. And only on Intel processors, In my case it...

I have updated the Ryzen hosts to Proxmox 7.1 with 5.13.19-2-pve Kernel. I can confirm that in my use case the issue is fixed now. Proxmox7.1>Windows Server>Virtualbox nested virtualization works, no more BSODs on Windows VMs.

Decided to try the above scenario Linux Qemu-KVM>Windows Server>Virtualbox with different Qemu and Linux Kernel versions. On the same AMD Ryzen 5 3600 CPU host. Installed Debian 11 from scratch, the Qemu version is 5.2 Linux Kernel is 5.10.0-8-amd64 BSOD on Windows server guest running...

Hello! I faced up the same issue. Tried a number of machines, all with AMD Ryzen 5 3600 CPU. The nesting scenario Proxmox7>Windows Server>Virtualbox works, but BSOD happens at random time. Even if Virtualbox is already closed, but was running previously after boot. May get BSOD some minutes...

Same issue with 6.1-3 Setting the full pciid in the VM config works as a workaround