VirtualBox - No 64-bit
-
-
Is Hyper V enabled on that computer? If so, disable it.
-
Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...
-
@BBigford said in VirtualBox - No 64-bit:
Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...
I wonder why that might be.
-
@aaronstuder said in VirtualBox - No 64-bit:
Is Hyper V enabled on that computer? If so, disable it.
You beat me to it.
-
Probably because Hyper-V permanently takes over VT-x instead of sharing like VMware Player for instance (VB forum)... Because it's a level 1 hypervisor?
In either case, sharing is not caring I guess.
-
@BBigford said in VirtualBox - No 64-bit:
Probably because Hyper-V permanently takes over VT-x instead of sharing like VMware Player for instance (VB forum)... Because it's a level 1 hypervisor?
In either case, sharing is not caring I guess.
Type 1. It has nothing to do with sharing. It is because you are doing nesting. Hyper-V does not support hypervisor nesting. Why do you want to nest your hypervisors?
-
@BBigford said in VirtualBox - No 64-bit:
Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...
Correct, because Hyper-V does not virtualize the virtualization functions.
-
Whatever you are wanting to install into VirtualBox you could just install directly onto Hyper-V.
-
@scottalanmiller said in VirtualBox - No 64-bit:
@BBigford said in VirtualBox - No 64-bit:
Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...
Correct, because Hyper-V does not virtualize the virtualization functions.
A dev has a vmdk that I tried converting for HV but it just comes up as user: drac and no commands will execute. So basically the conversion is botched. I need to spin up that VM and grab some files that he needs to compare against others. I do everything in HV so I had just wanted to install VB with the intention I'd convert the vmdk (used to be just CLI only but now you can copy to VHD then attach in HV).
So I'm just using VB again as a one time use.
-
@StrongBad said in VirtualBox - No 64-bit:
Whatever you are wanting to install into VirtualBox you could just install directly onto Hyper-V.
It's an existing image that a new dev needs info from, and the previous dev saved it as a vmdk. I can probably use a Hyper-V conversion tool but I was trying the opposite.. Convert it in VBox which didn't work.
-
Something like this, or via PowerShell...
