Invalid setting detected
-
- Posts: 10
- Joined: 10. May 2020, 00:52
Invalid setting detected
Hi,
My base OS is Ubuntu 20.
On it I have VirtualBox.
virtualbox-6.1_6.1.6-137129~Ubuntu~eoan_amd64.deb
I have installed whonix (anonymity os) inside the first virtualbox.
I then have another virtualbox installed on whonix [workstation] .
In that VirtualBox I am trying to run Kali Linux.
I have tried both using the IOS and the .OVA files.
I keep getting the same error message.
When I try to correct it using the given directions the OK button
to save the changed settings remains grayed out so I can't make and save the new setting.
Then when I start virtual machine with invalid settings detected error I get this VT error.
<quote> "
Failed to open a session for the virtual machine Kali-Linux-2020.1-vbox-i386.
VT-x is not available (VERR_VMX_NO_VMX).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Invalid settings detected
System Acceleration Page
The hardware virtualization is enabled in the acceleration section of the system Page
Although it is not supported by the host system.
It should be disabled in order to start virtual system. "</quote>
My base OS is Ubuntu 20.
On it I have VirtualBox.
virtualbox-6.1_6.1.6-137129~Ubuntu~eoan_amd64.deb
I have installed whonix (anonymity os) inside the first virtualbox.
I then have another virtualbox installed on whonix [workstation] .
In that VirtualBox I am trying to run Kali Linux.
I have tried both using the IOS and the .OVA files.
I keep getting the same error message.
When I try to correct it using the given directions the OK button
to save the changed settings remains grayed out so I can't make and save the new setting.
Then when I start virtual machine with invalid settings detected error I get this VT error.
<quote> "
Failed to open a session for the virtual machine Kali-Linux-2020.1-vbox-i386.
VT-x is not available (VERR_VMX_NO_VMX).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Invalid settings detected
System Acceleration Page
The hardware virtualization is enabled in the acceleration section of the system Page
Although it is not supported by the host system.
It should be disabled in order to start virtual system. "</quote>
Last edited by vbuseruservb on 10. May 2020, 06:35, edited 2 times in total.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Invalid setting detected
On https://www.virtualbox.org/wiki/Linux_Downloads there is no download for Ubuntu 20 yet, so you're using the Ubuntu fork of Virtualbox, which we would't have the knowledge to support.
You would also at least have to zip and post both guest vbox.logs, then we might have more data to make a guess.
You would also at least have to zip and post both guest vbox.logs, then we might have more data to make a guess.
-
- Volunteer
- Posts: 5105
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Invalid setting detected
Nested virtualization (running a vm inside a vm) is a new feature and may not be reliable yet.
The error message is telling you that hardware virtualization is not available to the nested vm. That does not surprise me.
Whether you can change the setting in the vm and have the nested vm run without it depends on the version of VirtualBox you are using. In the latest versions, the old emulation software has been removed, so you cannot fall back. The vm guest must have access to VT-x or AMD-V.
The error message is telling you that hardware virtualization is not available to the nested vm. That does not surprise me.
Whether you can change the setting in the vm and have the nested vm run without it depends on the version of VirtualBox you are using. In the latest versions, the old emulation software has been removed, so you cannot fall back. The vm guest must have access to VT-x or AMD-V.
Bill
-
- Posts: 10
- Joined: 10. May 2020, 00:52
Re: Invalid setting detected
My first Virtual Box on Ubuntu 20 is
virtualbox-6.1_6.1.6-137129~Ubuntu~eoan_amd64.deb
with whonix workstation installed
build 6.1.6_ubuntu r137129
The Second virtual Box installed on whonix workstation at the moment is
Version 6.1.4 r136177 (Qt5.6.1) running on it.
I previously had build 6.1.6_ubuntu r137129 installed as the second virtual box
but still same error.
I thought if I try an earlier version I may be able to rectify the error but no luck.
The behaviour is same with both versions.
virtualbox-6.1_6.1.6-137129~Ubuntu~eoan_amd64.deb
with whonix workstation installed
build 6.1.6_ubuntu r137129
The Second virtual Box installed on whonix workstation at the moment is
Version 6.1.4 r136177 (Qt5.6.1) running on it.
I previously had build 6.1.6_ubuntu r137129 installed as the second virtual box
but still same error.
I thought if I try an earlier version I may be able to rectify the error but no luck.
The behaviour is same with both versions.
-
- Volunteer
- Posts: 5105
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Invalid setting detected
You need to enable nested virtualization in the settings of the first vm which is hosting your nested vm so that it can expose it to its vm. See the manual Chapter 9.33 .
Bill
-
- Posts: 10
- Joined: 10. May 2020, 00:52
Re: Invalid setting detected
I believe you have identified the issue.
The only problem is "Enable Nested VT-x/AMD-V "
is grayed out and I can't select it on my machine.
www<dot>virtualbox<dot>org<slash>manual<slash>ch09.html -> I can't do URI
There is chapter 9.3.1 & 9.3.2 then 9.4 hot plugging but not 9.3.3 or 9.33
The only problem is "Enable Nested VT-x/AMD-V "
is grayed out and I can't select it on my machine.
www<dot>virtualbox<dot>org<slash>manual<slash>ch09.html -> I can't do URI
There is chapter 9.3.1 & 9.3.2 then 9.4 hot plugging but not 9.3.3 or 9.33
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Invalid setting detected
Then you'll not be able to use nested virtualization on this machine. The VBox.log file that you didn't post would show the details needed for an explanation.vbuseruservb wrote:The only problem is "Enable Nested VT-x/AMD-V "
is grayed out and I can't select it on my machine.
And chapter 9.33 is the second but last chapter. Look closely.
-
- Posts: 10
- Joined: 10. May 2020, 00:52
Re: Invalid setting detected
Please find attached zip file of Logs.
1st VirtualBox log file Whonix-Workstation-VBox.log
1st VirtualBox log file Whonix-Workstation-VBox.log
- Attachments
-
- vblog.zip
- (69.01 KiB) Downloaded 119 times
-
- Posts: 10
- Joined: 10. May 2020, 00:52
Re: Invalid setting detected: Solved issue closed
Hi,
Looking through the documents as per your directions.
I ran the command
VBoxManage modifyvm Whonix-Workstation-XFCE --nested-hw-virt on
and I have gone past that error, it is now trying to install.
next I think I have to go back and re install the 64 bit version virtual machines & ISO.
With the previous error I didn't have the option only 32 bit.
The error is saying use the correct kernel for the CPU.
So thanks you.
This Issue closed.
Looking through the documents as per your directions.
I ran the command
VBoxManage modifyvm Whonix-Workstation-XFCE --nested-hw-virt on
and I have gone past that error, it is now trying to install.
next I think I have to go back and re install the 64 bit version virtual machines & ISO.
With the previous error I didn't have the option only 32 bit.
The error is saying use the correct kernel for the CPU.
So thanks you.
This Issue closed.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Invalid setting detected
AFAIK, the VirtualBox Manager will prevent setting the Enable Nested VT-x/AMD-V checkbox, if any of those 4 CPU features is not available(*). This can be circumvented (in VirtualBox 6.1.6 at least) with the VBoxManage modifyvm <vm name> --nested-hw-virt on command, but then VirtualBox will still not be provide the EPT and UnrestrictedGuest features to the first level guest. In consequence, I'd expect the second level guest to be quite slow.VBox.log file wrote:00:00:01.017651 Nested hardware virtualization - VMX features 00:00:01.017651 Mnemonic - Description = guest (host) 00:00:01.017651 VMX - Virtual-Machine Extensions = 0 (1) 00:00:01.017665 Ept - Extended Page Tables = 0 (1) 00:00:01.017668 UnrestrictedGuest - Unrestricted guest = 0 (1) 00:00:01.017671 VmcsShadowing - VMCS shadowing = 0 (0)
(*) Many newer (8th/9th gen) mobile Intel CPUs are missing the VMCS Shadowing feature. I've verified this on my own notebook and in several threads on the VirtualBox forums so far.
-
- Volunteer
- Posts: 5105
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Invalid setting detected
Why are you surprised? In the reply to your previous post on this same topic, you were told it would be slow!
Nested virtualisation is still in its early stages (especially on an Intel CPU). It certainly does not work very well for me on an I7-7700 .
Nested virtualisation is still in its early stages (especially on an Intel CPU). It certainly does not work very well for me on an I7-7700 .
Bill
Re: Invalid setting detected
Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!
(VERR_CPUM_INVALID_HWVIRT_CONFIG).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
i have enable but it show this issue .what is the best solN for it ??
(VERR_CPUM_INVALID_HWVIRT_CONFIG).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
i have enable but it show this issue .what is the best solN for it ??
Re: Invalid setting detected
Failed to open a session for the virtual machine GNS3 VM.
Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!
(VERR_CPUM_INVALID_HWVIRT_CONFIG).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!
(VERR_CPUM_INVALID_HWVIRT_CONFIG).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Invalid setting detected
Please post a zipped VBox.log file from a VM run showing the error.