Alternatively: you could just use what's already preconfigured for your system by using kvm & qemu using nothing but simple "dnf install" commands and I recommend using virt-manager if you want a GUI like VMware
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
see the last line ;)
but yeah Boxes is great
reading your post reminded me of myself 25 years long ago; searching google, or articles, or forums with well done informations like yours and my comment was intended for someone like the old version of me tearing his hear out trying to get something like vmware to work, when someone could have just told me that the names of a lazier version that works just as well... so i'm paying it forward. lol
This.
I came into this expecting Selinux or firewald to be the issue.
I recently installed VMware Workstation on Fedora 41 KDE. Browsing Broadcom's website to find the download link was one of the most abysmal life experiences I have ever had. So, at the end, I went to the AUR and got the link from the PKGBUILD there. I installed it by running the executable as root. I didn't have any issues with the modules since the Workstation automatically offers to install required kernel modules upon launch if they are not present. Only manual intervention I had to do was to disable Secure Boot from BIOS since MSI likes to enable it each time I update it's firmware.