New VM is not able to start

[TwoFour]

When I try to start a new VM with all default settings that is pointed at a 'physical CD/DVD' for boot media, it does not start.
This is what I see:



A few moments ago, I had tried to create the same VM and it at least spun up the physical DVD. Then I deleted it and recreated, but it does not even spin it up now.
I tried to put different guest OS DVDs into the drive but all do the same: do not boot. Even after I uploaded the ISO image to local storage the VM still does not boot from it.

Also, as I navigate the UI, I randomly get this:


When I try to add SMB storage I get this:



It also cannot update itself for some reason:

 

[Moayad]

Hi,

Can you please post the full output of the `qm start 100` command? You can run this command in the SSH or you can post the information included in the task error `Error: start failed: QEMU existed with code 1` in the [Task Log]. Also, verify the configuration of the SMB storage if the Proxmox VE has the right permission.

 

[TwoFour]

root@pve:~# qm start 100
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.1 [bit 19]
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.sse4.2 [bit 20]
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.popcnt [bit 23]
kvm: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
kvm: Host doesn't support requested features
start failed: QEMU exited with code 1
root@pve:~#

I do not understand your suggestion:

verify the configuration of the SMB storage if the Proxmox VE has the right permission.

Do you mean to verify that the SMB share, user, and password are correct? Yes, they are.

 

[Moayad]

Could you please post the VM config? `qm config 100`

 

[TwoFour]

I changed the CPU from x86-64-AES default to kvm64 and it started.
Should not defaults be safe instead of highest possible?
I think that by 2024 we should be able to detect the CPU capabilities and not suggest a non-working default?

 

[LnxBil]

I changed the CPU from x86-64-AES default to kvm64 and it started.
Should not defaults be safe instead of highest possible?
I think that by 2024 we should be able to detect the CPU capabilities and not suggest a non-working default?

I have to say: yes, this is a bug. I just filed it.