I have tried running an image in Virtualbox, and it took 10 minutes to start up, whereas Hyper-V takes less than 30 seconds.

More importantly,  I do not get any network connection, or sound.

The same image opens in HyperV with sound (it is a Pro image which supports enhanced mode), and has a network connection.

I could not see any way to get sound or network connection.

So the VB implementation is virtually unusable at the moment.

I had the same problem.
With the VM shut down I opened its settings and changed the following:

Network:
Enable Network Adapter
Attached to :  Bridged Adapter
Name: Realtek PCIe Gbe Family Controller
(Settings may differ on your setup)

Audio
Enable Audio
Host Audio Driver: Windows Direct Sound
Audio Controller: Intel HD Audio
(Setting may differ on your setup)

Rebooted virtual machine.

Are you using VirtualBkx through Hyper-V’s virtualization engine rather than its own? That’s supported but is a lot slower. To use VirtualBox natively, you have to boot Windows using a BCD entry that disables the Hyper-V hypervisor.

+x

 

Derek - 30 May 2021 1:39 PM

I had the same problem.
With the VM shut down I opened its settings and changed the following:

Network:
Enable Network Adapter
Attached to :  Bridged Adapter
Name: Realtek PCIe Gbe Family Controller
(Settings may differ on your setup)

Audio
Enable Audio
Host Audio Driver: Windows Direct Sound
Audio Controller: Intel HD Audio
(Setting may differ on your setup)

Rebooted virtual machine.

Thanks I will give it a try.

+x

 

jphughan - 30 May 2021 2:00 PM

Are you using VirtualBkx through Hyper-V’s virtualization engine rather than its own? That’s supported but is a lot slower. To use VirtualBox natively, you have to boot Windows using a BCD entry that disables the Hyper-V hypervisor.

I will try again.  I forgot that

+x

 

jphughan - 30 May 2021 2:00 PM

Are you using VirtualBkx through Hyper-V’s virtualization engine rather than its own? That’s supported but is a lot slower. To use VirtualBox natively, you have to boot Windows using a BCD entry that disables the Hyper-V hypervisor.

Thanks. I should have tried this before I posted, as I always had to disable HyperV in past to run vb!

aIt made a big difference, and although a bit sedate compared with HyperV, it is manageable.

I managed to get network settings working (thanks to new user Derek) - took a couple of reboots after running troubleshooter.

Had no luck with sound, as I suspecr it does not see my conecant audio adapter.  I went into networl settings, but could not select anything else other than it default setting as the VM is not activated.  However HyperV mode just works (despite vm being unactivated).

Still, apart from sound, it is usable.

Do you know if Viboot runs in Windows 10 Home?

+x

 

Derek - 30 May 2021 1:39 PM

I had the same problem.
With the VM shut down I opened its settings and changed the following:

Network:
Enable Network Adapter
Attached to :  Bridged Adapter
Name: Realtek PCIe Gbe Family Controller
(Settings may differ on your setup)

Audio
Enable Audio
Host Audio Driver: Windows Direct Sound
Audio Controller: Intel HD Audio
(Setting may differ on your setup)

Rebooted virtual machine.

Thanks very much.  I managed to get the network working but no luck with sound so far.

Also disabling the HyperV Hypervisor made a huge difference in speed.  Still slower than HyperV though.

Glad to hear it’s working better! viBoot runs on Win10 Home through VirtualBox since that can be installed on Win10 Home, but won’t run on Hyper-V since that’s only available on Pro and better editions.