New
#140
Here's what I want to do. Since Hyper-V runs on Ring 0 of the kernel you cannot directly access most of the host hardware without remotely logging into the guest VM. Not a problem for Windows guests but I haven't figured out how to remote into Linux guest (like I upgraded the built-in Ubuntu 19.10 VM to Ubuntu 20.04). On the other hand VMware runs on Ring 1 and has no problem accessing the host hardware though of course you can also remote into say ESXui VMs etc etc. Running these concurrently is great so I'm saving my money to upgrade to VMware 16 which should come out this fall. I suspect however that they sell the Linux product seperately in which case VMware WS 15.5.2 has never yet failed on the newest kernels (running early 5.7 kernels on Fedora 33 [Rawhid].
Cheers
The reality is we should not expect any new features until 20H1 (2004) is finally released. They will mostly be looking for feedback on update experience but between WU and UUPDUMP it almost never fails.
I must say I completely disagree! I've got last two UEFI firmware updates through Windows Update, nothing could be easier and simpler. I really like the fact that HP is giving me firmware updates through Windows Update.
I think you have misunderstood something. Fast Ring Insider builds are not about the next version of Windows, version 20H1 (or 2004) released sometime later this spring.
Fast Ring builds are for build or two beyond that, testing features coming in versions 20H2 late this year and 21H1 coming spring 2021.
Kari
Hi there
I think there's also some confusion as to 20H1 --the next version of VMWare workstation is called 20H1 and is available as a Free trial --expires in Oct for those wanting to play with it. - Windows only version though.
@martyfelker -- to logon to a Linux VM (or Host) FROM Windows you need to enable an X-Server on Windows (e,g XMING / VMCSERVER or similar) and then you have to allow SSH with an X-server to be active on the Linux VM/Host. This is currently problematic with some desktops that use the WAYLAND system rather than the classical "XORG" system.
I'm seeing what I can do with a WINDOWS VM on KVM/QEMU -- there's no problem accessing the HOST Linux via command line FROM the Windows VM and things like SAMBA and the odd GUI program work but to get to a full LINUX desktop GUI is something I haven't got working yet -- I'll investigate with some Linux distros as VM's using an older kernel and without WAYLAND entering the fray and see what comes out.
This used to work (Ubuntu with xrdp / vncserver but I can't get this to work with this build of Windows and current UBUNTU kernel. -- I'm messing around on a WINDOWS Host to avoid any extra complications with VMWare Workstation for the UBUNTU VM. (Ihate the GNOME interface but while testing I'll put up with it).
How to Establish Remote Desktop Access to Ubuntu From Windows
Note though when using VMWare for VM's the only physical drivers that work "natively" are done via attaching a device via a USB port . The rest of the system is "Paravirtualised" i.e uses "Virtual Hardware" which is why most of these VM's are "Hardware agnostic" i.e can run on almost any capable computer without configuration changes.
Things like HYPER-V and KVM/QEMU allow actual physical hardware to be passed through so in the config just add for example the spare graphics card / lan card or whatever. You will then need the Windows (or Linux if the VM is a Linux one) driver(s) for those devices passed straight through. The purpose of things like vmware tools / open-vm-tools is to optimize the virtual graphics / keyboard / mouse for the VM -- this is of course not needed if you are passing through actual hardware including pci cards etc.
Cheers
jimbo