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.
-- Mark
On Wed, 2024-06-26 at 15:56 -0400, 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.
-- Mark
This was my reply to Broadcom list - hope it helps
From my notes for F40 (meon & monks)
ja@meon ~ 1$ uname -a Linux meon.jaa.org.uk 6.9.5-200.fc40.x86_64
ja@meon ~ 3$ vmware -v VMware Workstation 17.5.2 build-23775571
Went here https://github.com/mkubecek/vmware-host-modules/issues/243 for forum then ...
This time I down loaded from here
https://github.com/nan0desu/vmware-host-modules/tree/tmp/workstation-17.5.2-...
ja@monks ~ 45$ cd /global/db/sw/VMware_17/mkubecek_17.5.2/Second_Attempt/vmware-host-modules-tmp- workstation-17.5.2-k6.9.1
Probably a make clean in here!!!
ja@monks vmware-host-modules-tmp-workstation-17.5.2-k6.9.1 47$ make
[root@monks:/global/db/sw/VMware_17/mkubecek_17.5.2/Second_Attempt/vmware-host-modules-tmp-workstation- 17.5.2-k6.9.1]$ make install
[root@monks:/global/db/sw/VMware_17/mkubecek_17.5.2/Second_Attempt/vmware-host-modules-tmp-workstation- 17.5.2-k6.9.1]$ systemctl restart vmware.service
Ran w11 on Monks - saw no errors with jc -fn40 - so far!
John
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?
On Wed, 2024-06-26 at 15:41 -0500, Thomas Cameron wrote:
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
On Wed, 2024-06-26 at 15:41 -0500, Thomas Cameron wrote:
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
On 26 Jun 2024, at 22:29, Mark C. Allman via users users@lists.fedoraproject.org wrote:
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."
I managed to move a vmware windows 10 to kvm and windows license, i think, needed to be reactivated in the normal way. Now running that vm as windows 11 under kvm.
I did have backups to fall back on in case the move had failed.
Barry
On 2024-06-26 16:41, Thomas Cameron wrote:
On 6/26/24 2:56 PM, Mark C. Allman via users wrote:
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?
+!
Frank
-
Barry -
Frank Bures -
ja -
Mark C. Allman -
Thomas Cameron