Bridged Network and Virt Manager

Ask Fedora Ask in English
,
1

Hello Everyone,

I am trying to set up a bridged network to use with virt-manager. The end goal is to have my virtual machines accessible from the network so I can run a web server from one of them. The host machine is running Fedora 32 while the virtual machine is running CentOS 8. To create the bridge I used these commands:

nmcli connection add ifname br0 type bridge con-name br0 connection.zone trused
nmcli connection add type bridge-slave ifname enp4s0 master br0
nmcli connection modify br0 bridge.stp no
nmcli connection modify enp4s0 autoconnect no
nmcli connection down enp4s0
nmcli connection up id br0

Then in virt-manager I set up the “Virtual Network Interface” like:

a055f812110d49e51d5fec70ecb3a68d8991fca6.png

When I reboot the virtual machine it has no network connectivity. So I then rebooted the host and ran an ifconfig which shows the newly created bridge:

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.50.166  netmask 255.255.255.0  broadcast 192.168.50.255
        inet6 fe80::d5bf:2680:545f:1f4e  prefixlen 64  scopeid 0x20<link>
        ether 82:51:60:26:f7:6d  txqueuelen 1000  (Ethernet)
        RX packets 327  bytes 54957 (53.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 74  bytes 12637 (12.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

However, there still is no joy in the virtual machine as it refuses to connect.

86a2378e2d27180c9d2aeaa1b4fe425b90175425.png

Here is all the information about my system… fpaste

Any help or advice would be greatly appreciated!

All the best,
Jim

2

Based on what you have shown so far, it looks like everything is configured properly on the Host. Give the following from the Virtual Machine:

$ fpaste --sysinfo
$ sudo journalctl -b | fpaste
3

OK Here is the sysinfo fpaste and here is the journal -b fpaste from the Virtual Machine

4

So, it looks like the network device on the Virtual Machine is failing to gain any information from DHCP. This could be due to a routing issue, but without digging into it further, I am not able to point to anything specific.

What you may want to try is manually configuring the VM’s network interface manually and specify your network’s Gateway within the configuration so that traffic can flow normally.

If all else fails, you may want to reach out to the CentOS community for assistance with your VM, since it is CentOS.