Why VirtualBox or VMware can not run with Hyper-V enabled Windows 10
I am running Windows 10 Pro 64bit with Hyper-V enabled and also enabled Intel VT-x virtualization technology. But when I try to run VirtualBox 64bit Windows goes into a BSOD. When I run VMware it shows an error.
My question is Why VirtualBox and VMware can not be run with Hyper-V enabled? Please explain with all details you have including hardware and software. I want to know the internal cause of this error.
Here are some findings of mine. Most sites suggest adding a boot entry with BCDedit or to disable Hyper-V with BCDedit. e.g. Creating a "no hypervisor" boot entry, Run Hyper-V and VirtualBox on the same machine. But I can run QEMU with Hyper-V. Qemu does not show any error with Hyper-V and runs smoothly.
windows-10 virtualbox virtual-machine virtualization vmware
edited Feb 10 at 16:21
Dave Mackey
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
add a comment |
I am running Windows 10 Pro 64bit with Hyper-V enabled and also enabled Intel VT-x virtualization technology. But when I try to run VirtualBox 64bit Windows goes into a BSOD. When I run VMware it shows an error.
My question is Why VirtualBox and VMware can not be run with Hyper-V enabled? Please explain with all details you have including hardware and software. I want to know the internal cause of this error.
Here are some findings of mine. Most sites suggest adding a boot entry with BCDedit or to disable Hyper-V with BCDedit. e.g. Creating a "no hypervisor" boot entry, Run Hyper-V and VirtualBox on the same machine. But I can run QEMU with Hyper-V. Qemu does not show any error with Hyper-V and runs smoothly.
windows-10 virtualbox virtual-machine virtualization vmware
edited Feb 10 at 16:21
Dave Mackey
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
1
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09
add a comment |
I am running Windows 10 Pro 64bit with Hyper-V enabled and also enabled Intel VT-x virtualization technology. But when I try to run VirtualBox 64bit Windows goes into a BSOD. When I run VMware it shows an error.
My question is Why VirtualBox and VMware can not be run with Hyper-V enabled? Please explain with all details you have including hardware and software. I want to know the internal cause of this error.
Here are some findings of mine. Most sites suggest adding a boot entry with BCDedit or to disable Hyper-V with BCDedit. e.g. Creating a "no hypervisor" boot entry, Run Hyper-V and VirtualBox on the same machine. But I can run QEMU with Hyper-V. Qemu does not show any error with Hyper-V and runs smoothly.
windows-10 virtualbox virtual-machine virtualization vmware
edited Feb 10 at 16:21
Dave Mackey
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
I am running Windows 10 Pro 64bit with Hyper-V enabled and also enabled Intel VT-x virtualization technology. But when I try to run VirtualBox 64bit Windows goes into a BSOD. When I run VMware it shows an error.
My question is Why VirtualBox and VMware can not be run with Hyper-V enabled? Please explain with all details you have including hardware and software. I want to know the internal cause of this error.
Here are some findings of mine. Most sites suggest adding a boot entry with BCDedit or to disable Hyper-V with BCDedit. e.g. Creating a "no hypervisor" boot entry, Run Hyper-V and VirtualBox on the same machine. But I can run QEMU with Hyper-V. Qemu does not show any error with Hyper-V and runs smoothly.
windows-10 virtualbox virtual-machine virtualization vmware
windows-10 virtualbox virtual-machine virtualization vmware
edited Feb 10 at 16:21
Dave Mackey
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
edited Feb 10 at 16:21
Dave Mackey
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
edited Feb 10 at 16:21
Dave Mackey
2901620
edited Feb 10 at 16:21
Dave Mackey
2901620
edited Feb 10 at 16:21
Dave Mackey
2901620
2901620
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
asked May 13 '17 at 15:30
BiswapriyoBiswapriyo
3,06141344
3,06141344
1
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09
add a comment |
1
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09
1
1
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09
add a comment |
2 Answers
2
active
oldest
votes
VirtualBox and VMware Workstation (or VMware Player) is what we called an Hypervisor level 2.
Hyper-V or VMware ESXi are however Hypervisor level 1.
One of the main difference between the two sorts of hypervisor is the first is an application running inside an existing OS, while the latter is the OS itself.
It means that when you have enabled Hyper-V, your Windows 10 "host" became a virtual machine. A special one, but nonetheless a virtual machine.
So your question may be changed to: "Why VirtualBox and VMware Workstation does not work inside an Hyper-V virtual machine ?". One can answer because as a VM, the Intel VT-X instruction is no more accessible from your virtual machine, only the host can have it.
QEMU works because it does not do virtualization but emulation, which is completely different and explain why QEMU is awfully slow. Virtualization is the process to run a complete isolated machine inside another, but with the help of the processor. This requires the virtual machine and the host be instruction compatible.
The emulation is the process to run any machine inside a running OS, there is no platform restriction, it's why QEMU can run an ARM machine on an amd64 platform.
Note: QEMU has 2 operating mode:
- it can work as an emulator, this is this mode I explained above
- it can work as a virtualization software with the help of KVM if the guest architecture is compatible with the host's and if the VT instruction is present of course.
answered May 13 '17 at 15:47
VeovisVeovis
60666
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
add a comment |
Starting from Windows Redstone 4 build, QEMU will be able to run under Hyper-V by employing the Windows Hypervisor Platform API.
The Windows Hypervisor Platform accelerator (WHPX) is being integrated to QEMU patches are submitted for merging.
The Windows Hypervisor Platform API will be included in Redstone 4 build
Experimental support for WHPX is included in QEMU 2.12
Update:
Virtualbox 6.0 added support for WHPX Virtualbox 6.0 Changelog.
answered Feb 4 '18 at 10:34
nkefnkef
27325
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1208850%2fwhy-virtualbox-or-vmware-can-not-run-with-hyper-v-enabled-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
VirtualBox and VMware Workstation (or VMware Player) is what we called an Hypervisor level 2.
Hyper-V or VMware ESXi are however Hypervisor level 1.
One of the main difference between the two sorts of hypervisor is the first is an application running inside an existing OS, while the latter is the OS itself.
It means that when you have enabled Hyper-V, your Windows 10 "host" became a virtual machine. A special one, but nonetheless a virtual machine.
So your question may be changed to: "Why VirtualBox and VMware Workstation does not work inside an Hyper-V virtual machine ?". One can answer because as a VM, the Intel VT-X instruction is no more accessible from your virtual machine, only the host can have it.
QEMU works because it does not do virtualization but emulation, which is completely different and explain why QEMU is awfully slow. Virtualization is the process to run a complete isolated machine inside another, but with the help of the processor. This requires the virtual machine and the host be instruction compatible.
The emulation is the process to run any machine inside a running OS, there is no platform restriction, it's why QEMU can run an ARM machine on an amd64 platform.
Note: QEMU has 2 operating mode:
- it can work as an emulator, this is this mode I explained above
- it can work as a virtualization software with the help of KVM if the guest architecture is compatible with the host's and if the VT instruction is present of course.
answered May 13 '17 at 15:47
VeovisVeovis
60666
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
add a comment |
VirtualBox and VMware Workstation (or VMware Player) is what we called an Hypervisor level 2.
Hyper-V or VMware ESXi are however Hypervisor level 1.
One of the main difference between the two sorts of hypervisor is the first is an application running inside an existing OS, while the latter is the OS itself.
It means that when you have enabled Hyper-V, your Windows 10 "host" became a virtual machine. A special one, but nonetheless a virtual machine.
So your question may be changed to: "Why VirtualBox and VMware Workstation does not work inside an Hyper-V virtual machine ?". One can answer because as a VM, the Intel VT-X instruction is no more accessible from your virtual machine, only the host can have it.
QEMU works because it does not do virtualization but emulation, which is completely different and explain why QEMU is awfully slow. Virtualization is the process to run a complete isolated machine inside another, but with the help of the processor. This requires the virtual machine and the host be instruction compatible.
The emulation is the process to run any machine inside a running OS, there is no platform restriction, it's why QEMU can run an ARM machine on an amd64 platform.
Note: QEMU has 2 operating mode:
- it can work as an emulator, this is this mode I explained above
- it can work as a virtualization software with the help of KVM if the guest architecture is compatible with the host's and if the VT instruction is present of course.
answered May 13 '17 at 15:47
VeovisVeovis
60666
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
add a comment |
VirtualBox and VMware Workstation (or VMware Player) is what we called an Hypervisor level 2.
Hyper-V or VMware ESXi are however Hypervisor level 1.
One of the main difference between the two sorts of hypervisor is the first is an application running inside an existing OS, while the latter is the OS itself.
It means that when you have enabled Hyper-V, your Windows 10 "host" became a virtual machine. A special one, but nonetheless a virtual machine.
So your question may be changed to: "Why VirtualBox and VMware Workstation does not work inside an Hyper-V virtual machine ?". One can answer because as a VM, the Intel VT-X instruction is no more accessible from your virtual machine, only the host can have it.
QEMU works because it does not do virtualization but emulation, which is completely different and explain why QEMU is awfully slow. Virtualization is the process to run a complete isolated machine inside another, but with the help of the processor. This requires the virtual machine and the host be instruction compatible.
The emulation is the process to run any machine inside a running OS, there is no platform restriction, it's why QEMU can run an ARM machine on an amd64 platform.
Note: QEMU has 2 operating mode:
- it can work as an emulator, this is this mode I explained above
- it can work as a virtualization software with the help of KVM if the guest architecture is compatible with the host's and if the VT instruction is present of course.
answered May 13 '17 at 15:47
VeovisVeovis
60666
VirtualBox and VMware Workstation (or VMware Player) is what we called an Hypervisor level 2.
Hyper-V or VMware ESXi are however Hypervisor level 1.
One of the main difference between the two sorts of hypervisor is the first is an application running inside an existing OS, while the latter is the OS itself.
It means that when you have enabled Hyper-V, your Windows 10 "host" became a virtual machine. A special one, but nonetheless a virtual machine.
So your question may be changed to: "Why VirtualBox and VMware Workstation does not work inside an Hyper-V virtual machine ?". One can answer because as a VM, the Intel VT-X instruction is no more accessible from your virtual machine, only the host can have it.
QEMU works because it does not do virtualization but emulation, which is completely different and explain why QEMU is awfully slow. Virtualization is the process to run a complete isolated machine inside another, but with the help of the processor. This requires the virtual machine and the host be instruction compatible.
The emulation is the process to run any machine inside a running OS, there is no platform restriction, it's why QEMU can run an ARM machine on an amd64 platform.
Note: QEMU has 2 operating mode:
- it can work as an emulator, this is this mode I explained above
- it can work as a virtualization software with the help of KVM if the guest architecture is compatible with the host's and if the VT instruction is present of course.
answered May 13 '17 at 15:47
VeovisVeovis
60666
edited May 13 '17 at 17:00
answered May 13 '17 at 15:47
VeovisVeovis
60666
answered May 13 '17 at 15:47
VeovisVeovis
60666
answered May 13 '17 at 15:47
VeovisVeovis
60666
60666
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
add a comment |
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
1
1
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
The virtualization creates a whole "fake" system, except for the processor where the hypervisor will only limits the amount of processor time the vm can use. So you can virtualize arm only on an arm host, x86 on an x86/amd64 host, amd64 on an amd64 host etc... An emulator will recompile each instruction for a binary compiled for a specific platform to run on another platform. QEMU belongs to the same family as console emulators for example (psx, dolphin, virtualboy, project64, MAME...)
– Veovis
May 13 '17 at 16:50
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
Virtualization (yes, not emulation) has been available long before hardware-assisted virtualization became available. It can be nested as desired.
– Daniel B
May 13 '17 at 17:53
add a comment |
Starting from Windows Redstone 4 build, QEMU will be able to run under Hyper-V by employing the Windows Hypervisor Platform API.
The Windows Hypervisor Platform accelerator (WHPX) is being integrated to QEMU patches are submitted for merging.
The Windows Hypervisor Platform API will be included in Redstone 4 build
Experimental support for WHPX is included in QEMU 2.12
Update:
Virtualbox 6.0 added support for WHPX Virtualbox 6.0 Changelog.
answered Feb 4 '18 at 10:34
nkefnkef
27325
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
add a comment |
Starting from Windows Redstone 4 build, QEMU will be able to run under Hyper-V by employing the Windows Hypervisor Platform API.
The Windows Hypervisor Platform accelerator (WHPX) is being integrated to QEMU patches are submitted for merging.
The Windows Hypervisor Platform API will be included in Redstone 4 build
Experimental support for WHPX is included in QEMU 2.12
Update:
Virtualbox 6.0 added support for WHPX Virtualbox 6.0 Changelog.
answered Feb 4 '18 at 10:34
nkefnkef
27325
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
add a comment |
Starting from Windows Redstone 4 build, QEMU will be able to run under Hyper-V by employing the Windows Hypervisor Platform API.
The Windows Hypervisor Platform accelerator (WHPX) is being integrated to QEMU patches are submitted for merging.
The Windows Hypervisor Platform API will be included in Redstone 4 build
Experimental support for WHPX is included in QEMU 2.12
Update:
Virtualbox 6.0 added support for WHPX Virtualbox 6.0 Changelog.
answered Feb 4 '18 at 10:34
nkefnkef
27325
Starting from Windows Redstone 4 build, QEMU will be able to run under Hyper-V by employing the Windows Hypervisor Platform API.
The Windows Hypervisor Platform accelerator (WHPX) is being integrated to QEMU patches are submitted for merging.
The Windows Hypervisor Platform API will be included in Redstone 4 build
Experimental support for WHPX is included in QEMU 2.12
Update:
Virtualbox 6.0 added support for WHPX Virtualbox 6.0 Changelog.
answered Feb 4 '18 at 10:34
nkefnkef
27325
edited Dec 21 '18 at 8:56
answered Feb 4 '18 at 10:34
nkefnkef
27325
answered Feb 4 '18 at 10:34
nkefnkef
27325
answered Feb 4 '18 at 10:34
nkefnkef
27325
27325
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
add a comment |
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
2
2
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
This API in theory could be used by VMWare and VirtualBox also.
– Ramhound
Feb 4 '18 at 13:45
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Ramhound Can it be done with VirtualBox or VMware? That article only mention qemu.
– Biswapriyo
Mar 28 '18 at 10:08
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
@Biswapriyo I determined that VMWare and VirtualBox was possible directly from the documentation. However, VMWare and VirtualBox would have to make the necessary changes to their application
– Ramhound
Mar 28 '18 at 11:25
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1208850%2fwhy-virtualbox-or-vmware-can-not-run-with-hyper-v-enabled-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Hyper-V does not support nested virtualization (with hardware acceleration). However, it will not crash under normal circumstances. VirtualBox would complain that it cannot run x64 guests and that’s it. So something else is wrong like a malfunctioning device driver or whatever.
– Daniel B
May 13 '17 at 15:37
I see, it does indeed crash. However, again: This is not normal. A crash is never normal. It appears this is a bug in Hyper-V. You should probably get in touch with Microsoft about it.
– Daniel B
May 13 '17 at 17:51
Worth pointing out that QEMU isn't a hypervisor. Hyper-V does support nested virtualization.
– Ramhound
May 13 '17 at 19:09