On 6/26/24 2:56 PM, Mark C. Allman via users wrote:

Anyone have VMware Workstation or Player 17.5.1 or 17.5.2 working on the 
6.9.* kernels? The kernel modules from VMware haven't worked in quite a 
while. They don't compile for the 6.9.* kernels, and, if I'm remembering 
correctly, they don't compile when running the 6.8.* kernels either.

I have the code for vmnet and vmmon from 
https://github.com/mkubecek/vmware-host-modules/tree/workstation-17.5.1. 
There are all kinds of exceptions when the kernel modules are loaded at 
boot time. I tried running vmplayer as a test -- it "ran" but trashed 
the kernel and required hard reboots. One of the tests totally bricked 
my laptop (that was fun to recover).

I'm currently running kernel 6.9.5-200.fc40.x86_64and all packages are 
up to date. The laptop is a Dell Inspiron 7591, Core i7-10510U CPU, 16GB 
of ram.

Not telling you how to compute, just curious: why not just use native 
KVM? I use KVM on my workstation to virtualize RHEL 7, RHEL8, RHEL9, 
Windows 2022, Windows 2019, Windows 10 and Windows 11. It Just Works(TM).

Since Broadcom has told us all to kick rocks, maybe consider using 
native Linux virtualization?

-- 
Thomas
--

I have not been able to get my Picoscope 7 to work with KVM or VirtualBox.
I think the USB disconnects when it shouldn't.

Ubuntu docker version works OK with F40.
w11 version works OK with VMware Workstation 17 Pro & F40

AFAIK Picoscope will not run natively under Fedora

John
--

Ah. I didn't click on "View All Branches" in the branches dropdown on GitHub. Select that and you see "tmp/workstation-17.5.2-k6.9."

Use a different VM technology? One word: licenses. Move to another vm technology and everything, e.g., Windows 11, Office, Quickbooks, etc., etc., thinks it's on a new system. Or at least it did. I tried it a few years ago using VirtualBox and ran into a brick wall with Microsoft. My experience was more of a "go pound sand."

-- Mark