this post was submitted on 01 Nov 2024
57 points (100.0% liked)

Linux

5185 readers
169 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
57
VMware Workstation Shifting From Proprietary Code To Using Upstream KVM (www.phoronix.com)
submitted 1 week ago by vividspecter@lemm.ee to c/linux@programming.dev
6 comments fedilink hide all child comments
top 6 comments
sorted by: hot top controversial new old
[–] OsrsNeedsF2P@lemmy.ml 4 points 5 days ago (1 children)

Surprised this is still getting developed and not on life support

[–] possiblylinux127@lemmy.zip 1 points 4 days ago

Don't hold your breath

[–] Kissaki@programming.dev 4 points 6 days ago

Notably for CPU only. And on other platforms they already did.

Broadcom would like to clarify that while using KVM for the CPU virtualization, they will continue to rely on all of the existing VMware virtual devices for graphics and other functionality. Also on both macOS and Windows they have migrated to the native CPU virtualization frameworks.

[–] horse_battery_staple@lemmy.world 4 points 1 week ago (2 children)

Proxmox is starting to look really promising

[–] possiblylinux127@lemmy.zip 2 points 4 days ago

Its more than just promising

[–] Scoopta@programming.dev 3 points 6 days ago

Not sure what proxmox has to do with this? All this is doing is allowing VMware workstation to run without out of tree modules, it means nothing for anyone else