The problem is with virtio-mmio.
https://bugzilla.redhat.com/show_bug.cgi?id=1422413
Instances launched with virtio-mmio on aarch64 will not get DHCP (will not have a nic)
xml with libvirt 2.5.0
<interface type='bridge'> <mac address='fa:16:3e:af:95:2e'/> <source bridge='qbrb5abdeb0-a0'/> <target dev='tapb5abdeb0-a0'/> <model type='virtio'/> <alias name='net0'/> <address type='virtio-mmio'/>
I have updated libvirt-daemon to 3.6.0 on a particular compute node - when an instance is booted now, the nic section of the virsh xml looks like this:
<interface type='bridge'> <mac address='fa:16:3e:10:0e:22'/> <source bridge='qbr274809a0-dc'/> <target dev='tap274809a0-dc'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
The instance then gets a NIC and is able to get DHCP and complete cloud-init successfully.
The problem is with virtio-mmio.
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1422413
Instances launched with virtio-mmio on aarch64 will not get DHCP (will not have a nic)
xml with libvirt 2.5.0
<interface type='bridge'> 'fa:16: 3e:af:95: 2e'/> 'qbrb5abdeb0- a0'/> 0-a0'/> mmio'/>
<mac address=
<source bridge=
<target dev='tapb5abdeb
<model type='virtio'/>
<alias name='net0'/>
<address type='virtio-
I have updated libvirt-daemon to 3.6.0 on a particular compute node - when an instance is booted now, the nic section of the virsh xml looks like this:
<interface type='bridge'> 'fa:16: 3e:10:0e: 22'/> 'qbr274809a0- dc'/> 0-dc'/>
<mac address=
<source bridge=
<target dev='tap274809a
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
The instance then gets a NIC and is able to get DHCP and complete cloud-init successfully.