Network connection in VM failing

Ask Fedora
1

Okay, but the wired connection keeps failing as no connection is shown. Why is that?
If it helps: I noticed when I boot the VM it shows:
“Failed to start network manager wait online”
Maybe it has something to do with this. Anyway, there is no wired connection showing. Do I have to do something else for it or should it just work?

2

This topic was split off from another topic. Please be so kind and provide some information, such as

  • host OS,
  • guest OS,
  • virtualization software (Gnome Boxes, virt-manager, …),
  • type/configuration of your virtual network adapter
  • guest os (error) logs (how to find them: Viewing logs in Fedora :: Fedora Docs)

Yes, it should just work out the box, could be that you misconfigured the virtual network interface in your virtualization software.

1 Like
3

Thanks.

  1. Fedora 34
  2. Fedora 34
  3. virt-manager
  4. I once tried Bridge device + virbr0 + virtio and once NAT + virtio
    Side note: No IP address is shown for either, it just says “Unknown”
    (QEMU/KVM Connection Details say: default, virbr0, active, on boot).
  5. I hope the logs for journalctl are okay. If somebody needs other ones, please tell me.
    Side note: I’m not sure if this plays a role here but I’ll mention it again:
    I noticed that when I boot the VM, it says “Failed to start network manager wait online”.
    Perhaps it has something to do with this.
- Journal begins at Tue 2021-09-07 18:44:13 EDT, ends at Tue 2021-09-07 18:57:19 EDT. --
Sep 07 18:44:13 fedora kernel: Linux version 5.11.12-300.fc34.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc>
Sep 07 18:44:13 fedora kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.11.12-300.fc34.x86_64 root=UUID=49dfac7>
Sep 07 18:44:13 fedora kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 07 18:44:13 fedora kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 07 18:44:13 fedora kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 07 18:44:13 fedora kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 07 18:44:13 fedora kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' form>
Sep 07 18:44:13 fedora kernel: BIOS-provided physical RAM map:
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007ffdbfff] usable
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x000000007ffdc000-0x000000007fffffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
Sep 07 18:44:13 fedora kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
Sep 07 18:44:13 fedora kernel: NX (Execute Disable) protection: active
Sep 07 18:44:13 fedora kernel: SMBIOS 2.8 present.
Sep 07 18:44:13 fedora kernel: DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2.fc34 04/01/2014
Sep 07 18:44:13 fedora kernel: Hypervisor detected: KVM
Sep 07 18:44:13 fedora kernel: kvm-clock: Using msrs 4b564d01 and 4b564d00
lines 1-23
4

Would you post the output of “ip address” from the host, then again from the VM.

my host shows

$ ip address show dev virbr0
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:31:29:bb brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.1/24 brd 192.168.124.255 scope global virbr0
       valid_lft forever preferred_lft forever


$ ip route
default via 192.168.2.1 dev wlp4s0 proto dhcp metric 600 
192.168.2.0/24 dev wlp4s0 proto kernel scope link src 192.168.2.111 metric 600 
192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1

and on the VM

$ ip address show
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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:e8:30:68 brd ff:ff:ff:ff:ff:ff
    inet 192.168.124.153/24 brd 192.168.124.255 scope global dynamic noprefixroute enp1s0
       valid_lft 3171sec preferred_lft 3171sec
    inet6 fe80::5ed9:5a59:cf48:f145/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:d1:c6:2a brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever

$ ip route
default via 192.168.124.1 dev enp1s0 proto dhcp metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 
192.168.124.0/24 dev enp1s0 proto kernel scope link src 192.168.124.153 metric 100

Note that the VM has enp1s0 configured as the interface that matches the virbr0 interface IP on the host.

I configured it as bridged at the time of install and it just worked. I have not been able to figure out how to make changes in that config after the install was complete (but then if it works why break it). :thinking: