Support and News Forum

Hello!

i test nested virtualization in EVE

HOST(Sandy Bridge 2630L) -> EVE-NG(5ver) -> ESXI -> Create VM -> Power On ( Failed )

qemu-system-x86_64 -m 2048 -enable-kvm -cpu host
Unable to init server: Could not connect: Connection refused
qemu-system-x86_64: error: failed to set MSR 0x48f to 0x7fffff00036dfb
qemu-system-x86_64: /build/qemu-0Dw8aG/qemu-4.2/target/i386/kvm.c:2691: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
Aborted (core dumped)

and i have old EVE (same host)

root@EVESDK:~# qemu-system-x86_64 -m 2048 -enable-kvm -cpu host
Could not initialize SDL(No available video device) - exitin

root@EVESDK:/opt/unetlab/addons/qemu/exsi-nested-7.0u3c# 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 'devices' controller support : PASS
QEMU: Checking for cgroup 'devices' controller mount-point : PASS
QEMU: Checking for cgroup 'net_cls' controller support : PASS
QEMU: Checking for cgroup 'net_cls' 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 DMAR 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 'devices' controller support : PASS
LXC: Checking for cgroup 'devices' controller mount-point : PASS
LXC: Checking for cgroup 'net_cls' controller support : PASS
LXC: Checking for cgroup 'net_cls' controller mount-point : PASS
LXC: Checking for cgroup 'freezer' controller support : PASS
LXC: Checking for cgroup 'freezer' controller mount-point : PASS

i trying ALL settings

echo 'vhv.enabled = "TRUE"'
echo 'vmx.allowNested = "TRUE"'
echo 'monitor.allowLegacyCPU = "TRUE"'
echo 'featMask.vm.hv.capable = "Min:1"'

etc

all combination - result - VM inside ESXi, does not work ( VT-d platfrom is not supported )

Do you understand what you are asking !!!

It is almost impossible because it is 3 layer virtualization!

Your native ESXI Server and EVE VM on it (1st virtualization)
EVE itself is acting like hypervisor. Node on EVE is 2nd virtualization layer.
and VM on EVE node as esxi is 3rd virtualization then !!!

turn on virtualization in such layer is simply impossible.
I had success to test v motion on lab below, but for sure not 3rd nested virtualization, also it will be very slow
I used Slax linux OVA for this test, you will find it under folde Small ova

https://mega.nz/folder/30p3TKob#42_S__9wwPVO0zHIfC4xow