Windows 10 Insider Preview Fast Build 19559.1000 - February 5 Insider

martyfelker said:

I know. Maybe Brink can arrange it! Seriously, VirtrualBox compiles fine but like VMware does not work on this kernel. Maybe because there are Windows versions of VMware and VirtualBox

- - - Updated - - -

Here's the error log for VirtualBox

Failed to open a session for the virtual machine Windows 10 Insider Fast Ring.

The virtual machine 'Windows 10 Insider Fast Ring' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Hi there
I stick to the Arch Linux kernel builds --usually they update pretty quick -- current is 5.5.3 so I suppose within a day or two we'll get the 5.5.6.

Things like VMWare are IMO a bit too complex to meddle around in the kernel --if others have fixed it --it's fine by me -- VMWare works OK on 5.5.3 and creating the Windows build isn't an issue either -- but I'm weaning myself off VMWare unless I'm using a Windows Host.

I can't be bothered though with VBOX -- not my favourite bit of software. For VM's now sticking with QEMU/KVM on Linux Hosts and VMWare Workstation on Windows Hosts. I also hate GNOME --it's almost impossible to get any sort of decent desktop -- I use either basic CLI (on a decent server) or KDE Plasma or XFCE if I need a Window manager.

No probs running VMWare WKS and QEMU/KVM Windows (or any other) VM's concurrently (and with VM's on both running on the same Host too).

Image of VMWare and KVM /QEMU running Concurrent Windows 10 VM's from earlier builds of Windows -- still creating a brand new VMWare W10 VM on this build.



Cheers
jimbo

martyfelker said:

I'm coming around to your virtualization but have a completely different take on GNOME. I love it - it is my favorite DE. But when VMware 16 comes out this year I think it just might give QEMU/KVM a run for its money (actually not, since QEMU/KVM is free!).
You might want to look at VirtualBox 6.1.x on Windows - it's not half bad.

Back in Windows. I have installed my two most expensive and best shareware programs - VMware and Take Command. I've been using JPSoft shareware since 1990 when they came out with 4DOS. Also have installed Start10 from Stardock, which, as some of you may know started out making software for OS/2 (sadly abandoned by VMware for purely marketing reasons - it was working great 20 years ago. And of course IBM has pretty much abandoned OS/2 - wish they would make it opensource but I guess a few banks still pay for it.

Hi there.

Windows (this release as HOST) and ANY Linux distro that I've tried creating as a VM (tried UBUNTU, OPENSUSE, ARCH LINUX, FEDORA (31) and CENTOS 8 as VM) that's 5 different distros so it's not an inherent problem with the Linux variants -- all have different kernel releases !! -- can get almost any screen resolution under the sun except THE ONE I WANT (1080p --- 1920 X 1080 @ 60 HZ).

Running the XRANDR stuff to add the 1920 X 1080 mode will briefly display it in proper resolution and then it reverts to something else !!!

BAD ONE VMware this time.


This is absolute B/S on VMWare's part since these days 1920 X 1080 must be one of the most popular screen resolutions around -- especially on typical laptops.

Why on earth am I still being offered 640 VGA for instance -- when they can't even get "Sensible" resolutions correct.

I don't blame Windows at all for this fiasco !!!! So for once No Rant against Ms.

Cheers
jimbo