Fresh PVE 9 installation

F

fynchy

New Member
Sep 12, 2025
6
0
1
I have a beginner question. I just finished a fresh installation of PVE, but I don’t have any network access. During the installation, the system picked up an IP address via DHCP. However, after rebooting and logging in for the first time, the network interface was down.

I confirmed that the interface name in /etc/network/interfaces matches the name shown under ip a. I also tried bringing it up with ip link set eno2 up, but there’s still no network connection (despite the interface being listed as up).

I tested both onboard NICs in case the interface names were switching between them, but neither one is working.

What’s strange is that PVE 8 installed without any issues. This problem only seems to happen with PVE 9. Any suggestions?
 
On second thought, could the issue be that the default bridge isn’t inheriting the physical MAC address from the interface? I’ll check on this tomorrow, but it might explain the network problems. If the DHCP lease for the physical MAC wasn’t released during installation, the node could be trying to reuse that IP with a newly generated MAC, causing the conflict.
 
I took some photos to help troubleshoot the issue. On boot, I noticed errors with ifupdown2-pre.service and systemd-udev-settle.service. When I run ip link, I see that the bridge is actually missing. Does ifupdown2-pre.service bring the bridge online?

1000000765.jpg1000000767.jpg
 
Are you sure the ip address should be 192.168.1.153 in a /23 network? Gateway is 192.168.0.1?

Shouldn't it be 192.168.0.153/24?

And your interfaces are down, network cable disconnected?
 
The network cable is connected. One of the issues is that the interfaces are down on boot despite being physically connected to the network. The subnet configuration is correct—it’s a /23, which provides IP addresses in the range 192.168.0.1 to 192.168.1.254.
 
Another update: running 'systemctl start networking' does bring up the bridge and restores network access, but the problem returns after every reboot. I tried updating the system, but the issue remains. What’s unusual is that the command takes about three minutes to complete. At this point, I suspect it may be some odd driver compatibility issue that changed between PVE 8 and 9. I would greatly appreciate some help.
 
The only thing that comes to mind that the ip address is already in use.
You could try to change the ip to something that you know is not in the dhcp range

And what nic do you use?
Code: 
lspci | grep net
 
This issue can be marked as solved. The problem was caused by AMD GPU drivers, which triggered a udev timeout during boot and led to the networking service failing to start. I swapped out the GPU.
 
You must log in or register to reply here.
Top Bottom