VirtualBox

Opened 5 years ago

Last modified 5 years ago

#18747 new defect

vt-x imbricate grayed

Reported by: Sizy458 Owned by:
Component: other Version: VirtualBox 6.0.8
Keywords: Cc:
Guest type: other Host type: other

Description

Hello,
I have AMD processor , the checkbox 'VT-X imbricate' is accessible on the host machine
okay

When i install virtualbox on the guest machine virtualbox , then VT-X is recognized
but 'VT-X imbricate' is grayed on virtualbox installed on the

guest machine Virtualbox.


Thank.

Change History (4)

comment:1 by Sizy458, 5 years ago

Pardon I write by error word 'Imbricate' instead of 'nested' excuse-me

Hello,

I have AMD processor , the checkbox 'VT-X nested' is accessible on the host machine okay

When i install virtualbox on the guest machine virtualbox , then VT-X is recognized

but 'VT-X nested' is grayed on virtualbox installed on the

guest machine Virtualbox.


Thank.

Last edited 5 years ago by Sizy458 (previous) (diff)

comment:2 by Socratis, 5 years ago

So, let me understand it. It would help if you could 1) switch to English and 2) use the exact wording as it shows in the dialogs...

  • You installed VirtualBox on your host. The "Enable Nested VT-x/AMD-V" is available and checked.
  • You then installed VirtualBox on your guest. The "Enable Nested VT-x/AMD-V" is not available and it's greyed out.

Is that the problem?

comment:3 by Sizy458, 5 years ago

yes

comment:4 by Socratis, 5 years ago

It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

Plus a discussion and analysis on the bug tracker is going to help me, you, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

So, please open a new thread in the Using VirtualBox section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

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) / Create-Observe problem / 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 post in the forums.

Please do that both for the host and the guest.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use