Ubuntu Cloud Minimal Fails To Boot From Default Display

[mstarks01]

I have seen other boot failure threads, but they typically seem to be related to a failed upgrade or migration of some sort. My problem is much more concise.

When booting Ubuntu 20.0.4 from either the default display or Spice, the message Booting from Hard Disk... is displayed and the VM fails to boot. It will only boot with a serial console, but since that has much to be desired, I can't even use vim effectively to enable SSH login.

The disk was imported from the ubuntu-20.04-minimal-cloudimg-amd64.img image file provided by Ubuntu.

Hardware:

bootdisk: scsi0
cipassword:
ciuser: me
cores: 1
ide2: none,media=cdrom
memory: 1024
name: Ubuntu-Cloud-Minimal-20.04
net0: virtio=56:FC:02:AC:7E:1E,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-106-disk-0,size=2252M
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=f3c62e96-7f4f-47a1-a978-989054f1c0d4
sockets: 1
vga: qxl
vmgenid: 4bb049a2-b91a-4f6d-b94d-2f384dc0dea

PVE Info:

root@holodeck:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 14.2.16-pve1
ceph-fuse: 14.2.16-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

 

[mstarks01]

Just a follow-up here. I realized that the system does actually boot, but the display seems to freeze on that message with those displays.