no network on guest after replacing motherboard and cpu

[stef68]

Hi,
i'm new to promox and like it so far. i decided to upgrade my homelab for a cpu with more core. So i replaced the mobo and cpu of my homelab promox. after reading that i only needs to update /etc/netork/interfaces with new network interface name. I give it a try. it did fix the network to allow me to load the admin page from another computer on my lan but the guess does not seems to reach my DHCP service from my router. i'm able to start a VM and interact with it but my guest VM don't see my lan which was working fine before i upgrade. not sure if relevent but my new mobo has 2 nic but only one is hook to my lan on 10.0.1.x

anything i missed to set ?

here some info that was asked in other post with network issue.

/etc/network/interfaces

auto lo
iface lo inet loopback

iface enp7s0 inet manual

iface enp8s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.0.1.235/24
        gateway 10.0.1.1
        bridge-ports enp8s0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.2.235/24
        bridge-ports enp7s0
        bridge-stp off
        bridge-fd 0

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 state DOWN group default qlen 1000
    link/ether f0:2f:74:f2:d8:89 brd ff:ff:ff:ff:ff:ff
3: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether f0:2f:74:f2:d8:88 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f0:2f:74:f2:d8:88 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.235/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::f22f:74ff:fef2:d888/64 scope link
       valid_lft forever preferred_lft forever
5: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether f0:2f:74:f2:d8:89 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.235/24 scope global vmbr1
       valid_lft forever preferred_lft forever

ip l

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:f2:d8:89 brd ff:ff:ff:ff:ff:ff
3: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:f2:d8:88 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:f2:d8:88 brd ff:ff:ff:ff:ff:ff
5: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether f0:2f:74:f2:d8:89 brd ff:ff:ff:ff:ff:ff

 

[stef68]

It looks like an incompatibility issue with the Linux bridge option with both onboard nic. I guess the 2.5g nic on this MBoard is to recent. I was able to have it to works by adding another nic and set this one to be used by the vm guest. And now, i have network access on VMs. to confirm, I switch it back to the onboard 2,5G and no network for guest VMs. So for now, i'll keep this other nic in my promox and hope that linux bridge function gets fix

 

[stef68]

Promox 7.0 and higher did fix this issue