Hi everyone.
I have been running my home production server on Ubuntu 18.04 LTS for a while now and have just rebuilt it using Ubuntu 20.04.3 LTS. For virtualisation I was previously using Virtualbox which I managed through phpVirtualbox, I have now decided to utilise KVM for my VM needs but have hit a snag while setting up.
I have installed KVM and all of the dependencies, also installed Cockpit but didnt realise that managing Windows VMs is limited, so decided to carry on with my learning and use the CLI instead.
I had successfully created a bridge br0, bridge-slave to interface enp3s4f0 and configured IP, Gateway and DNS using nmcli commands. Then successfully created my first KVM VM using virt-install and powered on. I wasnt able to connect to the VM using RDP from my desktop PC and on running ip a found the IP addresses were not what I thought Id configured. So tried again using the nmcli commands to no effect.
I then decided to remove the bridge and slave-bridge so that I could start again but this time set the bridge up using virsh commands. I created a br0.xml file to create a bridge using br0 again, contents of the xml file below.
Then ran:
However when I started br0 I get the below error message:
error: Failed to start network br0
error: internal error: Network is already in use by interface enp3s4f0
When I run ip a there are no bridge interfaces listed that suggest anything is slaved to enp3s4f0. it feels like somehow there is the previous br0 bridge I created still slaved to enp3s4f0.
Can anyone offer some advice as to how I can rectify this issue please?
Thanks
Phill
I have been running my home production server on Ubuntu 18.04 LTS for a while now and have just rebuilt it using Ubuntu 20.04.3 LTS. For virtualisation I was previously using Virtualbox which I managed through phpVirtualbox, I have now decided to utilise KVM for my VM needs but have hit a snag while setting up.
I have installed KVM and all of the dependencies, also installed Cockpit but didnt realise that managing Windows VMs is limited, so decided to carry on with my learning and use the CLI instead.
I had successfully created a bridge br0, bridge-slave to interface enp3s4f0 and configured IP, Gateway and DNS using nmcli commands. Then successfully created my first KVM VM using virt-install and powered on. I wasnt able to connect to the VM using RDP from my desktop PC and on running ip a found the IP addresses were not what I thought Id configured. So tried again using the nmcli commands to no effect.
I then decided to remove the bridge and slave-bridge so that I could start again but this time set the bridge up using virsh commands. I created a br0.xml file to create a bridge using br0 again, contents of the xml file below.
Code:
<network>
<name>br0</name>
<forward mode='nat'>
<nat>
<port start='1024' end='65535'/>
</nat>
</forward>
<bridge name='br0' stp='on' delay='0'/>
<ip address='192.168.3.187' netmask='255.255.255.0'>
</ip>
</network>Code:
sudo virsh net-define br0.xml
sudo virsh net-start br0error: Failed to start network br0
error: internal error: Network is already in use by interface enp3s4f0
When I run ip a there are no bridge interfaces listed that suggest anything is slaved to enp3s4f0. it feels like somehow there is the previous br0 bridge I created still slaved to enp3s4f0.
Can anyone offer some advice as to how I can rectify this issue please?
Thanks
Phill