Rocky + KDE + VirtualBox = successful Windows 10 Pro guest VM!

My virtualized Windows 10 Pro system is now running, and behaves MUCH better than I expected.

After months of thrashing with VMware Workstation Pro – and after paying $200 for it – I tried the most recent (v6.2) version of VirtualBox. About a day later, everything works!

I had to buy a new retail version of Windows 10 Pro, because my three physical Windows 10 Pro systems all have digital OEM licenses. In the grand scheme of things, that’s fine by me.

I’m very happy with Rocky Linux and only a little less so with KDE plasma. Once I identified and expelled the two bad guys – Dell (physical machine) and VMware – all is good.

I look forward to continuing to contribute to Rocky Linux and this community.

2 Likes

Tom,

Maybe a bit later now, but with digital licenses you need to connect your Windows 10 machine to a Microsoft account. rather than a local account The machine then appears in the devices list in the Microsoft account. Then when you want to re-activate later, there is an option that says I have a digital license, it then looks at your Microsoft accounts and gives you a list of the machines registered. At this point you choose the one that you are replacing since you reinstalled it for example. That digital license then gets transferred to the newly installed machine and the old one disappears from the device list in the Microsoft account.

The other big thing is here, never delete old devices from your Microsoft account, since the digital license will then disappear I expect. I’m glad I didn’t do this with mine, and later reinstalled the VM and was able to activate it and continue as normal without having to buy another license.

Incidently though, mine was a Windows 10 Pro license bought direct from Microsoft, so it wasn’t OEM. This means I can transfer it between different hardware, something that you cannot do with an OEM key anyway. The downside for that is it costs far more than an OEM license, but I can live with that.

1 Like

I wonder how libvirtd/KVM would fare compared to VMware and VirtualBox?
(AppStream has libvirt in Virtualization module.)

VMWare and “VMWare Workstation” are two very different things.
Kernel Virtual Machine is open source and already in the kernel.

No doubt.

Still my bottom line, as a reasonably competent senior developer with forty+ years of professional experience, is that I thrashed for months trying to get a Windows 10 Pro guest VM working using VMware tools. I bought the license, I attempted to use their “support” (another joke), I spent many weeks installing and uninstalling things, patching things, editing config files, and all the rest.

When I gave up and decided to try VirtualBox, it all just worked.

I’m running Windoze 10 VM using KVM, & those run better than when using VirtualBox (that is to be expected, as it is a type 1 HyperVisor rather than type 2 which VirtualBox & VMware Workstation Player are. If I were you I’d change to KVM…

Sounds very interesting. If you get a chance to put together a recipe, I’ll check it out.

I appreciate the information.