Search results

  1. P

    Proxmox VE 7.1 released!

    Agree Pass through complicated tracking the bug but I believe turned out not to be the cause (as did the current complexity in rolling back the kernel). The root cause is how 7.1 behaves when no DHCP / DNS /external route is available when Proxmox boots. The work around is to add a second...
  2. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    To update / answer my own questions The following were tried but did not help Restart Proxmox with only single dedicated NIC connected (LAN5) then adding other Ethernet connections after Host & all VM finished starting up. Renewing the network connections in Proxmox by pve -> Network -> edit...
  3. P

    pfSense Help

    Should be disabled virtIO (paravirtualised) works fine for me I assume you have created a bridge to connect your NIC to the virtual machines virtIO How many physical NIC to you have? A separate one for Wan and Lan? Are you using Vlans at the moment? What version of pfsense and Proxmox are you...
  4. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    Statically excluding NICs the Proxmox hypervisor will not have access to must be possible because that is what appears to happen dynamically in Kernel Version: Linux 5.13.19-1-pve #1 SMP PVE 5.13.19-3 PVE Manager Version: pve-manager/7.1-6 Although it is not really a solution to the current...
  5. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    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...
  6. P

    [SOLVED] Revert to prior Kernel

    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...
  7. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    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...
  8. P

    [SOLVED] Revert to prior Kernel

    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...
  9. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    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...
  10. P

    [SOLVED] Host network access lost after Proxmox upgrade 7.0 to 7.1 (Router VM with pass through NIC)

    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...