Search results

I believe the problem is Proxmox is having trouble moving PCI devices / NIC to the vfio-pci kernel driver when it's own network configuration is not established. It thows lots of errors on changing kernel to a later version, disables the Proxmox NIC and can not shutdown but eventually becomes...

Thank you for the insight. I can work with that and it is valuable to have it listed with the other alternatives. I had hoped reverting the kernel would fix my problems however I have since shown my problem is not just the kernel so changing the boot order is not a fix. It would be great if...

Further testing demonstrated: The differences shown above for dmesg | grep -e DMAR -e IOMMU are due to differences between kernel 5.11.22-7-pve and 5.13.19-1-pve (dimonstrated by connecting a keyboard & screen to the hardware to enable selection of the kernel boot options). Network issues when...

What is the recommended way of doing this? An older Kernel can be selected at boot time if A screen and keyboard is connected, and and someone is there when the hypervisor boots So not that convenient for a headless server The boot order can be edited as follows (there is no boot menu option...

I'm not sure if there are any other tests I can do to look at the Nic configuration settings and confirm nothing is being sent from the hardware. Given the other issues reported with pass through, I suspect the problem maybe there. I'm not sure this is correct root@pve:~# dmesg | grep -e DMAR...

I'm new to Proxmox and not sure how to further investigate this fault. Any ideas would be appreciated Fault Proxmox hypervisor has no network access. Ping 192.168.11.1 gateway has 100% packet loss, chrony fails to access any time servers, update servers are unable to refresh. Lan Web access to...