Arch Linux

rakehandle

Member

Registered: 2022-10-23

Posts: 2

VMs will not pull IP address

Hello,

I'm trying to set up a bridged VM and I just can't seem to get IP connectivity for my VMs on the network. Booting into the VM (running oracle linux, and same with ubuntu) gives no IP address on their ethernet interface. If I manually assign one in the VM I am able to ping the bridge interface IP on the host, but not the gateway (which is just the network router) or anything else. I assigned a static IP for the VM as well in the router just to test it and nothing seemed to change.

I'm using br3 to bridge the VM

❯ virsh net-list --all
 Name      State      Autostart   Persistent
----------------------------------------------
 br3       active     yes         yes
 default   inactive   no          yes

❯ 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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br3 state UP group default qlen 1000
    link/ether 10:7b:44:25:b6:c2 brd ff:ff:ff:ff:ff:ff
3: br3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 36:ec:a4:f8:b1:18 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.136/24 metric 1024 brd 192.168.0.255 scope global dynamic br3
       valid_lft 6585sec preferred_lft 6585sec
    inet6 fe80::34ec:a4ff:fef8:b118/64 scope link
       valid_lft forever preferred_lft forever
4: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether f4:96:34:3b:65:c8 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:91:7f:c5:cf brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

VM nic configuration:
<interface type="bridge">
  <mac address="52:54:00:0d:73:cf"/>
  <source network="br3" portid="ca7aeeb5-1e58-4c5c-8340-a1056ff52467" bridge="br3"/>
  <target dev="vnet0"/>
  <model type="virtio"/>
  <alias name="net0"/>
  <address type="pci" domain="0x0000" bus="0x08" slot="0x00" function="0x0"/>
</interface>

VM eth interace shows up in an unkown state on the host (guessing that's normal)
6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br3 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:0d:73:cf brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe0d:73cf/64 scope link
       valid_lft forever preferred_lft forever

Network DHCP is clearly working for the bridge based on networkd output:

❯ systemctl status systemd-networkd
● systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Mon 2022-10-24 22:04:08 CDT; 1h 43min ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 270 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9378)
     Memory: 3.2M
        CPU: 88ms
     CGroup: /system.slice/systemd-networkd.service
             └─270 /usr/lib/systemd/systemd-networkd

Oct 24 22:04:09 wizard systemd-networkd[270]: br3: Gained IPv6LL
Oct 24 22:04:10 wizard systemd-networkd[270]: br3: Lost carrier
Oct 24 22:04:10 wizard systemd-networkd[270]: br3: DHCPv6 lease lost
Oct 24 22:04:11 wizard systemd-networkd[270]: enp2s0: Gained carrier
Oct 24 22:04:11 wizard systemd-networkd[270]: br3: Gained carrier
Oct 24 22:04:18 wizard systemd-networkd[270]: br3: DHCPv4 address 192.168.0.136/24, gateway 192.168.0.1 acquired from 192.168.0.1
Oct 24 22:04:21 wizard systemd-networkd[270]: docker0: Link UP
Oct 24 22:22:51 wizard systemd-networkd[270]: vnet0: Link UP
Oct 24 22:22:51 wizard systemd-networkd[270]: vnet0: Gained carrier
Oct 24 22:22:53 wizard systemd-networkd[270]: vnet0: Gained IPv6LL

I'm not sure where the DHCP is getting lost between the bridge and the VMs. I have dnsmasq installed and active and the bridge is configured in systemd-networkd.

It feels like I must be missing something super simple and I just can't see it. Any help is appreciated. Thanks for reading

Last edited by rakehandle (2022-10-29 02:31:46)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,576

Re: VMs will not pull IP address

Welcome to the forums.
I'm sorry, what is the host OS? What is the Guest OS? And which VM are you using?

Also, please be considerate to your reader and use BBCode code tags around program output and file contents.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

rakehandle

Member

Registered: 2022-10-23

Posts: 2

Re: VMs will not pull IP address

Thank you for your rapid response!
BBCode tags, got it. Will do, my apologies.

Host OS: arch 6.0.2-arch1-1
Guest OS: oracle linux 8.5

I created another VM using Ubuntu-22.04.1, but that was only for the sake of having another test case. Both VMs use qemu/kvm with virt-manager. I hope that answers your question about which VM I'm using. Let me know if I mistook your question.

The oracle VM is running NM, which gives the following log:

 -- Logs begin at Tue 2022-10-25 17:58:16 EDT, end at Tue 2022-10-25 18:00:14 EDT. --
Oct 25 17:58:21 localhost.localdomain systemd[1]: Starting Network Manager...
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.7969] NetworkManager (version 1.36.0-4.0.1.el8) is starting... (for the first time)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.7974] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 00-server.conf)
Oct 25 17:58:21 localhost.localdomain systemd[1]: Started Network Manager.
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.8048] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.8107] manager[0x55fa7404f000]: monitoring kernel firmware directory '/lib/firmware'.
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9278] hostname: hostname: using hostnamed
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9279] hostname: static hostname changed from (none) to "localhost.localdomain"
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9281] dns-mgr[0x55fa74024250]: init: dns=default,systemd-resolved rc-manager=symlink
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9391] manager[0x55fa7404f000]: rfkill: Wi-Fi hardware radio set enabled
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9392] manager[0x55fa7404f000]: rfkill: WWAN hardware radio set enabled
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9431] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-device-plugin-adsl.so)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9525] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-device-plugin-bluetooth.so)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9604] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-device-plugin-wifi.so)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9631] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-device-plugin-wwan.so)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9652] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-device-plugin-team.so)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9658] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9658] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9659] manager: Networking is enabled by state file
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9717] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.36.0-4.0.1.el8/libnm-settings-plugin-ifcfg-rh.so")
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9718] settings: Loaded settings plugin: keyfile (internal)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9770] dhcp-init: Using DHCP client 'internal'
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9770] device (lo): carrier: link connected
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9785] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9859] manager: (enp9s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9872] device (enp9s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Oct 25 17:58:21 localhost.localdomain NetworkManager[908]: <info>  [1666735101.9912] device (enp9s0): carrier: link connected
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0047] modem-manager: ModemManager available
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0081] device (enp9s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0111] policy: auto-activating connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0170] device (enp9s0): Activation: starting connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0178] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0193] manager: NetworkManager state is now CONNECTING
Oct 25 17:58:22 localhost.localdomain NetworkManager[908]: <info>  [1666735102.0208] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:58:23 localhost.localdomain NetworkManager[908]: <info>  [1666735103.0066] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:58:23 localhost.localdomain NetworkManager[908]: <info>  [1666735103.0084] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3331] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3364] manager: NetworkManager state is now DISCONNECTED
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <warn>  [1666735148.3376] device (enp9s0): Activation: failed for connection 'eth1'
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3390] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3535] dhcp4 (enp9s0): canceled DHCP transaction
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3568] policy: auto-activating connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3579] device (enp9s0): Activation: starting connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3580] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3585] manager: NetworkManager state is now CONNECTING
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3589] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3810] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:08 localhost.localdomain NetworkManager[908]: <info>  [1666735148.3815] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
Oct 25 17:59:22 localhost.localdomain NetworkManager[908]: <info>  [1666735162.3320] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0532] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0537] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0543] device (virbr0): Activation: starting connection 'virbr0' (6a46a9d3-2afd-40d3-95c4-b04546afc4bd)
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0543] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0546] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0547] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.0549] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.1436] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.1440] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Oct 25 17:59:23 localhost.localdomain NetworkManager[908]: <info>  [1666735163.1444] device (virbr0): Activation: successful, device activated.
Oct 25 17:59:26 localhost.localdomain NetworkManager[908]: <info>  [1666735166.1206] agent-manager: agent[a7b243cd931b65fe,:1.65/org.gnome.Shell.NetworkAgent/42]: agent registered
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3409] device (enp9s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3423] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <warn>  [1666735193.3430] device (enp9s0): Activation: failed for connection 'eth1'
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3435] device (enp9s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3844] dhcp4 (enp9s0): canceled DHCP transaction
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3875] policy: auto-activating connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3887] device (enp9s0): Activation: starting connection 'eth1' (885d4564-34a6-4f94-9b17-28fef0f89f45)
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3891] device (enp9s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3895] manager: NetworkManager state is now CONNECTING
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.3903] device (enp9s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.4153] device (enp9s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 25 17:59:53 localhost.localdomain NetworkManager[908]: <info>  [1666735193.4157] dhcp4 (enp9s0): activation: beginning transaction (timeout in 45 seconds)
Oct 25 17:59:58 localhost.localdomain NetworkManager[908]: <info>  [1666735198.0121] agent-manager: agent[999710b422741d4d,:1.232/org.gnome.Shell.NetworkAgent/1000]: agent registered

I disabled the default network and manually removed the IP from virbr0 and set the link to down on the host machine before starting up the VM. NM seems to still want to use virbr0 though.

$ nmcli con show
NAME    UUID                                  TYPE    DEVICE 
virbr0  a7c297f8-286f-4f98-9bd4-90d73f6e9956  bridge  virbr0 

Let me know if that should point me in a specific direction. Thanks so much for your time.

Last edited by rakehandle (2022-10-26 01:10:19)