Debian Linux gives me VERR_VMX_NO_VMX

[rkb]

I am trying to get a Linux VM up an running on my Windows 10 laptop. I downloaded a Debian iso image and pointed the VM to boot from it to install but I immediately get VERR_VMX_NO_VMX. I have gone into the BIOS and enabled VT-x (done originally to enable docker). What else am I doing wrong?

Thank you.

Kevin

[Perryg]

FAQ: I have a 64bit host, but can't install 64bit guests.

[rkb]

This is a 32-bit guest. I have stopped the Docker daemon so that is the only app that I can think is using the hardware virtualization.

[mpack]

It doesn't really matter that the guest is 32bit. The guest is clearly trying to use VT-x, which is what the FAQ discusses. The name of the FAQ merely reflects the most common form of the question.

[rkb]

I am not sure what to do now. I cleared the Hyper-V as mentioned in the app and I stopped the Docker daemon to make sure that no other apps are trying to use the hardware virtualization as mentioned in the FAQ. Any other suggestions? The FAQ also mentions disabling for EFI BIOS. I was unable to find those to disable them.

[scottgus1]

There's not much else for us to do either. All the suggestions in the tutorial pertain to the Host PC OS & BIOS. You need a BIOS and a CPU that have VT-x/AMD-V. Then you have to be sure no programs on the host are using VT-x. Hyper-V is one, there are others mentioned in the tutorial. Try uninstalling Docker, just in case.

[Perryg]

You could look at the guest and see why it is requiring hardware virtualization. 32-bit shouldn't even need it. Common issues are trying to force SMP ( more than one CPU ) with requires IOAPIC and that requires VT-x/AMD-v. Also depending on the guests kernel i686 requires PAE.

[rkb]

The ISO image I downloaded from the Debian site is https://cdimage.debian.org/debian-cd/cu ... 6/iso-dvd/. I am not sure how to tell "why" hardware virtualization is required by the guest.

[Perryg]

You can post the guests configuration file ( *.vbox) and maybe it will show why. You will need to compress it to get past the file extension filter.

[rkb]

I attached the .vbox file. Thanks again.

[Perryg]

I should have also asked for the following.

Code: Select all

VBoxManage showinfo <name|uuid>

Note: you will need to be in the directory that actually has the vboxmanage.exe for the command to work.

[rkb]

Here is the additional information:

Code: Select all

PS C:\Program Files\Oracle\VirtualBox> .\VBoxManage.exe showvminfo TestLinux --details
Name:            TestLinux
Groups:          /
Guest OS:        Debian (32-bit)
UUID:            22880e48-5341-4ee3-80fc-97bd9fd0d799
Config file:     C:\Users\rburton\VirtualBox VMs\TestLinux\TestLinux.vbox
Snapshot folder: C:\Users\rburton\VirtualBox VMs\TestLinux\Snapshots
Log folder:      C:\Users\rburton\VirtualBox VMs\TestLinux\Logs
Hardware UUID:   22880e48-5341-4ee3-80fc-97bd9fd0d799
Memory size:     4096MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       off
Triple Fault Reset: off
APIC:            on
X2APIC:          on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): DVD
Boot Device (2): HardDisk
Boot Device (3): Network
Boot Device (4): Floppy
ACPI:            on
IOAPIC:          off
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:           powered off (since 2017-08-16T17:50:46.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (0, 0): C:\Users\rburton\Downloads\debian-9.1.0-i386-DVD-1.iso (UUID: ab0bdd66-b783-4615-b249-08b82c
SATA (0, 0): C:\Users\rburton\VirtualBox VMs\TestLinux\TestLinux.vdi (UUID: c782e233-a731-4554-90bd-e830
NIC 1:           MAC: 0800272983AF, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type:
ed speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: AC97, Codec: AD1980)
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Users\rburton\VirtualBox VMs\TestLinux\TestLinux.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

[Perryg]

Try enabling PAE like I pointed out previously. If that fails then turn off hardware-v ( both are located in the system settings )

[mpack]

I would also reduce the memory allocation below 4GB. In fact I'm not certain that this number is above the threshold at which VirtualBox will assume that it's a 64bit guest and therefore require VT-x, but it's certainly a lot of RAM for a 32bit VM. I'd have thought 2GB was plenty.

[rkb]

I reduced the memory to 2Gb and I get the Windows 10 equivalent of the "blue screen of death" when I start the VM. I tried it twice with the same result (computer reboot). Then I enabled PAE with the same result. I couldn't find hardware-v but there is a grayed out tab labeled "Hardware" that I cannot get to.

It may be related but I noticed that I only get the option for 32-bit guests. It seems that the suggestion to get 64-bit guests enabled follows much of the same suggestions as I have been using.