bc3tech wrote:Perryg wrote:If you run Hyper-V on the host it has already taken ownership of hardware virtualization. Since only one thing at a time can own hardware virtualization VirtualBox will not work except in 32-bit mode. There is a way to make Hyper-V not load at boot, see MS support for the proper way to disable load at boot.
relevant blog entry:
http://blogs.msdn.com/b/virtual_pc_guy/ ... entry.aspx though it is all in reference to Win 2k8 server and still means you have to actually
reboot your machine in order to enable WP8 dev after working w/ something in VirtualBox. Still much less than optimal IMO.
ok so here's the question...
Thus far I've seen this "no Hypervisor" boot entry as the only way to get around this problem. The problem for me, and i'm sure others, is that if we are doing this because we want to
occasionally run virtualBox, what happens when we start Windows w/o the "no hypervisor" entry? Boom. VirtualBox is installed and activated on both of these entries, so in reality what we're saying is that Hyper-V and VirtualBox are mutually exclusive. If you want one, you
can't have the other.
Ever. So rather than create a boot entry that disables Hyper-V, you might as well just uninstall it. Because as long as VBox is installed, you're never going to get booted in to the Hyper-V boot entry anyway.
Of course, then, what this means is that VBox is an off-limits product for anybody doing WP8 (and maybe Win8?) development and wanting to use the Simulator(s).
Just making sure I understand it correctly.