New Windows 10 Insider Preview Fast+Skip Build 18965 (20H1) - Aug. 21 Insider

kado897 said:

VBox has only recently got support for Hyper V and from all reports it doesn't work very well if at all.

Yup - it's still horrid. So I still have to use my HVLaunch script to switch between (although, truth be told, I haven't run VBox in a long time now).

New Weekly Windows 10 Insider Program Pulse Survey - Aug. 23

So reinstalled Manago using Gnome Testing. Interestinglly, you can install VMware on this distro from AUR without using the github kernel patch How to Install VMware Workstation on Arch Linux / Manjaro - Computing for Geeks. Takes a bit of effort, especially if you are used to Ubuntu but my Windows 10 VMs are all updated (except perhaps the ESXI VMs - I'll check later). Right now I have to use DEL at reboot to enter the BIOS and do a boot override to reach Linux but that is a very minor annoyance.

Kari said:

The best part of installing Windows to VHD and booting to it is that no virtualization software is required. Booting natively to VHD means it uses the real, physical hardware of the host. It is and behaves as any physical Windows installation, with only one difference: Windows cannot be upgraded on native boot VHD.

To upgrade my native boot VHDs, I boot to host main OS, create a Hyper-V VM using the native boot VHD as existing hard disk, and upgrade it using UUP Dump ISO. When upgraded, I can again boot natively to it.

When I no longer need a specific VHD, I simply delete the VHD file and remove its boot menu entry.

Kari

I really do not understand WHY you cannot upgrade a VHD automatically but can when it in a virtual machine. For clarity for other readers, you still ge cumulative /security updates.

johngalt said:

Yup - it's still horrid. So I still have to use my HVLaunch script to switch between (although, truth be told, I haven't run VBox in a long time now).

Ditto. Tried it and it just crashed - miserable failure. Using the old BCD edit method works ok.

martyfelker said:

So reinstalled Manago using Gnome Testing. Interestinglly, you can install VMware on this distro from AUR without using the github kernel patch How to Install VMware Workstation on Arch Linux / Manjaro - Computing for Geeks. Takes a bit of effort, especially if you are used to Ubuntu but my Windows 10 VMs are all updated (except perhaps the ESXI VMs - I'll check later). Right now I have to use DEL at reboot to enter the BIOS and do a boot override to reach Linux but that is a very minor annoyance.

Hi there
the patch is no problem --currently on fedora 30 kernel 5.2.9-200 ---ignore the little popup screen saying install VMware tools for vista (????) by clicking the remind me later box -- VM powers on - no problems and runs just OK including 3-D and hardware support.



You can install vmware tools on the guest by using say another host (windows) but you still get the message on kernel 5.x regardless --just ignore - doesn't seem to have any negative effects

I'm messing around with Fedora currently (basically Red Hat's --Now part of IBM-- opensource development system which is used to build the commercial support editions of RHEL -- Red hat Enterprise Linux --stable system used all over the world) to get newer packages and latest kernels.

I suspect a minor VMWare update will be in the offing soon since kernel 5 is now pretty much mainstream.

BTW it's not really a good idea to run two Hypervisor types together even if it's possible (of course as a VM you can run a second level VM e.g on a HYPER-V VM you can then run a guest on it - 2nd level running VMWare and have a VM on that but response time won't be very good).

The only way I think you can get away with doing that sort of stuff is to run your VM's on a very small and lean OS like Esxi where the VMs are almost 100% Native -- the problem with that approach though for home users is that the free version of Esxi doesn't have local console handling to communicate / log on to the VM's so you need another machine e.g a laptop to connect via say RDP or tigerVNC.

I'll try out a Windows VM on Esxi with HYPER-V and a guest VM on that and see how it performs. The other issue with Esxi is that it can be quite picky where hardware is concerned = you need a good quality "White Box" to get it working properly though --not for the faint hearted but great if you've spare hardware and free time !!!!. --Beats trundling to supermarket etc on Sat afternoon's !!!!

I still think though it's all personal choice that VBOX is a terrible experience after using VMWare -- even with the odd hassles with VMWare at some Windows and Linux host updates !!!!

Cheers
jimbo

cereberus said:

I really do not understand WHY you cannot upgrade a VHD automatically but can when it in a virtual machine. For clarity for other readers, you still ge cumulative /security updates.

I have been wondering the same. It's not logical.

It is weird, that now when Slow Ring upgrades come as cumulative updates, it can be upgraded on native boot VHD. But, if you try to upgrade Fast Ring Windows, you'll get this:



However, this is not a big issue. It is easy to use the VHD on a Hyper-V VM, upgrade, then boot to it again natively.

Kari

Kari said:

I have been wondering the same. It's not logical.

It is weird, that now when Slow Ring upgrades come as cumulative updates, it can be upgraded on native boot VHD. But, if you try to upgrade Fast Ring Windows, you'll get this:



However, this is not a big issue. It is easy to use the VHD on a Hyper-V VM, upgrade, then boot to it again natively.

Kari

Easy if using Pro of course.

What I do not understand is why MS would choose the Slow Ring to trial cumulative updates for builds rather than the more cavalier Fast Ring.

The whole ethos was Fast Ring was for trail blazing and Slow Ring builds were relatively stable. We now have a situation whereby 19h2 is out soon but not tested by a lot of users (my perception). MS have not thought this through

cereberus said:

Easy if using Pro of course.

What I do not understand is why MS would choose the Slow Ring to trial cumulative updates for builds rather than the more cavalier Fast Ring.

The whole ethos was Fast Ring was for trail blazing and Slow Ring builds were relatively stable. We now have a situation whereby 19h2 is out soon but not tested by a lot of users (my perception). MS have not thought this through

All was thrown into confusion and panic by the 1809 fiasco,

kado897 said:

All was thrown into confusion and panic by the 1809 fiasco,

Sure but obviously a knee-jerk solution and not thought through. The plan has more wholes than Swiss Cheese.