Configuring a second VM - Ubuntu desktop

[harpmonkey]

Hi,

Complete beginner here, so apologies in advance.

I am new to Proxmox, having just set up a NUC with a first VM running Home Assistant. I managed to follow some guides to correctly configure the initial VM with no issues - it is operating as expected.

I am now trying to spin up a second VM running Ubuntu desktop. I have looked a bunch of guides, and cannot seem to get the initialisation to work.

NUC is a new gen 11 i3, with 8gb RAM and 250gb SATA SSD

Proxmox 7.0-13, Ubuntu desktop image 20.04.03

Steps I have followed:
* download Ubuntu desktop ISO image
* add ISO image into the local drive
* apply the ISO image under CD drive
* provision memory (2gb), hard drive space, cores (2)
* q35 machine, have tried 128gb hard drive space with both Sata and SCSI option, bios OVMF

When I try to start the VM, I am getting the following Error: start failed: QEMU exited with code 1, and the VM doesn't start.

What am I missing here?

cheers

 

[dcsapak]

hi,

you can check the failed task log by double clicking on it to see the complete error message.

 

[harpmonkey]

hi,

you can check the failed task log by double clicking on it to see the complete error message.

Great, thanks! I hadn't figured that out.

This is the result:
Error: Unknown device type.
can't create interface fwln101i0 - command '/sbin/ip link add name fwln101i0 mtu 1500 type veth peer name fwpr101p0 mtu 1500' failed: exit code 2

kvm: -netdev type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 512
Use of uninitialized value $tpmpid in concatenation (.) or string at /usr/share/perl5/PVE/QemuServer.pm line 5465.
stopping swtpm instance (pid ) due to QEMU startup error
TASK ERROR: start failed: QEMU exited with code 1

Nothing that makes a lot of sense to me. Any further ideas?

cheers

 

[dcsapak]

mhmm... can you post the output of 'dmesg' as well as the output of 'lsmod |grep eth' ?

 

[harpmonkey]

By co-oincidence, just had a big storm blow through. I woke up, and we had lost power at some point - NUC was powered down.
Booted her up and - the second VM spun up fine!

Is this expected behaviour? e.g. should I have to reboot the host to trigger effective VM behaviour? Or was this just a random glitch?

 

[dcsapak]

Is this expected behaviour? e.g. should I have to reboot the host to trigger effective VM behaviour? Or was this just a random glitch?

without logs, it's hard to say what happened and why it was failing but works now...

 

[harpmonkey]

Fair enough - thanks so much for your help. I'll make sure to review those logs next time I hit a snag.

As you said - all up and running so no problem now!

I suspect it may have been something to do with bootable drives, OVMF, EFI disks based on additional tinkering, but could be wrong