Hi all,
Having an issue with PVE 4.2-2... first of all, after a host reboot, the networking stack does not come back up. A simple "service networking restart" fixes this, but I would like to remove this step. Per recommendations in this forum, I have purged and reinstalled openvswitch-switch to no avail.
Additionally, VMs that are created using the virtio or E1000 NICs have incredibly slow network performance (as in it takes 20 minutes just to run an apt-get update). Selecting the RTL8139 resolves this issue. The host network is fine, and runs as expected. This only affects VMs and containers.
Unfortunately, for containers, there is no option to select NIC, and the slow network performance is evident there.
I'm assuming this is all somehow connected... and for the life of me, I don't even know where to start troubleshooting.
Happy to post whatever logs, configs, etc you think might be helpful!
Having an issue with PVE 4.2-2... first of all, after a host reboot, the networking stack does not come back up. A simple "service networking restart" fixes this, but I would like to remove this step. Per recommendations in this forum, I have purged and reinstalled openvswitch-switch to no avail.
Additionally, VMs that are created using the virtio or E1000 NICs have incredibly slow network performance (as in it takes 20 minutes just to run an apt-get update). Selecting the RTL8139 resolves this issue. The host network is fine, and runs as expected. This only affects VMs and containers.
Unfortunately, for containers, there is no option to select NIC, and the slow network performance is evident there.
I'm assuming this is all somehow connected... and for the life of me, I don't even know where to start troubleshooting.
Happy to post whatever logs, configs, etc you think might be helpful!