S Schmukas New Member Feb 9, 2024 1 0 1 Feb 9, 2024 #1 The container wont start after a reboot an the cluster log shows this error: kvm: Hyper-V enlightened VMCS (hv-evmcs) requires Hyper-V virtual APIC (hv-vapic) TASK ERROR: start failed: QEMU exited with code 1
The container wont start after a reboot an the cluster log shows this error: kvm: Hyper-V enlightened VMCS (hv-evmcs) requires Hyper-V virtual APIC (hv-vapic) TASK ERROR: start failed: QEMU exited with code 1
Chris Proxmox Staff Member Staff member Jan 2, 2019 3,980 888 188 Feb 9, 2024 #2 Schmukas said: The container wont start after a reboot an the cluster log shows this error: kvm: Hyper-V enlightened VMCS (hv-evmcs) requires Hyper-V virtual APIC (hv-vapic) TASK ERROR: start failed: QEMU exited with code 1 Click to expand... Hi, this sounds more like you have a VM with nested virtualization, rather than a container. Please try setting the cpu type and needed cpu flags [0], also see this thread where users resolved this [1]. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cpu [1] https://forum.proxmox.com/threads/nested-virtualization-stopped-working-pve-6-1-5.64316/
Schmukas said: The container wont start after a reboot an the cluster log shows this error: kvm: Hyper-V enlightened VMCS (hv-evmcs) requires Hyper-V virtual APIC (hv-vapic) TASK ERROR: start failed: QEMU exited with code 1 Click to expand... Hi, this sounds more like you have a VM with nested virtualization, rather than a container. Please try setting the cpu type and needed cpu flags [0], also see this thread where users resolved this [1]. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cpu [1] https://forum.proxmox.com/threads/nested-virtualization-stopped-working-pve-6-1-5.64316/