So i had a working VMware environment with VMWare ESXI up until a few months ago. For various reasons it was abandoned for a time. Now i can't seem to get VMWare ESXi to start any VM's at all. It will install and start up fine, but isn't really usable. I keep getting a error message when i try to start any VM's that indicates VMware is having a issue with the system it is running on running another VM Software. I have tried rebuilding the several times and following whatever tutorials i can find online to install VMWare 7.x. I have tried 7.01 and 7.03g. I have tried using SEABIOS which seems to now cause a error during startup and OVMF with and without TPM.
I have not made any progress. I have attempted again today to try to get this working manipulating a few things. Now I am just going to focus on ESXI 8.0. It generates that strange message about: AMD-V is supported by the platform, but is implemented in a way that is incompatible. What is strange is that i can't get ESXi 7.x working either which was working a while back.
I have confirmed the platform works as expected if using ESXI on Bare Metal instead of Unraid. For testing i switched my box to boot into ESXi first and then run Unraid underneath ESXi. This kind of worked for testing, but complications with PCIe Passtrough requirements caused me to move away from running ESXi as the main hypervisor.
So I got out my old Unraid server hardware and got it in a working state, then got Unraid running on it. Tested it with trying to run VMware ESXi7.0 on it as this older hardware doesn't support ESXi8.0 and it seems to have worked. It doesn't say much though as that older hardware is a Sandybridge Intel Chip that is rather dated at this point.
<topology sockets='1' dies='1' cores='2' threads='2'/>
<cache mode='passthrough'/>
<feature policy='require' name='topoext'/>
cpuid level : 16
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm art rep_good nopl extd_apicid eagerfpu pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat npt lbrv nrip_save tsc_scale vmcb_clean pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq spec_ctrl intel_stibp arch_capabilities
bogomips : 6787.24
TLB size : 2560 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management:
Further update....
I have built a CentOS 7.8 VM and have looked at the contents of /proc/cpuinfo:
The output is below:
processor : 0vendor_id : AuthenticAMDcpu family : 25model : 33model name : AMD Ryzen 9 5950X 16-Core Processorstepping : 0microcode : 0xa201016cpu MHz : 3393.622cache size : 512 KBphysical id : 0siblings : 2core id : 0cpu cores : 1apicid : 0initial apicid : 0fpu : yesfpu_exception : yescpuid level : 16wp : yesflags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm art rep_good nopl extd_apicid eagerfpu pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext perfctr_core retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat npt lbrv nrip_save tsc_scale vmcb_clean pausefilter pfthreshold v_vmsave_vmload vgif umip pku ospke vaes vpclmulqdq spec_ctrl intel_stibp arch_capabilitiesbogomips : 6787.24TLB size : 2560 4K pagesclflush size : 64cache_alignment : 64address sizes : 48 bits physical, 48 bits virtualpower management:
As you can see, the SVM flag (along with many others) is being passed through to the VM. I'm going to dive deeper to see if there are any other flags that are potentially missing causing the errors in ESXi.
@afc_rich
what does your xml for the VM look like? Anything special? I added require SVM to my windows 11 VM and could not launch a hyper-v manager vm and coreinfo did not detect svm
Options from CPU below, it has been confirmed by others that they have been able to get nested virtualization to work on windows 11
Sent from my SM-G996U using Tapatalk
[root@centos /]# sudo virt-host-validate
QEMU: Checking for hardware virtualization : PASS
QEMU: Checking if device /dev/kvm exists : PASS
QEMU: Checking if device /dev/kvm is accessible : PASS
QEMU: Checking if device /dev/vhost-net exists : PASS
QEMU: Checking if device /dev/net/tun exists : PASS
QEMU: Checking for cgroup 'memory' controller support : PASS
QEMU: Checking for cgroup 'memory' controller mount-point : PASS
QEMU: Checking for cgroup 'cpu' controller support : PASS
QEMU: Checking for cgroup 'cpu' controller mount-point : PASS
QEMU: Checking for cgroup 'cpuacct' controller support : PASS
QEMU: Checking for cgroup 'cpuacct' controller mount-point : PASS
QEMU: Checking for cgroup 'cpuset' controller support : PASS
QEMU: Checking for cgroup 'cpuset' controller mount-point : PASS
QEMU: Checking for cgroup 'devices' controller support : PASS
QEMU: Checking for cgroup 'devices' controller mount-point : PASS
QEMU: Checking for cgroup 'blkio' controller support : PASS
QEMU: Checking for cgroup 'blkio' controller mount-point : PASS
QEMU: Checking for device assignment IOMMU support : WARN (No ACPI IVRS table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
LXC: Checking for Linux >= 2.6.26 : PASS
LXC: Checking for namespace ipc : PASS
LXC: Checking for namespace mnt : PASS
LXC: Checking for namespace pid : PASS
LXC: Checking for namespace uts : PASS
LXC: Checking for namespace net : PASS
LXC: Checking for namespace user : PASS
LXC: Checking for cgroup 'memory' controller support : PASS
LXC: Checking for cgroup 'memory' controller mount-point : PASS
LXC: Checking for cgroup 'cpu' controller support : PASS
LXC: Checking for cgroup 'cpu' controller mount-point : PASS
LXC: Checking for cgroup 'cpuacct' controller support : PASS
LXC: Checking for cgroup 'cpuacct' controller mount-point : PASS
LXC: Checking for cgroup 'cpuset' controller support : PASS
LXC: Checking for cgroup 'cpuset' controller mount-point : PASS
LXC: Checking for cgroup 'devices' controller support : PASS
LXC: Checking for cgroup 'devices' controller mount-point : PASS
LXC: Checking for cgroup 'blkio' controller support : PASS
LXC: Checking for cgroup 'blkio' controller mount-point : PASS
LXC: Checking if device /sys/fs/fuse/connections exists : FAIL (Load the 'fuse' module to enable /proc/ overrides)
The same issue here, I have one VM with Vmware which use one time of 3 mounts, and last time after may be 6.11.X update face same error.
Nothing is changed to the VM or config, he is stopped all the time its only powered on when its need. I try with some xml custom config with no success. It's important to note, I do BIOS update and Unraid update, before that all work fine.
After some searching it turns out that pre-2011 AMD's version of AMD-V botched the VMCB flags and didn't include the proper virtualization parameters. My best guess at the moment is that the QEMU version in UnRAID 6.11.x is for some reason implementing an extremely outdated version of AMD-V that is getting passed through...when they were doing it properly before. No amount of XML flags seems to fix the issue.
You can post now and register later.
If you have an account,
sign in now
to post with your account.
Note:
Your post will require moderator approval before it will be visible.
