New
#1
Virtualbox and Hyper-V
Allegedly, virtualbox 6 and hyper-v can now coexist i..e you can run VB6 if Hyper-V is enabled - not tried it.
Allegedly, virtualbox 6 and hyper-v can now coexist i..e you can run VB6 if Hyper-V is enabled - not tried it.
I have the latest version of VB installed on my win10pro1903 pc that also has hyper-installed.
I turn hyper-v off and on,reboot with a bcdedit :
BCDEDIT /Set {current} hypervisorlaunchtype auto <--- this turns hyper-v on and I can run hyper-v vm or vb vm
BCDEDIT /Set {current} hypervisorlaunchtype off <---- this turns off hyper-v and I can run either VB VM or vmware VM
VMW Workstation Pro 15 and Windows 1903 Hyper-V Compatibility : vmware
let me clarify:
I have VB 6.0.8 installed and it runs with or without hypervisorlaunchtype auto or off.....
with hypervisorlaunchtype off, hyper-v vm will not run, vb vm will run, vmware vm will run
with hypervisorlaunchtype on or auto hyper-v vm will run, and vb vm will run
credential guard is disabled
I have never attempted to run 2 hypervisors at the same time....
Last edited by shockwaveriderz; 12 Jul 2019 at 09:07.
There is a portable freeware app turning hyper-v on/off without having to type anything :)
HyperVSwitch (GitHub)
just run it, it will show the current situation, click on the button to turn off/on + reboot. :)
Sort of, I can boot a virtual machine while hyper-v is enabled, however,
there are still issues.
*if the vm has a server such as iRedMail running in an ubuntu 20.04 vm,
it boots and runs and local net can connect to it's mail and web servers, but the outside 'public' network can't.
The following tests were run.
Hyper-v was turned on by an update so I tried a boot up, yes it will if the virtualbox settings say hyper-v accelleration in the system.
However it appeared to be blocked on the public network, such as an external machine on another network.
None of the ports were connecting and yet its not the router. Ports were forwarded to a real machine with a web server
and there it was.
Connecting from the host machine was ok.
The ip addressing is 1)nat 2) bridged.
On the bridged side it obtained a dhcp address and appeared in the private network.
Windows firwall was set to allow all on the public network , still blocked.
One suggestion was to shut off hyper-v then reboot, then enable it again, then try it. I haven't done that yet,
because it works now with hyper-v shut off. I booted the VM and tried it and all was working.
In windows firewall I saw how you can disable protection in the public tab for specific cards, that did not work,
just disabling hyper-v worked. All the windows firewall settings were ignored or don't work.
So maybe another time I'll try the servers again in hyper-v but I've proven to myself its not suitable in the case of oracle Virtual machines, that have servers. They are allowed to connect to the internet but internet connections to them are not routed. Nothing in the firewall log about dropping packets, they are not making it to the firewall. So maybe there is a network setting that is done wrong.