Hi!
I am running latest version of VB Version 5.1.28 r117968 (Qt5.5.1) on Linux Mint 18.2 Cinamon Edition with latest Guest Utils installed and the following kernel installed:
Linux linux-desktop 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
My Linux Host has VM-X enabled. See attached file cpuinfo, but my VirtualBox image does not enable VM-X, even thought I have selected it in the config.
Can not see it if I do
cat /proc/cpuinfo | grep vmx
on the virtual machines.
Please see attached OpenNebula-Frontend1.vbox for details.
I also included VBox.log file.
This is true for all other VM:s I am using.
VM-X not activated in VM:s
-
- Posts: 4
- Joined: 18. Sep 2017, 21:00
VM-X not activated in VM:s
- Attachments
-
- VM-X.zip
- Files described in message
- (17.46 KiB) Downloaded 4 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VM-X not activated in VM:s
Hardware virtualization ( VT-x/AMD-v ) is not passed through to the guest so what you see is in fact accurate.
-
- Posts: 4
- Joined: 18. Sep 2017, 21:00
Re: VM-X not activated in VM:s
Thank you for your answer.
If that is the case, why do you have the option to configure VT-x/AMD-v for the VM if that is not supported?
If that is the case, why do you have the option to configure VT-x/AMD-v for the VM if that is not supported?
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VM-X not activated in VM:s
I assume you mean for the original guest. The option is there to control whether or not the guest will be allowed to access that feature from the hosts processor, but it does not get passed through as a feature on the guest.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VM-X not activated in VM:s
VT-x is used by the VM, not by the guest OS. It is useful to make yourself aware of the distinction. I.e. the VM is an application running on the host.Thunderlight1 wrote:If that is the case, why do you have the option to configure VT-x/AMD-v for the VM if that is not supported?
-
- Posts: 4
- Joined: 18. Sep 2017, 21:00
Re: VM-X not activated in VM:s
Thank you for the clarification.