Why is Hyper V So bad?

Bree said:

On advantage Hyper-V has over all others comes into play when you have Macrium Reflect installed. Its viBoot allows you to boot a Macrium image as a Hyper-V VM.

Meh, that is nothing to do with Hyper-V - it is just Macrium making their format compatible - they could have made it bootable with anything if they desired - VHD(x) is just a container.

The biggest advantage Hyper-V has for me over other virtualisation is it suspends and resumes guests on host restart. I have a small Linux VM (for torrents) that has been running for years after countless Windows host reboots and upgrades. If it shut down I'm not sure I'd remember the password after all this time.

lx07 said:

Meh, that is nothing to do with Hyper-V - it is just Macrium making their format compatible - they could have made it bootable with anything if they desired - VHD(x) is just a container.

So far Hyper-V is the only Hypervisor they can use with viBoot. Apparently they have been working on using VMWare/Virtualvbox for years, but no success yet. This statement from two years ago....

Unfortunately, I can't offer you any estimate on when this will be available, but VMWare/VirtualBox support is something that we are looking into and it should be available in a future update.

Kind Regards,
Macrium Support

Any news on booting MR images in vmware?

Bree said:

So far Hyper-V is the only Hypervisor they can use with viBoot.

Well fair enough.

I'm not an expert on the internals of the VHD format. My point was that Hyper-V guests resuming after a host restart is a massive benefit. Neither VMWare or VBox do it.

lx07 said:

Well fair enough.

I'm not an expert on the internals of the VHD format. My point was that Hyper-V guests resuming after a host restart is a massive benefit. Neither VMWare or VBox do it.

Yes, that is a great benefit. On the same lines you can sign out from Windows and a Hyper-V VM will continue running because it is the SYSTEM account that is used, not your own account as with VMWare/Virtualbox.

This is all due to the difference between using a Type 1 Hypervisor and a Type 2.

Hypervisor Type 1 and Type 2

lx07 said:

Well fair enough.

I'm not an expert on the internals of the VHD format. My point was that Hyper-V guests resuming after a host restart is a massive benefit. Neither VMWare or VBox do it.

Hi there
On Linux Hosts BTW with the KVM/QEMU Hypervisor - Guest machines have no problem with restart after any Host re-boot either . (Both Linux and Windows VM's will resume after any host re-boot). Nobody needs to be logged on to the host either for the VM's to run - in fact if using the HOST essentially for running a load of VM's it's probably better anyway to have nobody logged on to the host system and simply manage it remotely when needed.

in the config just set this : (using GUI Virtual machine manager) -- if you don't use a GUI just edit the XML config file



Another nice advantage - if running Linux VM's you can have direct kernel boot so the VM doesn't even have the overhead of the host OS.

Cheers
jimbo

Bree said:

Yes, that is a great benefit. On the same lines you can sign out from Windows and a Hyper-V VM will continue running because it is the SYSTEM account that is used, not your own account as with VMWare/Virtualbox.

Workarounds for vmplayer/wksta:
- shared VMs (removed in v16), or
- vmrun commandline tool.
Same functionality. Yes, more complex.

Bree said:

This is all due to the difference between using a Type 1 Hypervisor and a Type 2

I don't think so. Only missing configuration options in GUI.

cereberus said:

I just do not think this is ever going to happen.

It's been on the 'wish list' for two or three years and it's still just that - a wish.