The network card does not work properly when the first pci slot is used.

[moqi2011]

Steps:
1. Install PVE when PCI slot 1 is empty.
2. Close PVE, PCI slot 1 is inserted into the device.
3. Start PVE, and the network card light goes out after entering the PVE boot interface, restart still like this.

Inserting a device in PCI slot 2 does not have this problem.

 

[moqi2011]

System version: Linux 5.15.102-1-pve #1 SMP PVE 5.15.102-1 (2023-03-14T13:48Z)

 

[moqi2011]

Motherboard model: TUF GAMING B660M-PLUS D4

 

[moqi2011]

CPU : Intel 12500

 

[leesteken]

Adding (or removing) PCI(e) devices can change the PCI ID of other devices (typically the ones numbered higher than the added (or removed) one). The network device name is derived from the PCI ID (which probably changed). You need to adjust the Proxmox network configuration accordingly. Several threads about this on this forum contain more details about this.

 

[moqi2011]

Adding (or removing) PCI(e) devices can change the PCI ID of other devices (typically the ones numbered higher than the added (or removed) one). The network device name is derived from the PCI ID (which probably changed). You need to adjust the Proxmox network configuration accordingly. Several threads about this on this forum contain more details about this.

Why does the PCI ID change affect the normal use of functions when PCI passthrough is not used?

 

[leesteken]

Why does the PCI ID change affect the normal use of functions when PCI passthrough is not used?

The network device name is derived from the PCI ID (which probably changed).

The PCI ID's change because a device was inserted somewhere in between (complain to your motherboard/BIOS manufacturer). Therefore the names of your network devices change, because that's how Debian/Linux works unless you change the naming of the network devices. Therefore the Proxmox network configuration is no longer valid, because it uses the old names in the configuration. Note that I did not mention PCI(e) passthrough anywhere.

 

[moqi2011]

The PCI ID's change because a device was inserted somewhere in between (complain to your motherboard/BIOS manufacturer). Therefore the names of your network devices change, because that's how Debian/Linux works unless you change the naming of the network devices. Therefore the Proxmox network configuration is no longer valid, because it uses the old names in the configuration. Note that I did not mention PCI(e) passthrough anywhere.

I don't quite understand this situation. Does this situation exist under Linux? Why not identify the device by device ID but by PCI ID. According to my experience, both PCI devices and USB devices are plug and play.

 

[leesteken]

I don't quite understand this situation. Does this situation exist under Linux? Why not identify the device by device ID but by PCI ID. According to my experience, both PCI devices and USB devices are plug and play.

The device ID would be problematic when you have multiple identical devices. I don't feel the need to convince you of any of this, but I do think it is what happens when you insert the network card. Please check for yourself using ip a and /etc/network/interfaces.

 

[moqi2011]

The device ID would be problematic when you have multiple identical devices. I don't feel the need to convince you of any of this, but I do think it is what happens when you insert the network card. Please check for yourself using ip a and /etc/network/interfaces.

OK, I get it. Thank you for your answer.

 

[leesteken]

Here is a new occurrence of the same problem. Did you manage to fix the network configuration?

 

[moqi2011]

Here is a new occurrence of the same problem. Did you manage to fix the network configuration?

I just plugged in a PCI device for testing, and now I have canceled the device. Thanks for the information.

 

[moqi2011]

Here is a new occurrence of the same problem. Did you manage to fix the network configuration?

Through the information provided by 'ip a', I modified the '/etc/network/interfaces' file to change enp4s0 to enp5s0, and the network can be used normally.

 

[moqi2011]

Here is a new occurrence of the same problem. Did you manage to fix the network configuration?

Now there is a new problem. If I pass through the device of PCI slot 1 to the guest, the network card becomes enp4s0 again when the guest is turned on, which again causes the network to be unavailable. Is there any way to resolve this conflict?

 

[leesteken]

Now there is a new problem. If I pass through the device of PCI slot 1 to the guest, the network card becomes enp4s0 again when the guest is turned on, which again causes the network to be unavailable. Is there any way to resolve this conflict?

I have never seen that happen. The PCI ID should not change because of passthrough. It is common that devices disappear because they are in the same IOMMU group, but not change their name (even when based on PCI ID) that is determined during the boot process.
Anyway, you can set the network device names yourself (based on device ID or MAC) using udev rules. I have no experience with that but I'm sure it has come up here or on the Proxmox wiki and there are generic Linux guides on the internet.

 

[moqi2011]

I have never seen that happen. The PCI ID should not change because of passthrough. It is common that devices disappear because they are in the same IOMMU group, but not change their name (even when based on PCI ID) that is determined during the boot process.
Anyway, you can set the network device names yourself (based on device ID or MAC) using udev rules. I have no experience with that but I'm sure it has come up here or on the Proxmox wiki and there are generic Linux guides on the internet.

Not sure if the PCI ID has changed, I am now resorting to using another PCI slot to solve this problem. Because using this slot all the PCI IDs are out of order.