VMX is not reconized

[Sizy458]

Windows 10 in Guest machine work good , But in guest machine the VMX is not recognized
Virtualbox don't define instruction VMWRITE,VMREAD,.... for the guest machine
VT-X work good on my host machine and == don't work == on guest machine.

[Ramshankar Venkataraman]

VirtualBox does not yet support nested hardware-virtualization feature on Intel CPUs. Nested hardware-virtualization is only available on AMD CPUs starting with VirtualBox 6.0.0.

[Sizy458]

Let me explain
I would like to virtualize a guest machine on a guest virtualbox machine.

[Socratis]

Let me summarize what 'ramshankar' said:

You can't! Not with an Intel CPU, only with an AMD one.

So, unless you have an AMD CPU, this ticket is not valid I'm afraid.

[Sizy458]

However I have cpu AMD in the host machine.

[Socratis]

You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

We need to see a complete VBox.log, from a complete VM run, when the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe issue / Shutdown the VM (force close it if you have to).

• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".

• Save only the first "VBox.log" and attach it to your response.

[Sizy458]

I have checked "Vt-X imbricate" it work good !

BUT !

the checkbox 'VT-x imbricate' is grayed on VirtualBox installed on guest machine VirtualBox

with "Vt-x imbricate" checked in the host machine

[Socratis]

Replying to Sizy458:

I have checked "Vt-X imbricate" it work good ''

This ticket can then be closed as [Invalid] or [WorksForMe].

BUT

Your "But..." is now ticket #18747, so this ticket can be definitely closed.