Score:0

MAAS 2.9: KVM VMs not booting, how to add them to the "bond0"?

in flag

I just set up a system with MAAS 2.9. I have several servers with the following network config: Network

I deployed them as KVM hosts.

When I now try to add a VM to one host, it never boots, it gets stuck on PXE: Stuck

When I ssh into the host, this is what ifconfig -a gives me:

bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 121213  bytes 8631180 (8.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 21694  bytes 7224074 (7.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-bond0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet REDACTED  netmask 255.255.248.0  broadcast 10.93.111.255
        inet6 REDACTED  prefixlen 64  scopeid 0x20<link>
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 120738  bytes 6841216 (6.8 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 19005  bytes 7068956 (7.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 153

eno2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 189

eno33np0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 62019  bytes 4414557 (4.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10833  bytes 3604626 (3.6 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno34np1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether REDACTED  txqueuelen 1000  (Ethernet)
        RX packets 59194  bytes 4216623 (4.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10861  bytes 3619448 (3.6 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 352  bytes 31676 (31.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 352  bytes 31676 (31.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:9c:98:0d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:9c:98:0d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:fee6:472a  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:e6:47:2a  txqueuelen 1000  (Ethernet)
        RX packets 14  bytes 2544 (2.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 739  bytes 49428 (49.4 KB)
        TX errors 0  dropped 12059 overruns 0  carrier 0  collisions 0

virsh net-list gives me:

 Name      State    Autostart   Persistent
--------------------------------------------
 default   active   yes         yes

virsh net-dumpxml default gives me:

<network>
  <name>default</name>
  <uuid>cefb637b-9b45-4407-b458-ac0445aa900d</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='virbr0' stp='on' delay='0'/>
  <mac address='52:54:00:9c:98:0d'/>
  <ip address='192.168.122.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.122.2' end='192.168.122.254'/>
    </dhcp>
  </ip>
</network>

So it seems that there is a second network with IP addresses 192.168.122.x. How do I change the configuration so that this is bridged to my main network (bond0)?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.