#14885 closed defect (worksforme)
Please fix 64-bit dectection
| Reported by: | zburns | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 5.0.10 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Running on a Retina MacBook Pro Windows 10 using BootCamp. Everything about this computer is 64 bit and virtualization is supported. Something in the 5.x branch of VirtualBox is broken. My 64-bit machines in 5.0.10 have now reverted to 32-bit and fail to boot.
See attached
Attachments (3)
Change History (8)
by , 9 years ago
| Attachment: | SNAG-0000.png added |
|---|
by , 9 years ago
comment:1 by , 9 years ago
Same hardware and virtual machines as in ticket # 14694 - in which that sort of worked also.
comment:2 by , 9 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Actually it's very likely that Hyper-V is active on your Windows 10 box. Disable Hyper-V and VT-x will be most likely available again.
comment:3 by , 9 years ago
There's no way to do that - It's a macbook pro retina 2015 - there is no way to enter the bios to enable/disable that setting.
comment:4 by , 9 years ago
Ah, I misunderstood what you said. Yes, for some reason Hyper-V got reinstalled (thanks Microsoft!) and I removed that restarted and had to fiddle with the network card because VirtualBox said mine was wrong.
I've attached a working log file - not sure of the difference and why Virtualbox was really complaining and can't work around it.
by , 9 years ago
| Attachment: | Working Log.log added |
|---|
comment:5 by , 9 years ago
There is no workaround :-) The VT-x extension is a restricted resource which cannot be used by different hypervisors in parallel.
Regarding the difference: Look for the 'HVP' CPUID bit. It was set for the host in the "non-working" log file and now it's clear.
Host OS Picture