I have been testing Fedora 30 Server edition in a virtual machine and now I would like to place the NIC in bridged mode so the VM appears on the same subnet as the rest of my physical devices.
So I go to my Virtual Networks in virt-manager and click the plus to add a new virtual network. I give it a name and the first odd thing I notice on step 2 is that the IP address is highlighted in red. No problem, I drop a 0 from the third octet and the highlight turns green.
On step 4 I select āForwarding to physical networkā, set the destination to āAny physical deviceā and the mode to āRoutedā. Upon clicking finish, I get a message with the following error:
Error creating virtual network: The name is not activatable
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/createnet.py", line 811, in _async_net_create
net.install()
File "/usr/share/virt-manager/virtinst/network.py", line 244, in install
net.create()
File "/usr/lib64/python3.7/site-packages/libvirt.py", line 3007, in create
if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self)
libvirt.libvirtError: The name is not activatable
Iāve done this a few times before and not experienced this error. Does anyone have experience with this sort of thing who can point me in the right direction?
That configuration window manages virtual networks which rely on virtual switches.
The bridged networking is a different mode that doesnāt involve virtual networking.
Yes. Indeed.
But, maybe, as for me, it is sufficient if the goal is to assign an IP of the LAN to the VM. Without having to tinker with network manager and so on in order to configure a bridge.