True or False - HYPER-V to be discontinued in 2029 ?

jimbo45 said:

I thought this had already been settled ages ago!!!!

You might have though some suggestions though in getting a 2nd level VM on Hyper-V to work -- I.E

Host (W11 with HYPER-V)->W11 VM with Hyper-V->2nd level VM (any windows or anything even a basic WinPE)

Cheers
jimbo

Click to expand...

I just set it up and it works on Intel pcs.

On host (Pro) - install hyper-v

Run Hyper-V and install Pro as guest in vm

Run guest and install Hyper-V

Run nested Hyper-V and install any iso

Older AMD pcs cannot nest hyper-V.

cereberus said:

Older AMD pcs cannot nest hyper-V.

Click to expand...

Yeah, I think Ryzen CPUs all have the capabilities though. If I recall correcttly, I did this nesting on my laptop which is 1st gen. Ryzen (even though it is a 2700U. Mobile CPUs were one generation behind. Confusing, right!)

cereberus said:

I just set it up and it works on Intel pcs.

On host (Pro) - install hyper-v

Run Hyper-V and install Pro as guest in vm

Run guest and install Hyper-V

Run nested Hyper-V and install any iso

Older AMD pcs cannot nest hyper-V.

Click to expand...

On Intel it works fine --Host Linux Opensuse kernel 6.-10.x CPU N100 @ 3.40 Ghz with 4 cores
Guest VM under KVM/QEMU W11 Iot Enterprise pro with Hyper-V active 9GB RAM and 4 Virt CPU's
Guest VM under Windows Guest on Hyper V -- OK

Screenshot from my post here :


Host :



Cheers
jimbo

"...take the red pill - you stay in Wonderland and I show you how deep the rabbit hole goes"

Nested virtualisation inside nested virtualisation with Hyper-V. The host machine is running it's own Reflect image as a Hyper-V VM using viBoot, one of its VMs is running a VM of its own....



.....boy does a VM run slow inside a VM

Bree said:

.....boy does a VM run slow inside a VM

Click to expand...

It sure does

@Bree
@SlicEnDicE

Not surprising - you've a double set of paravirtualisation -- e.g double set of CPU virtualisation where the ist virtual CPU is paravirtualising the 2nd CPU, same with graphics, networking and disk I/O subsystem.

That's why nested VM's are only really useful to "Proof of concept" an OS i.e will it boot etc, unless you've loads of hardware and can pass thru physical devices so the "Guest OS" can minimize the amount of paravirtualisation needed.

Anyway we've discovered that It DOES work whether the REAL Host is a Linux KVM/QEMU machine or Windows itself without needing to go through loads of hoops and whistles.

Containerisation actually might be a better option for running multiple Windows applications even if on different Windows builds rather than needing a full Windows instance.

That's the next thing I want to play with !!!.


Probably not the best way of doing it - but it's a starting point.

Cheers
jimbo