Ubuntu VM - no network on first boot when using OVMF

darmach

New Member
Aug 2, 2024
2
0
1
I'm spawning an ubuntu vm from the template built from newest 24.04 image here, configs at the end of the post:
https://cloud-images.ubuntu.com/noble/currentnobleserver-cloudimg-amd64.img

On first boot of the vm it get's stuck for a minute or two at 2.087525 s with CPU usage practically zero.
Around 2 minutes later in journalctl I noticed :
Code:
ubuntu systemd-networkd-wait-online[565]: timeout occured while waiting for network connectivity.
ubuntu systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE

followed a bit later on by

Failed to start systemd-networkd-wait-online.service - Wait for Network to be Configured.

When it get's back responsive, I end up without the network.

After resetting the VM - next boot boots fine, snappy, with network.
Am I doing something wrong?

Template:
Code:
agent: enabled=1
bios: ovmf
boot: c
bootdisk: scsi0
cores: 2
cpu: cputype=host
efidisk0: local-zfs:base-1000-disk-1,size=1M
ide2: local-zfs:vm-1000-cloudinit,media=cdrom
ipconfig0: ip=dhcp
memory: 2048
meta: creation-qemu=9.0.2,ctime=1723246116
name: ubuntu-24.04
net0: virtio=BC:24:11:2F:65:FC,bridge=vmbr0
ostype: l26
scsi0: local-zfs:base-1000-disk-0,size=3584M
scsihw: virtio-scsi-pci
smbios1: uuid=2bac32c5-6e0d-4e18-8cc4-60ac7f975110
template: 1
vmgenid: ca987128-0398-4c7b-ba65-0215374568db

VM config:
Code:
agent: enabled=1
bios: ovmf
boot: c
bootdisk: scsi0
cores: 2
cpu: cputype=host
efidisk0: local-zfs:base-1000-disk-1/vm-100-disk-0,size=1M
ide2: local-zfs:vm-100-cloudinit,media=cdrom,size=4M
ipconfig0: ip=dhcp
memory: 2048
meta: creation-qemu=9.0.2,ctime=1723246116
name: ubuntu
net0: virtio=BC:24:11:6E:A2:46,bridge=vmbr0
ostype: l26
scsi0: local-zfs:base-1000-disk-0/vm-100-disk-1,size=3584M
scsihw: virtio-scsi-pci
smbios1: uuid=d40aa90a-8ec1-49fd-9d53-a9d510984001
vmgenid: dfd27ee6-cc76-4b20-a766-e83e8a414479
 
All right, leaving a reply here in case someone else will be struggling with it - the missing piece was setting the VM type to q35
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!