VMware Workstation Shifting From Proprietary Code To Using Upstream KVM

[erniv2]

Nice that will also mean you can run vmware and kvm vms in paralell cause both use the kvm driver for the cpu, that´s like countering the windows hypervisor hypervisor ? Windows usally runs a hypervisor and to run vmware or vbox it has to run on top of that thing.

And with this Vmware cuts one of the steps, once upstream they can focus on their drivers for disks net and graphics.

[stormcrow]

This isn't a boon to KVM by any stretch. This is Broadcom trying to get more free labor so they can squeeze more profit out of the VMWare acquisition going forward. They're cutting labor costs by shifting the labor spent on the proprietary Linux back end to open source developers. They're already gouging customers by tripling (or more) their fees and dropping smaller clients entirely. Broadcom is not one of the good faith actors in the computing industry. They take and never give back anything without a crowbar and rust remover.

[pWe00Iri3e7Z9lHOX2Qx]

Nice! Now Oracle just needs to start advancing the VirtualBox KVM backend from Cyberus and ditch the existing one.

[pWe00Iri3e7Z9lHOX2Qx]

This isn't a boon to KVM by any stretch. This is Broadcom trying to get more free labor so they can squeeze more profit out of the VMWare acquisition going forward. They're cutting labor costs by shifting the labor spent on the proprietary Linux back end to open source developers. They're already gouging customers by tripling (or more) their fees and dropping smaller clients entirely. Broadcom is not one of the good faith actors in the computing industry. They take and never give back anything without a crowbar and rust remover.

Broadcom sucks and what they are doing to VMWare and their customers sucks. But I'd still prefer they used KVM.

[mirmirmir]

It's bad enough that I can't find a suitable Inkscape replacement for editing my SVGs, given that GTK 3's theming API is apparently too restrictive for Breeze-GTK to get rid of the buggy drop shadows on its menus.

(Ever since GNOME-isms started to leak into non-GNOME apps, I've been working to purge all GTK use from my desktop and I've almost succeeded. I think the main things remaining are Geeqie (part-way through writing a PyQt-based clone of the features I need), GIMP (need to experiment with Krita), Flatseal (need to upgrade KDE from 5 to 6 for flatpak-kcm), Inkscape (no solution yet), gcdemu (need to write a replacement cdemu frontend), guvcview (need to test out alternatives), playonlinux (need to write a replacement. I don't like Phoenicis), workrave (need to write a more tailored replacement), gLabels (haven't used in years, so I'll probably just delete it), jstest-gtk (need to verify that KDE's joystick control panel has reached feature parity), EasyTAG (need to research alternatives with similar UX), and gVim (need to explore replacements).)

It's getting to the point where I'm starting to find it a more appealing prospect to just bump my RAM from 64GB to 96GB and start using Electron apps instead of GTK apps. At least they properly respect my CSD vs. SSD preferences.

Least deranged KDE fan

[Quackdoc]

This is wild. I'm not a personal fan of vmware products, but I do recognize that they really do have some of the best features and UIs. This is rather big, love to see it.

[eszlari]

(need to upgrade KDE from 5 to 6 for flatpak-kcm)

flatpak-kcm is part of Plasma since 5.27.

At least they properly respect my CSD vs. SSD preferences.

virt-manager respects SSD.

[OneTimeShot]

"VMWare backdoor".... I thought the Kernel didn't allow APIs that didn't have an OpenSource implementation.

Seems like these days the kernel is just a pipe between a closed-source firmware blob and a closed-source userspace blob.

[NM64]

Ever since GNOME-isms started to leak into non-GNOME apps, I've been working to purge all GTK use from my desktop and I've almost succeeded.

I'm by far no Linux guru, but while I don't tend to mind the aesthetic of GTK3 applications (though GTK4 is a bit much...), I do find it maddening that they don't obey Fitts' Law (and, of course, neither does GTK4 - my personal pet theory is that the GTK devs don't see the problem because GNOME defaults to having the panel at the top).

I don't know about your distro, but simply installing the gtk3-nocsd package seemed to make all GTK3 apps actually obey Fitts' Law (with the exception that Firefox and LibreWolf are no longer able to have tabs up against the top of their maximized window to take advantage of Fitts' Law for tab-switching, but my primary albeit rather small-time web browser is offered in a GTK2 flavor anyway)

From the official github page:

gtk3-nocsd is a small module used to disable the client side decoration of Gtk+ 3.

Since Gtk+ 3.10, its developers added a so-called header bar or custom title bar. With this and the client-side decoration, the original title bar and window border provided by the window manager are disabled by Gtk+. This makes all Gtk+ 3 programs look alike. Even worse, this may break some window manager or compositors.

Unfortunately, the Gtk+ developers decided to be against the existing standards and provide "no option" to turn it off.

Luckily, with gtk3-nocsd, we still have a way to (partially) turn it off. Window manager (title bar and window border) can be re-enabled.

[slalomsk8er]

More mindless "bloated" garbage.

Enterprise users have no fucking time to toy with the command line just to spin up, modify or manage a VM. If every damn option and the kitchen sink is not included in the graphical manager interface, it's useless garbage. End of story.

Enterprise user here and I did use the CLI for managing my VMs while I was the admin of the KVM hypervisor hosts.
I vastly prefer to copy and paste the CLI command from the company wiki then to go over screenshots and follow the click trail. CLI also makes automation a lot easier.