[SOLVED] VM failed to start

[oldfart]

Proxmox 8.0.3
New download of ubuntu server iso
start failed: QEMU exited with code 1
Any ideas?

200.conf
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
ide2: local:iso/ubuntu-22.04.2-live-server-amd64.iso,media=cdrom,size=1929660K
memory: 2048
meta: creation-qemu=8.0.2,ctime=1690465431
name: ubuntuserver
net0: virtio=D6:BE:CF:BE:20:E4,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-zfs:vm-200-disk-0,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=4c5b4e53-7449-4f8b-9fa7-747299e1ad6b
sockets: 1
vmgenid: d5e82092-d8b1-42e3-80d4-8322b3197223

syslog

Jul 27 14:43:51 pve pvedaemon[3072]: <root@pam> starting task UPID:pve:000380AB:000959BE:64C27497:qmcreate:200:root@pam:
Jul 27 14:43:52 pve pvedaemon[3072]: <root@pam> end task UPID:pve:000380AB:000959BE:64C27497:qmcreate:200:root@pam: OK
Jul 27 14:44:07 pve pvedaemon[230126]: start VM 200: UPID:pve:000382EE:00096033:64C274A7:qmstart:200:root@pam:
Jul 27 14:44:07 pve pvedaemon[3072]: <root@pam> starting task UPID:pve:000382EE:00096033:64C274A7:qmstart:200:root@pam:
Jul 27 14:44:08 pve systemd[1]: Started 200.scope.
Jul 27 14:44:09 pve kernel: device tap200i0 entered promiscuous mode
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered blocking state
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered disabled state
Jul 27 14:44:09 pve kernel: device fwpr200p0 entered promiscuous mode
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered blocking state
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered forwarding state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered blocking state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered disabled state
Jul 27 14:44:09 pve kernel: device fwln200i0 entered promiscuous mode
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered blocking state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered forwarding state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 2(tap200i0) entered blocking state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 2(tap200i0) entered disabled state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 2(tap200i0) entered blocking state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 2(tap200i0) entered forwarding state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 2(tap200i0) entered disabled state
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered disabled state
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered disabled state
Jul 27 14:44:09 pve kernel: device fwln200i0 left promiscuous mode
Jul 27 14:44:09 pve kernel: fwbr200i0: port 1(fwln200i0) entered disabled state
Jul 27 14:44:09 pve kernel: device fwpr200p0 left promiscuous mode
Jul 27 14:44:09 pve kernel: vmbr0: port 6(fwpr200p0) entered disabled state
Jul 27 14:44:10 pve pvedaemon[3073]: VM 200 qmp command failed - VM 200 not running
Jul 27 14:44:10 pve pvestatd[3007]: VM 200 qmp command failed - VM 200 not running
Jul 27 14:44:10 pve systemd[1]: 200.scope: Deactivated successfully.
Jul 27 14:44:10 pve systemd[1]: 200.scope: Consumed 1.428s CPU time.
Jul 27 14:44:10 pve pvedaemon[230126]: start failed: QEMU exited with code 1
Jul 27 14:44:10 pve pvedaemon[3072]: <root@pam> end task UPID:pve:000382EE:00096033:64C274A7:qmstart:200:root@pam: start failed: QEMU exited with code 1

 

[Philipp Hufnagl]

do you get more output when you do journalctl -b and then attempt to start?

 

[oldfart]

do you get more output when you do journalctl -f and then attempt to start?

No - exactly the same output as syslog
Getting the same error installing Debian in a VM
Very strange
Now having the same issue creating a container, I can clone an existing, but not create new

 

[oldfart]

solved .. CPU type is wrong
although the Wiki

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines

reports that
x86-64-v2-AES: Compatible with Intel CPU >= Westmere
my CPUs are 2 x Xeon X5650, the VM will not start
So, something is wrong, the wiki, or something in Proxmox is not working correctly

 

[oldfart]

solved .. CPU type is wrong
although the Wiki

https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines

reports that
x86-64-v2-AES: Compatible with Intel CPU >= Westmere
my CPUs are 2 x Xeon X5650, the VM will not start
So, something is wrong, the wiki, or something in Proxmox is not working correctly

Further info
AES-NI was disabled on my Supermicro Bios!, now enabled & can create & run VMs