[Resolved] win 10 64x intel Vt-d virtualitation error no VMX

Discussions about using Windows guests in VirtualBox.
Post Reply
vic1414
Posts: 5
Joined: 11. Oct 2018, 19:19

[Resolved] win 10 64x intel Vt-d virtualitation error no VMX

Post by vic1414 »

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by socratis »

Enable VT-x, that's all I can tell you without a log.

We need to see a complete VBox.log, from a complete VM run:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe error / 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", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Image
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
vic1414
Posts: 5
Joined: 11. Oct 2018, 19:19

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by vic1414 »

its that ok?
Attachments
win 10 64x-2018-10-11-21-58-38.zip
its that ok?
(5.24 KiB) Downloaded 29 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by socratis »

Yes, the VBox.log was the correct one. However, the log stops even before we have a chance to see the CPU in your host. We have some signs:
00:00:02.198725 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
...
00:00:02.453574 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))
We got to do this another way. Open a Command Prompt window and post the output of the command:
  • 
    "C:\Program Files\Oracle\VirtualBox\VBoxManage" list hostinfo
assuming that you've installed VirtualBox in its default location "C:\Program Files\Oracle\VirtualBox\".
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
vic1414
Posts: 5
Joined: 11. Oct 2018, 19:19

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by vic1414 »

C:\Program Files\Oracle\VirtualBox>VBoxManage list hostinfo
Host Information:

Host time: 2018-10-11T20:40:07.785000000Z
Processor online count: 8
Processor count: 8
Processor online core count: 4
Processor core count: 4
Processor supports HW virtualization: no
Processor supports PAE: yes
Processor supports long mode: yes
Processor supports nested paging: no
Processor#0 speed: unknown
Processor#0 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#1 speed: unknown
Processor#1 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#2 speed: unknown
Processor#2 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#3 speed: unknown
Processor#3 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#4 speed: unknown
Processor#4 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#5 speed: unknown
Processor#5 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#6 speed: unknown
Processor#6 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Processor#7 speed: unknown
Processor#7 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Memory size: 32456 MByte
Memory available: 25101 MByte
Operating system: Windows 10
Operating system version: 10.0.17763

C:\Program Files\Oracle\VirtualBox>
Last edited by socratis on 11. Oct 2018, 22:48, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
vic1414
Posts: 5
Joined: 11. Oct 2018, 19:19

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by vic1414 »

i doesnt undertand in my bios set write virtualization available wtf!
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by socratis »

vic1414 wrote:
Processor#0 description: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Your i7-6700 CPU most certainly supports hardware virtualization, so it's a matter of enabling it in the BIOS. See your PC's manufacturer help on how to do this. Also, make sure that nothing else has an exclusive hold on that.
vic1414 wrote:
Processor supports HW virtualization: no
Something is using your VT-x, most probably Hyper-V. Take a look at the above article to get some ideas...
win 10 64x intel Vt-d virtualitation error no VMX
Be careful though, we're talking about VT-x, not VT-d. They're two different things.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
vic1414
Posts: 5
Joined: 11. Oct 2018, 19:19

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by vic1414 »

got it
Hyper-V was graping my virtualizacion
thanks a lot
regards
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win 10 64x intel Vt-d virtualitation error no VMX

Post by socratis »

Glad you got it going. Marking as [Resolved].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply