QEMU exited with code 1 during install of VMs

[hammerhead8599]

I was getting this error as I tried installing Ubuntu 20.04 .iso and 22.04 .iso but kept receiving the above error as I tried starting the install. After reading several dozen posts concerning the same problem, I stumbled on a request in one that I didn't see anywhere else so I tried it. I double clicked on the tasks log at the bottom of the proxmox page and received the following info.

kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
kvm: Host doesn't support requested features
TASK ERROR: start failed: QEMU exited with code 1

As I once again built the VM the CPU defaulted to {x86-64-v2-AES}. On a whim I changed the CPU selection to {x86-64-v2} and the install started as it should have.
I am going to retry the install to see if that solves the issue. I will post if this completes the install process properly.

Thank you

 

[hammerhead8599]

UPDATE.... the next day and I am still up and running. Not sure if my issue is hardware related or not. I am running PM on a Dell R710. I have another R710 running PM and the VMs all have the vCPU set at {x86-64-v2-AES}. These are all Ubuntu based VMs and run fine. If any of you are curious and wish to do some bug chasing, please message me and I'll send in whatever logs or info to help others troubleshoot this issue

 

[beisser]

if the aes cpu doesnt work it simply means you are running a processor on that host that doesnt support aes-ni.
if you tell us what cpu is in your two r710 (working and nonworking one) we can lookup the specs.
im sure we will find that the nonworking one has a cpu that doesnt support it.

 

[sb-jw]

Either you don't have AES-NI enabled in the BIOS or you have an old BIOS or motherboard that doesn't support it. If in doubt, you could also try a BIOS reset, that might also help.

It most likely won't be the CPU's fault, as even an E5603 can do AES-NI.

 

[beisser]

seems like you are correct. we do have some old r710 around and i just checked their cpu's (some e-, some x-xeons) and they all support aes-ni.
so yeah, most likely its disabled somehow.