Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
0
votes
1
answers
35
views
How do I share an Ubuntu Ext4 partition in a VMWare VM, with another VM?
I am running VMware Workstation 16 Pro on my W11 PC. I have several VMs, including a Ubuntu 22.04.4 LTS VM, and a Solaris 10 VM (sadly still needed for legacy projects). I need to allow the Solaris VM access (full RW permissions) to my "/" partition (ext4, /dev/sda3) in the Ubuntu VM. First, is this...
I am running VMware Workstation 16 Pro on my W11 PC. I have several VMs, including a Ubuntu 22.04.4 LTS VM, and a Solaris 10 VM (sadly still needed for legacy projects). I need to allow the Solaris VM access (full RW permissions) to my "/" partition (ext4, /dev/sda3) in the Ubuntu VM. First, is this even possible? If so, what are the steps necessary for this to happen?
On the Ubuntu VM, I went to Settings -> Sharing, enabled Sharing, and then went into Media Sharing, and shared the folder
/
, and enabled Wired connection 1
. In the Solaris VM created the folder /etc/nfs/ub22
(as root), I su'd to root and entered
mount -F nfs 192.168.18.107:/ /etc/nfs/ub22
(1921.68.18.107 is the IP of the Ubuntu VM) but I get the error
nfs mount: 192.168.18.107: : RPC: Rpcbind failure - RPC: Unable to receive
Brie
(111 rep)
Jul 18, 2025, 03:10 PM
• Last activity: Jul 18, 2025, 06:58 PM
0
votes
1
answers
42
views
Building a custom Linux kernel causes VMware Tools to stop working
I am compiling kernels for CentOS 6.10 in VMware Workstation. For some reason when I compile and boot a new kernel, VMware Tools stops working, or at least the shared folders feature does, which is the feature I am using to copy files between the VM and host machine. CentOS is updated to the most re...
I am compiling kernels for CentOS 6.10 in VMware Workstation. For some reason when I compile and boot a new kernel, VMware Tools stops working, or at least the shared folders feature does, which is the feature I am using to copy files between the VM and host machine.
CentOS is updated to the most recent updated kernel, which I am also compiling with rpmbuild as stock with no modifications other than defining buildid in kernel.spec to differentiate it.
I am installing the kernel RPM as well as the kernel-firmware RPM. The kernel boots perfectly fine and everything appears to work other than VMware Tools.
Does anyone know why VMware Tools stops working when building a custom (unmodified) stock kernel?
I have tried reinstalling VMware Tools. This makes no difference unless I am on some version of a stock kernel.
Zhro
(2831 rep)
Oct 6, 2024, 02:26 PM
• Last activity: Oct 7, 2024, 12:56 PM
0
votes
0
answers
95
views
Built-in Webcam connects to Linux guest in VMWare but doesn't display image correctly
I'm running Kali Linux (deb) on VMWare Workstation 17 Pro. I have my host laptop's (Win10) webcam hooked up to Kali via VMware. On the Kali guest, when I give it a `ls /dev/video*` I get video0 through video3 as results, meaning the Kali guest knows there is a camera hooked up. I am testing the came...
I'm running Kali Linux (deb) on VMWare Workstation 17 Pro. I have my host laptop's (Win10) webcam hooked up to Kali via VMware. On the Kali guest, when I give it a
ls /dev/video*
I get video0 through video3 as results, meaning the Kali guest knows there is a camera hooked up.
I am testing the camera with cheese
to see what it sees, and here is where the issue is. The app/camera does start, but it's mostly a grey box. The top of the image renders a few lines so I can see my ceiling fan, but 95% of the rest of the bottom of the image is grey. The image also flickers here and there, some times showing more of my ceiling. I have the Accelerate 3D Graphics
option turned on in VMWare (although I didn't do anything on Kali side, maybe I'm missing something here?).
Any idea how to get this built-in laptop webcam to work properly on the Kali guest OS in VMware?
Tommy K
(141 rep)
Oct 4, 2024, 12:37 AM
0
votes
0
answers
54
views
How to get the a network adapter working with Fedora 6 on VMware Workstation?
I am experimenting with older versions of Linux in VMware. RHEL5 detects my virtual network adapter just fine, but Fedora 6 does not. I thought that RHEL5 was based on Fedora 6? I have tried various operating system options in VMware for Fedora 6, such as "Fedora", "Red Hat Linux", and "Red Hat Ente...
I am experimenting with older versions of Linux in VMware. RHEL5 detects my virtual network adapter just fine, but Fedora 6 does not. I thought that RHEL5 was based on Fedora 6? I have tried various operating system options in VMware for Fedora 6, such as "Fedora", "Red Hat Linux", and "Red Hat Enterprise Linux 5" without success.
I am trying to run Fedora 6 i386, if that makes a difference. I am using VMware Workstation 16.
Zhro
(2831 rep)
Sep 13, 2024, 09:49 PM
• Last activity: Sep 13, 2024, 10:05 PM
2
votes
2
answers
3050
views
Before you can run VMware several modules must be compiled (vmmon and vmnet)
I just restarted my Pop!_OS and when trying to open vmware it says I have to compile several modules. It then goes onto trying to compile vmmon and vmnet, which fails. and gives me an error log file. I've tried changing gcc version with ```sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin...
I just restarted my Pop!_OS and when trying to open vmware it says I have to compile several modules. It then goes onto trying to compile vmmon and vmnet, which fails. and gives me an error log file.
I've tried changing gcc version with
update-alternatives --install /usr/bin/gcc gcc /usr/bin/x86_64-linux-gnu-gcc-12 100
, this didn't seem to change the error files.
I've also tried running vmware-modconfig --console --install-all
but this also fails.
Error log file:
2023-10-17T08:12:11.525Z In(05) host-26414 Log for VMware Workstation pid=26414 version=17.0.2 build=build-21581411 option=Release
2023-10-17T08:12:11.525Z In(05) host-26414 The host is x86_64.
2023-10-17T08:12:11.525Z In(05) host-26414 Host codepage=UTF-8 encoding=UTF-8
2023-10-17T08:12:11.525Z In(05) host-26414 Host is Linux 6.5.4-76060504-generic Pop!_OS 22.04 LTS Pop!_OS 22.04
2023-10-17T08:12:11.525Z In(05) host-26414 Host offset from UTC is +02:00.
2023-10-17T08:12:11.525Z In(05) host-26414 DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2023-10-17T08:12:11.525Z In(05) host-26414 [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2023-10-17T08:12:11.525Z In(05) host-26414 PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2023-10-17T08:12:11.525Z In(05) host-26414 DictionaryLoad: Cannot open file "/home/grimley/.vmware/config": No such file or directory.
2023-10-17T08:12:11.525Z In(05) host-26414 [msg.dictionary.load.openFailed] Cannot open file "/home/grimley/.vmware/config": No such file or directory.
2023-10-17T08:12:11.525Z In(05) host-26414 PREF Optional preferences file not found at /home/grimley/.vmware/config. Using default values.
2023-10-17T08:12:11.606Z Wa(03) host-26414 Logging to /tmp/vmware-grimley/vmware-26414.log
2023-10-17T08:12:11.614Z In(05) host-26414 Obtaining info using the running kernel.
2023-10-17T08:12:11.614Z In(05) host-26414 Created new pathsHash.
2023-10-17T08:12:11.614Z In(05) host-26414 Setting header path for 6.5.4-76060504-generic to "/lib/modules/6.5.4-76060504-generic/build/include".
2023-10-17T08:12:11.614Z In(05) host-26414 Validating path "/lib/modules/6.5.4-76060504-generic/build/include" for kernel release "6.5.4-76060504-generic".
2023-10-17T08:12:11.614Z In(05) host-26414 Failed to find /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h
2023-10-17T08:12:11.614Z In(05) host-26414 /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2023-10-17T08:12:11.614Z In(05) host-26414 using /usr/bin/gcc-12 for preprocess check
2023-10-17T08:12:11.619Z In(05) host-26414 Preprocessed UTS_RELEASE, got value "6.5.4-76060504-generic".
2023-10-17T08:12:11.619Z In(05) host-26414 The header path "/lib/modules/6.5.4-76060504-generic/build/include" for the kernel "6.5.4-76060504-generic" is valid. Whoohoo!
2023-10-17T08:12:11.885Z In(05) host-26414 found symbol version file /lib/modules/6.5.4-76060504-generic/build/Module.symvers
2023-10-17T08:12:11.885Z In(05) host-26414 Reading symbol versions from /lib/modules/6.5.4-76060504-generic/build/Module.symvers.
2023-10-17T08:12:11.904Z In(05) host-26414 Read 28017 symbol versions
2023-10-17T08:12:11.904Z In(05) host-26414 Reading in info for the vmmon module.
2023-10-17T08:12:11.904Z In(05) host-26414 Reading in info for the vmnet module.
2023-10-17T08:12:11.904Z In(05) host-26414 Invoking modinfo on "vmmon".
2023-10-17T08:12:11.907Z In(05) host-26414 "/sbin/modinfo" exited with status 256.
2023-10-17T08:12:11.907Z In(05) host-26414 Invoking modinfo on "vmnet".
2023-10-17T08:12:11.909Z In(05) host-26414 "/sbin/modinfo" exited with status 256.
2023-10-17T08:12:11.922Z In(05) host-26414 to be installed: vmmon status: 0
2023-10-17T08:12:11.922Z In(05) host-26414 to be installed: vmnet status: 0
2023-10-17T08:12:11.934Z In(05) host-26414 Obtaining info using the running kernel.
2023-10-17T08:12:11.934Z In(05) host-26414 Setting header path for 6.5.4-76060504-generic to "/lib/modules/6.5.4-76060504-generic/build/include".
2023-10-17T08:12:11.934Z In(05) host-26414 Validating path "/lib/modules/6.5.4-76060504-generic/build/include" for kernel release "6.5.4-76060504-generic".
2023-10-17T08:12:11.934Z In(05) host-26414 Failed to find /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h
2023-10-17T08:12:11.934Z In(05) host-26414 /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2023-10-17T08:12:11.934Z In(05) host-26414 using /usr/bin/gcc-12 for preprocess check
2023-10-17T08:12:11.940Z In(05) host-26414 Preprocessed UTS_RELEASE, got value "6.5.4-76060504-generic".
2023-10-17T08:12:11.940Z In(05) host-26414 The header path "/lib/modules/6.5.4-76060504-generic/build/include" for the kernel "6.5.4-76060504-generic" is valid. Whoohoo!
2023-10-17T08:12:12.203Z In(05) host-26414 found symbol version file /lib/modules/6.5.4-76060504-generic/build/Module.symvers
2023-10-17T08:12:12.203Z In(05) host-26414 Reading symbol versions from /lib/modules/6.5.4-76060504-generic/build/Module.symvers.
2023-10-17T08:12:12.221Z In(05) host-26414 Read 28017 symbol versions
2023-10-17T08:12:12.222Z In(05) host-26414 Kernel header path retrieved from FileEntry: /lib/modules/6.5.4-76060504-generic/build/include
2023-10-17T08:12:12.222Z In(05) host-26414 Update kernel header path to /lib/modules/6.5.4-76060504-generic/build/include
2023-10-17T08:12:12.222Z In(05) host-26414 Validating path "/lib/modules/6.5.4-76060504-generic/build/include" for kernel release "6.5.4-76060504-generic".
2023-10-17T08:12:12.223Z In(05) host-26414 Failed to find /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h
2023-10-17T08:12:12.223Z In(05) host-26414 /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2023-10-17T08:12:12.223Z In(05) host-26414 using /usr/bin/gcc-12 for preprocess check
2023-10-17T08:12:12.228Z In(05) host-26414 Preprocessed UTS_RELEASE, got value "6.5.4-76060504-generic".
2023-10-17T08:12:12.228Z In(05) host-26414 The header path "/lib/modules/6.5.4-76060504-generic/build/include" for the kernel "6.5.4-76060504-generic" is valid. Whoohoo!
2023-10-17T08:12:12.229Z In(05) host-26414 Attempting to use a compiler at location "/usr/bin/gcc-12".
2023-10-17T08:12:12.231Z In(05) host-26414 Got gcc version "12".
2023-10-17T08:12:12.231Z In(05) host-26414 The GCC version matches the kernel GCC minor version like a glove.
2023-10-17T08:12:12.232Z In(05) host-26414 Got gcc version "12".
2023-10-17T08:12:12.232Z In(05) host-26414 The GCC version matches the kernel GCC minor version like a glove.
2023-10-17T08:12:12.233Z In(05) host-26414 Trying to find a suitable PBM set for kernel "6.5.4-76060504-generic".
2023-10-17T08:12:12.233Z In(05) host-26414 No matching PBM set was found for kernel "6.5.4-76060504-generic".
2023-10-17T08:12:12.233Z In(05) host-26414 The GCC version matches the kernel GCC minor version like a glove.
2023-10-17T08:12:12.233Z In(05) host-26414 Validating path "/lib/modules/6.5.4-76060504-generic/build/include" for kernel release "6.5.4-76060504-generic".
2023-10-17T08:12:12.233Z In(05) host-26414 Failed to find /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h
2023-10-17T08:12:12.233Z In(05) host-26414 /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2023-10-17T08:12:12.233Z In(05) host-26414 using /usr/bin/gcc-12 for preprocess check
2023-10-17T08:12:12.239Z In(05) host-26414 Preprocessed UTS_RELEASE, got value "6.5.4-76060504-generic".
2023-10-17T08:12:12.239Z In(05) host-26414 The header path "/lib/modules/6.5.4-76060504-generic/build/include" for the kernel "6.5.4-76060504-generic" is valid. Whoohoo!
2023-10-17T08:12:14.992Z In(05) host-26414 The GCC version matches the kernel GCC minor version like a glove.
2023-10-17T08:12:14.992Z In(05) host-26414 Validating path "/lib/modules/6.5.4-76060504-generic/build/include" for kernel release "6.5.4-76060504-generic".
2023-10-17T08:12:14.992Z In(05) host-26414 Failed to find /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h
2023-10-17T08:12:14.992Z In(05) host-26414 /lib/modules/6.5.4-76060504-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2023-10-17T08:12:14.992Z In(05) host-26414 using /usr/bin/gcc-12 for preprocess check
2023-10-17T08:12:15.006Z In(05) host-26414 Preprocessed UTS_RELEASE, got value "6.5.4-76060504-generic".
2023-10-17T08:12:15.006Z In(05) host-26414 The header path "/lib/modules/6.5.4-76060504-generic/build/include" for the kernel "6.5.4-76060504-generic" is valid. Whoohoo!
2023-10-17T08:12:15.006Z In(05) host-26414 Using temp dir "/tmp".
2023-10-17T08:12:23.261Z In(05) host-26414 Stopping VMware services:
2023-10-17T08:12:23.261Z In(05) host-26414 VMware Authentication Daemon[71G done
2023-10-17T08:12:23.261Z In(05) host-26414 Virtual machine monitor[71G done
2023-10-17T08:12:23.261Z In(05) host-26414 make: Entering directory '/tmp/modconfig-Q8NuOz/vmmon-only'
2023-10-17T08:12:23.261Z In(05) host-26414 /usr/bin/make -C /lib/modules/6.5.4-76060504-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
2023-10-17T08:12:23.261Z In(05) host-26414 MODULEBUILDDIR= modules
2023-10-17T08:12:23.261Z In(05) host-26414 make: Entering directory '/usr/src/linux-headers-6.5.4-76060504-generic'
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/linux/driver.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/linux/driverLog.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/linux/hostif.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/apic.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/comport.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/cpuid.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/crosspage.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/memtrack.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/moduleloop.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/phystrack.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/sharedAreaVmmon.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/statVarsVmmon.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/task.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/common/vmx86.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/bootstrap.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/monLoader.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/monLoaderVmmon.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/vmmblob.o
2023-10-17T08:12:23.261Z In(05) host-26414 LD [M] /tmp/modconfig-Q8NuOz/vmmon-only/vmmon.o
2023-10-17T08:12:23.261Z In(05) host-26414 MODPOST /tmp/modconfig-Q8NuOz/vmmon-only/Module.symvers
2023-10-17T08:12:23.261Z In(05) host-26414 make: Leaving directory '/usr/src/linux-headers-6.5.4-76060504-generic'
2023-10-17T08:12:23.261Z In(05) host-26414 make: Leaving directory '/tmp/modconfig-Q8NuOz/vmmon-only'
2023-10-17T08:12:23.261Z In(05) host-26414 make: Entering directory '/tmp/modconfig-Q8NuOz/vmnet-only'
2023-10-17T08:12:23.261Z In(05) host-26414 /usr/bin/make -C /lib/modules/6.5.4-76060504-generic/build/include/.. M=$PWD SRCROOT=$PWD/. \
2023-10-17T08:12:23.261Z In(05) host-26414 MODULEBUILDDIR= modules
2023-10-17T08:12:23.261Z In(05) host-26414 make: Entering directory '/usr/src/linux-headers-6.5.4-76060504-generic'
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/driver.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/hub.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/userif.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/netif.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/bridge.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/procfs.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/smac_compat.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/smac.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/vnetEvent.o
2023-10-17T08:12:23.261Z In(05) host-26414 CC [M] /tmp/modconfig-Q8NuOz/vmnet-only/vnetUserListener.o
2023-10-17T08:12:23.261Z In(05) host-26414 make: Leaving directory '/usr/src/linux-headers-6.5.4-76060504-generic'
2023-10-17T08:12:23.261Z In(05) host-26414 make: Leaving directory '/tmp/modconfig-Q8NuOz/vmnet-only'
2023-10-17T08:12:23.261Z In(05) host-26414 [AppLoader] GLib does not have GSettings support.
2023-10-17T08:12:23.261Z In(05) host-26414 Using kernel build system.
2023-10-17T08:12:23.261Z In(05) host-26414 warning: the compiler differs from the one used to build the kernel
2023-10-17T08:12:23.261Z In(05) host-26414 The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
2023-10-17T08:12:23.261Z In(05) host-26414 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodePage+0x207: 'naked' return found in RETHUNK build
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Add() falls through to next function PhysTrack_Remove()
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Remove() falls through to next function PhysTrack_Test()
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/monLoader.c: In function ‘MonLoader_Process’:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/monLoader.c:794:24: warning: the comparison will always evaluate as ‘false’ for the address of ‘entries’ will never be NULL [-Waddress]
2023-10-17T08:12:23.261Z In(05) host-26414 794 | if (header->entries == 0 || header->count == 0) {
2023-10-17T08:12:23.261Z In(05) host-26414 | ^~
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from /tmp/modconfig-Q8NuOz/vmmon-only/bootstrap/monLoader.c:57:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/./include/monLoader.h:239:19: note: ‘entries’ declared here
2023-10-17T08:12:23.261Z In(05) host-26414 239 | MonLoaderEntry entries[];
2023-10-17T08:12:23.261Z In(05) host-26414 | ^~~~~~~
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from /tmp/modconfig-Q8NuOz/vmmon-only/./include/cpu_types.h:29,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/./include/modulecall.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/common/moduleloop.c:33:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
2023-10-17T08:12:23.261Z In(05) host-26414 779 | #define DO_ONCE(code) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from ./include/linux/prandom.h:12,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/random.h:153,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/nodemask.h:97,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/sched.h:23,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/common/moduleloop.c:31:
2023-10-17T08:12:23.261Z In(05) host-26414 ./include/linux/once.h:46: note: this is the location of the previous definition
2023-10-17T08:12:23.261Z In(05) host-26414 46 | #define DO_ONCE(func, ...) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from /tmp/modconfig-Q8NuOz/vmmon-only/./include/cpu_types.h:29,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/./include/modulecall.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/common/vmx86.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/common/vmx86.c:38:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
2023-10-17T08:12:23.261Z In(05) host-26414 779 | #define DO_ONCE(code) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from ./include/linux/prandom.h:12,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/random.h:153,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/nodemask.h:97,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/sched.h:23,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/common/vmx86.c:31:
2023-10-17T08:12:23.261Z In(05) host-26414 ./include/linux/once.h:46: note: this is the location of the previous definition
2023-10-17T08:12:23.261Z In(05) host-26414 46 | #define DO_ONCE(func, ...) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from /tmp/modconfig-Q8NuOz/vmmon-only/./include/cpu_types.h:29,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/./include/modulecall.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/linux/hostif.c:58:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
2023-10-17T08:12:23.261Z In(05) host-26414 779 | #define DO_ONCE(code) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from ./include/linux/prandom.h:12,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/random.h:153,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/nodemask.h:97,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/sched.h:23,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/binfmts.h:5,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/linux/hostif.c:31:
2023-10-17T08:12:23.261Z In(05) host-26414 ./include/linux/once.h:46: note: this is the location of the previous definition
2023-10-17T08:12:23.261Z In(05) host-26414 46 | #define DO_ONCE(func, ...) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from /tmp/modconfig-Q8NuOz/vmmon-only/./include/cpu_types.h:29,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/./include/modulecall.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/./common/vmx86.h:33,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/linux/driver.h:32,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/linux/driver.c:47:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
2023-10-17T08:12:23.261Z In(05) host-26414 779 | #define DO_ONCE(code) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 In file included from ./include/linux/prandom.h:12,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/random.h:153,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/nodemask.h:97,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/list_lru.h:12,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/fs.h:13,
2023-10-17T08:12:23.261Z In(05) host-26414 from ./include/linux/highmem.h:5,
2023-10-17T08:12:23.261Z In(05) host-26414 from /tmp/modconfig-Q8NuOz/vmmon-only/linux/driver.c:25:
2023-10-17T08:12:23.261Z In(05) host-26414 ./include/linux/once.h:46: note: this is the location of the previous definition
2023-10-17T08:12:23.261Z In(05) host-26414 46 | #define DO_ONCE(func, ...) \
2023-10-17T08:12:23.261Z In(05) host-26414 |
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmmon-only/common/task.o: warning: objtool: .text: unexpected end of section
2023-10-17T08:12:23.261Z In(05) host-26414 ERROR: modpost: "__pte_offset_map" [/tmp/modconfig-Q8NuOz/vmmon-only/vmmon.ko] undefined!
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [scripts/Makefile.modpost:144: /tmp/modconfig-Q8NuOz/vmmon-only/Module.symvers] Error 1
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [/usr/src/linux-headers-6.5.4-76060504-generic/Makefile:1992: modpost] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [Makefile:234: __sub-make] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [Makefile:117: vmmon.ko] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 Using kernel build system.
2023-10-17T08:12:23.261Z In(05) host-26414 warning: the compiler differs from the one used to build the kernel
2023-10-17T08:12:23.261Z In(05) host-26414 The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
2023-10-17T08:12:23.261Z In(05) host-26414 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmnet-only/bridge.c: In function ‘VNetBridgeSendLargePacket’:
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmnet-only/bridge.c:1413:11: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘tcp_gso_segment’? [-Werror=implicit-function-declaration]
2023-10-17T08:12:23.261Z In(05) host-26414 1413 | segs = skb_gso_segment(skb, 0);
2023-10-17T08:12:23.261Z In(05) host-26414 | ^~~~~~~~~~~~~~~
2023-10-17T08:12:23.261Z In(05) host-26414 | tcp_gso_segment
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmnet-only/bridge.c:1413:9: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
2023-10-17T08:12:23.261Z In(05) host-26414 1413 | segs = skb_gso_segment(skb, 0);
2023-10-17T08:12:23.261Z In(05) host-26414 | ^
2023-10-17T08:12:23.261Z In(05) host-26414 /tmp/modconfig-Q8NuOz/vmnet-only/userif.o: warning: objtool: VNetCsumAndCopyToUser+0x2d: call to csum_partial_copy_nocheck() with UACCESS enabled
2023-10-17T08:12:23.261Z In(05) host-26414 cc1: some warnings being treated as errors
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [scripts/Makefile.build:243: /tmp/modconfig-Q8NuOz/vmnet-only/bridge.o] Error 1
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** Waiting for unfinished jobs....
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [/usr/src/linux-headers-6.5.4-76060504-generic/Makefile:2040: /tmp/modconfig-Q8NuOz/vmnet-only] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [Makefile:234: __sub-make] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 make: *** [Makefile:117: vmnet.ko] Error 2
2023-10-17T08:12:23.261Z In(05) host-26414 Unable to install all modules. See log for details.
2023-10-17T08:12:23.261Z In(05) host-26414
Jagemann
(23 rep)
Oct 17, 2023, 08:35 AM
• Last activity: Aug 23, 2024, 03:30 PM
0
votes
1
answers
315
views
Can't install vmware workstation 17.5 in slackware current
I can't install vmware workstation profesional 17.5 in my Slackware current, this is the error: ``` root@r2d2:/home/fito/Downloads# sh VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle Extracting VMware Installer...done. Installing VMware VMX 17.5.0 Configuring...--- Logging error --- Traceback...
I can't install vmware workstation profesional 17.5 in my Slackware current, this is the error:
root@r2d2:/home/fito/Downloads# sh VMware-Workstation-Full-17.5.0-22583795.x86_64.bundle
Extracting VMware Installer...done.
Installing VMware VMX 17.5.0
Configuring...--- Logging error ---
Traceback (most recent call last):#### ] 52%
File "/tmp/vmis.lbeQOf/install/vmware-installer/python/lib/logging/__init__.py", line 1103, in emit
stream.write(msg + self.terminator)
UnicodeEncodeError: 'ascii' codec can't encode character '\u2018' in position 950: ordinal not in range(128)
Call stack:
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmware-installer.py", line 694, in
main(options)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmware-installer.py", line 536, in main
txn.Install(options.installComponent,
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/transaction.py", line 687, in Install
RunTransaction(actions, options)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/transaction.py", line 414, in RunTransaction
RunThreadedTransaction(txn, actions)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/transaction.py", line 472, in RunThreadedTransaction
txn.Run()
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/transaction.py", line 78, in Run
self.get()()
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/common.py", line 156, in Show
wrap(i.PostTransaction, txn.opts['ignoreErrors'])
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/util/__init__.py", line 26, in wrap
func(*args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/install.py", line 308, in PostTransaction
self._installer.PostTransactionInstall(**self.args)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstaller.py", line 94, in PostTransactionInstall
return self.MessageOut(self.whoami(), old, new, upgrade)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstaller.py", line 387, in MessageOut
retval = vmispy.RunExternalMethod(self._remoteUID, 0, strio.getvalue().decode('latin-1'))
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/installer.py", line 122, in MessageIn
self.proxyObject.MessageIn(uid, str)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstallerops.py", line 403, in MessageIn
ret = method(*args, **kwargs)
File "", line 372, in PostTransactionInstall
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/installer.py", line 40, in Info
return self.installer.Log('info', *args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/installer.py", line 335, in Log
return self.proxyObject.Log(logType, *args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstallerops.py", line 159, in Log
return self.MessageOut(self.whoami(), logType, *args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstallerops.py", line 485, in MessageOut
retval = vmispy.RunExternalMethod(0, self._UID, strio.getvalue().decode('latin-1'))
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/remoteinstaller.py", line 301, in MessageIn
ret = method(*args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/installer.py", line 335, in Log
return self.proxyObject.Log(logType, *args, **kwargs)
File "/tmp/vmis.lbeQOf/install/vmware-installer/vmis/core/localinstallerops.py", line 241, in Log
ltype(*args, **kwargs)
Message: 'stderr: [AppLoader] Use shipped PC/SC Lite smart card framework.\nAn up-to-date "pcsc-lite-libs" or "libpcsclite1" package from your system is preferred.\n[AppLoader] GLib does not have GSettings support.\nUsing kernel build system.\n/tmp/modconfig-bzphMU/vmmon-only/common/crosspage.o: warning: objtool: CrossPage_CodePage+0x207: \'naked\' return found in MITIGATION_RETHUNK build\n/tmp/modconfig-bzphMU/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Free() falls through to next function PhysTrack_Add()\n/tmp/modconfig-bzphMU/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Add() falls through to next function PhysTrack_Remove()\n/tmp/modconfig-bzphMU/vmmon-only/common/phystrack.o: warning: objtool: PhysTrack_Remove() falls through to next function PhysTrack_Test()\nIn file included from /tmp/modconfig-bzphMU/vmmon-only/linux/hostif.c:76:\n/tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h: In function \u2018PgtblVa2MPNLocked\u2019:\n/tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h:60:8: error: implicit declaration of function \u2018pgd_large\u2019; did you mean \u2018pgd_page\u2019? [-Wimplicit-function-declaration]\n 60 | if (pgd_large(*pgd)) {\n | ^~~~~~~~~\n | pgd_page\nIn file included from /tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h:25:\n/tmp/modconfig-bzphMU/vmmon-only/./include/compat_pgtable.h:39:45: error: implicit declaration of function \u2018p4d_large\u2019; did you mean \u2018p4d_page\u2019? [-Wimplicit-function-declaration]\n 39 | # define compat_p4d_large(p4d) p4d_large(p4d)\n | ^~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h:70:8: note: in expansion of macro \u2018compat_p4d_large\u2019\n 70 | if (compat_p4d_large(*p4d)) {\n | ^~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h:78:11: error: implicit declaration of function \u2018pud_large\u2019; did you mean \u2018pud_page\u2019? [-Wimplicit-function-declaration]\n 78 | if (pud_large(*pud)) {\n | ^~~~~~~~~\n | pud_page\n/tmp/modconfig-bzphMU/vmmon-only/common/task.c:548:1: warning: no previous prototype for \u2018TaskGetFlatWriteableDataSegment\u2019 [-Wmissing-prototypes]\n 548 | TaskGetFlatWriteableDataSegment(void)\n | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/./include/pgtbl.h:86:14: error: implicit declaration of function \u2018pmd_large\u2019; did you mean \u2018pmd_page\u2019? [-Wimplicit-function-declaration]\n 86 | if (pmd_large(*pmd)) {\n | ^~~~~~~~~\n | pmd_page\n/tmp/modconfig-bzphMU/vmmon-only/linux/hostif.c: At top level:\n/tmp/modconfig-bzphMU/vmmon-only/linux/hostif.c:2926:1: warning: no previous prototype for \u2018HostIFCheckTrackedMPN\u2019 [-Wmissing-prototypes]\n 2926 | HostIFCheckTrackedMPN(VMDriver *vm, // IN: The VM instance\n | ^~~~~~~~~~~~~~~~~~~~~\nIn file included from /tmp/modconfig-bzphMU/vmmon-only/common/vmx86.c:52:\n./arch/x86/include/asm/timex.h: In function \u2018random_get_entropy\u2019:\n./arch/x86/include/asm/timex.h:12:24: error: implicit declaration of function \u2018random_get_entropy_fallback\u2019; did you mean \u2018random_get_entropy\u2019? [-Wimplicit-function-declaration]\n 12 | return random_get_entropy_fallback();\n | ^~~~~~~~~~~~~~~~~~~~~~~~~~~\n | random_get_entropy\n/tmp/modconfig-bzphMU/vmmon-only/linux/hostif.c:3046:1: warning: no previous prototype for \u2018HostIFWritePhysicalWork\u2019 [-Wmissing-prototypes]\n 3046 | HostIFWritePhysicalWork(MA ma, // MA to be written to\n | ^~~~~~~~~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/linux/hostif.c:3205:1: warning: no previous prototype for \u2018HostIFStartTimer\u2019 [-Wmissing-prototypes]\n 3205 | HostIFStartTimer(Bool rateChanged, //IN: Did rate change?\n | ^~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/common/vmx86.c: At top level:\n/tmp/modconfig-bzphMU/vmmon-only/common/vmx86.c:700:1: warning: no previous prototype for \u2018Vmx86FreeVMDriver\u2019 [-Wmissing-prototypes]\n 700 | Vmx86FreeVMDriver(VMDriver *vm)\n | ^~~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/common/vmx86.c:733:1: warning: no previous prototype for \u2018Vmx86AllocVMDriver\u2019 [-Wmissing-prototypes]\n 733 | Vmx86AllocVMDriver(uint32 numVCPUs)\n | ^~~~~~~~~~~~~~~~~~\nmake: *** [scripts/Makefile.build:244: /tmp/modconfig-bzphMU/vmmon-only/linux/hostif.o] Error 1\nmake: *** Waiting for unfinished jobs....\n/tmp/modconfig-bzphMU/vmmon-only/linux/driver.c:271:1: warning: no previous prototype for \u2018LinuxDriverInit\u2019 [-Wmissing-prototypes]\n 271 | LinuxDriverInit(void)\n | ^~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmmon-only/linux/driver.c:339:1: warning: no previous prototype for \u2018LinuxDriverExit\u2019 [-Wmissing-prototypes]\n 339 | LinuxDriverExit(void)\n | ^~~~~~~~~~~~~~~\nmake: *** [scripts/Makefile.build:244: /tmp/modconfig-bzphMU/vmmon-only/common/vmx86.o] Error 1\n/tmp/modconfig-bzphMU/vmmon-only/common/task.o: warning: objtool: .text: unexpected end of section\nmake: *** [/usr/src/linux-6.9.3/Makefile:1919: /tmp/modconfig-bzphMU/vmmon-only] Error 2\nmake: *** [Makefile:240: __sub-make] Error 2\nmake: *** [Makefile:117: vmmon.ko] Error 2\nUsing kernel build system.\n/tmp/modconfig-bzphMU/vmnet-only/userif.c:1091:1: warning: no previous prototype for \u2018VNetUserIf_Create\u2019 [-Wmissing-prototypes]\n 1091 | VNetUserIf_Create(VNetPort **ret) // OUT\n | ^~~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmnet-only/netif.c:173:1: warning: no previous prototype for \u2018VNetNetIf_Create\u2019 [-Wmissing-prototypes]\n 173 | VNetNetIf_Create(char *devName, // IN:\n | ^~~~~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c:258:1: warning: no previous prototype for \u2018VNetBridge_Create\u2019 [-Wmissing-prototypes]\n 258 | VNetBridge_Create(const char *devName, // IN: name of device (e.g., "eth0")\n | ^~~~~~~~~~~~~~~~~\nIn file included from ./include/linux/spinlock.h:305,\n from ./include/linux/sched.h:2138,\n from /tmp/modconfig-bzphMU/vmnet-only/bridge.c:25:\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c: In function \u2018VNetBridgeReceiveFromVNet\u2019:\n/tmp/modconfig-bzphMU/vmnet-only/vmnetInt.h:44:39: error: \u2018dev_base_lock\u2019 undeclared (first use in this function); did you mean \u2018device_lock\u2019?\n 44 | #define dev_lock_list() read_lock(&dev_base_lock)\n | ^~~~~~~~~~~~~\n./include/linux/rwlock.h:56:48: note: in definition of macro \u2018read_lock\u2019\n 56 | #define read_lock(lock) _raw_read_lock(lock)\n | ^~~~\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c:587:4: note: in expansion of macro \u2018dev_lock_list\u2019\n 587 | dev_lock_list();\n | ^~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmnet-only/vmnetInt.h:44:39: note: each undeclared identifier is reported only once for each function it appears in\n 44 | #define dev_lock_list() read_lock(&dev_base_lock)\n | ^~~~~~~~~~~~~\n./include/linux/rwlock.h:56:48: note: in definition of macro \u2018read_lock\u2019\n 56 | #define read_lock(lock) _raw_read_lock(lock)\n | ^~~~\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c:587:4: note: in expansion of macro \u2018dev_lock_list\u2019\n 587 | dev_lock_list();\n | ^~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmnet-only/userif.o: warning: objtool: VNetCsumCopyDatagram+0x52: call to csum_partial_copy_nocheck() with UACCESS enabled\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c: In function \u2018VNetBridgeUp\u2019:\n/tmp/modconfig-bzphMU/vmnet-only/vmnetInt.h:44:39: error: \u2018dev_base_lock\u2019 undeclared (first use in this function); did you mean \u2018device_lock\u2019?\n 44 | #define dev_lock_list() read_lock(&dev_base_lock)\n | ^~~~~~~~~~~~~\n./include/linux/rwlock.h:56:48: note: in definition of macro \u2018read_lock\u2019\n 56 | #define read_lock(lock) _raw_read_lock(lock)\n | ^~~~\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c:900:4: note: in expansion of macro \u2018dev_lock_list\u2019\n 900 | dev_lock_list();\n | ^~~~~~~~~~~~~\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c: At top level:\n/tmp/modconfig-bzphMU/vmnet-only/bridge.c:1411:1: warning: no previous prototype for \u2018VNetBridgeSendLargePacket\u2019 [-Wmissing-prototypes]\n 1411 | VNetBridgeSendLargePacket(struct sk_buff *skb, // IN: packet to split\n | ^~~~~~~~~~~~~~~~~~~~~~~~~\nmake: *** [scripts/Makefile.build:244: /tmp/modconfig-bzphMU/vmnet-only/bridge.o] Error 1\nmake: *** Waiting for unfinished jobs....\n/tmp/modconfig-bzphMU/vmnet-only/vnetUserListener.c:87:1: warning: no previous prototype for \u2018VNetUserListener_Create\u2019 [-Wmissing-prototypes]\n 87 | VNetUserListener_Create(uint32 classMask, // IN: the listener\'s class mask\n | ^~~~~~~~~~~~~~~~~~~~~~~\nmake: *** [/usr/src/linux-6.9.3/Makefile:1919: /tmp/modconfig-bzphMU/vmnet-only] Error 2\nmake: *** [Makefile:240: __sub-make] Error 2\nmake: *** [Makefile:117: vmnet.ko] Error 2\nUnable to install all modules. See log for details.\n\n'
Installing VMware Workstation 17.5.0
Configuring...
[######################################################################] 100%
I have the lastest kernel 6.9.3 and the headers, source and all dependencies, i think so.
Can you help me!!
Adolfo
(1 rep)
Jun 7, 2024, 02:57 PM
• Last activity: Jun 8, 2024, 09:26 AM
11
votes
5
answers
12766
views
kcompacd0 using 100% CPU with VMware Workstation 16
Same as posted in redhat bugzilla -- [kcompacd0 using 100% cpu](https://bugzilla.redhat.com/show_bug.cgi?id=1694305), which was closed for `INSUFFICIENT_DATA`. Also same as - https://unix.stackexchange.com/questions/458893/vmware-on-linux-host-causes-regular-freezes - https://unix.stackexchange.com/...
Same as posted in redhat bugzilla -- [kcompacd0 using 100% cpu](https://bugzilla.redhat.com/show_bug.cgi?id=1694305) , which was closed for
- When it does, it'll normally last for several minutes. Then kicks in again after a minutes or two.
- _"kcompactd0 goes away only with drop_caches. when it goes 100%, the vmware virtual machine guest is completely unresponsive (windows 10 ltsc vm)"_ So I only tried drop_caches once, and have confirmed the behavior.
As requested upstream, here is more info:
INSUFFICIENT_DATA
.
Also same as
- https://unix.stackexchange.com/questions/458893/vmware-on-linux-host-causes-regular-freezes
- https://unix.stackexchange.com/questions/161858/arch-linux-becomes-unresponsive-from-khugepaged/
Reopening because the solution there doesn't work for me.
Here is my situation:
- Ubuntu **21.10** host and Windows **10** Enterprise client, with VMware Workstation 16 v**16.2.0** build-18760230
- I'm not doing anything fancy or heavy load, just after a day of regular Windows 10 usage (of light load), things start to get wild.
- The process kcompactd0
is constantly using 100% cpu on one core, and vmware-vmx
using 100% cpu on eight cores.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish
$ grep -r . /sys/kernel/mm/transparent_hugepage/*
/sys/kernel/mm/transparent_hugepage/defrag:always defer defer+madvise [madvise] never
/sys/kernel/mm/transparent_hugepage/enabled:always [madvise] never
/sys/kernel/mm/transparent_hugepage/hpage_pmd_size:2097152
/sys/kernel/mm/transparent_hugepage/khugepaged/defrag:1
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_shared:256
/sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs:10000
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none:511
/sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan:4096
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap:64
/sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs:60000
/sys/kernel/mm/transparent_hugepage/khugepaged/pages_collapsed:0
/sys/kernel/mm/transparent_hugepage/khugepaged/full_scans:19
/sys/kernel/mm/transparent_hugepage/shmem_enabled:always within_size advise [never] deny force
/sys/kernel/mm/transparent_hugepage/use_zero_page:1
$ cat /proc/90/stack | wc
0 0 0
echo never > /sys/kernel/mm/transparent_hugepage/defrag
echo 0 > /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
echo never > /sys/kernel/mm/transparent_hugepage/enabled
$ grep -r . /sys/kernel/mm/transparent_hugepage/*
/sys/kernel/mm/transparent_hugepage/defrag:always defer defer+madvise madvise [never]
/sys/kernel/mm/transparent_hugepage/enabled:always madvise [never]
/sys/kernel/mm/transparent_hugepage/hpage_pmd_size:2097152
/sys/kernel/mm/transparent_hugepage/khugepaged/defrag:0
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_shared:256
/sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs:10000
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none:511
/sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan:4096
/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap:64
/sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs:60000
/sys/kernel/mm/transparent_hugepage/khugepaged/pages_collapsed:0
/sys/kernel/mm/transparent_hugepage/khugepaged/full_scans:19
/sys/kernel/mm/transparent_hugepage/shmem_enabled:always within_size advise [never] deny force
/sys/kernel/mm/transparent_hugepage/use_zero_page:1
Basically the source of the workaround is in a [Fedora bug report “khugepaged eating 100%CPU”](https://bugzilla.redhat.com/show_bug.cgi?id=879801) . The bug was never fixed, and the "solution" was meant for Fedora 17 in year 2013, and
> with the last 3, maybe 4-5 versions of Fedora Kernels I haven't encountered that issue again.
But it is happening again now.
xpt
(1858 rep)
Nov 30, 2021, 11:19 PM
• Last activity: Dec 15, 2023, 03:29 PM
1
votes
3
answers
16536
views
The vmmon and vmnet vmware-workstation kernel modules fail to build on Rocky Linux 8.5. Anyone have an easy fix?
I have freshly installed Rocky Linux 8.5 then yum upgrade and dnf upgrade. Installed the kernel-headers and kernel-devel with gcc, etc. all following the instructions posted at several locations around the web. Then tried to download and run the .bundle file from vmware.com to install Workstation Pr...
I have freshly installed Rocky Linux 8.5 then yum upgrade and dnf upgrade.
Installed the kernel-headers and kernel-devel with gcc, etc. all following the instructions posted at several locations around the web.
Then tried to download and run the .bundle file from vmware.com to install Workstation Pro 16.2.1.
During the first attempt to run, the kernel modules vmmon and vmnet are supposed to compile, but fail to do so.
From several posts, it appears there was a back-port to fix a problem with a forthcoming kernel - but that fix fails with the current kernel now shipped with Rocky 8.5
I upgraded to kernel 5.16.4 following standard instructions for a kernel upgrade, but the same basic problems continue to manifest themselves.
Does anyone have instructions for creating ANY VERSION of vmware workstation on Rocky 8.5?
I ask for Rocky 8.5 instructions because Rocky 8.4 is no longer available for download from rockylinux.org
I am told this problem is also active on Red Hat Enterprises 8.5, but do not have access to a legal license for testing purposes thereon...
I find my situation to be a surprise, because vmware.com is a sponsor of Rocky Linux, and you would think someone in their QA group would have regression tested their code on the most recent general availability of Rocky?...
I don't have the necessary reputation to create the tag "rocky-linux"...
jrvmedic
(21 rep)
Feb 5, 2022, 06:35 PM
• Last activity: Dec 1, 2023, 06:01 AM
0
votes
1
answers
767
views
VMware Workstation player 17 not using host memory, stops with 2GB
i just install VMware Workstation player 17 and setup a Windows 10 VM with 4 core CPU and 5GB of Memory, But when the VM turned on it only takes 2GB of host memory and Windows 10 Task Manager shows only single core like it was a 32-bit . I tried Uninstall and Reinstalling VMware Workstation Player a...
i just install VMware Workstation player 17 and setup a Windows 10 VM with 4 core CPU and 5GB of Memory, But when the VM turned on it only takes 2GB of host memory and Windows 10 Task Manager shows only single core like it was a 32-bit .
I tried Uninstall and Reinstalling VMware Workstation Player and same problem continues.
I have a Ryzen 7 5825U Processor with 16gb RAM and I'm running a Debian Testing based Distro with kernel version 6.1


HRC
(93 rep)
May 13, 2023, 05:05 AM
• Last activity: May 13, 2023, 01:56 PM
0
votes
0
answers
352
views
VMware Tools installation on CentOS 6.10 Failed: Blocking File System Error
Hello to the Linux SE! I'm facing an error on CentOS 6.10 (x86_64 arch) running on VMware Workstation. I searched the internet for this issue. Some relevant threads by users on other sites and forums were posted, but with no success. I didn't expect this error as I had no installation errors while i...
Hello to the Linux SE!
I'm facing an error on CentOS 6.10 (x86_64 arch) running on VMware Workstation. I searched the internet for this issue. Some relevant threads by users on other sites and forums were posted, but with no success.
I didn't expect this error as I had no installation errors while installing Linux.
It happened when the VMware Tools installation triggered
> Note that the
It occurred at this step.
I tried to reinstall it completely. But still, the problem persists.
/etc/vmware-tools/services.sh start
to start it.

VMware Tools
ISO file was not corrupted.
I had expected something wrong to happen when I saw this one at the finalization of installation:

user408276
Apr 23, 2020, 06:58 PM
• Last activity: Jan 25, 2023, 04:20 AM
5
votes
1
answers
7914
views
How to open GUI from systemd service on startup?
I'm trying to start a VMWare Workstation VM from the command line. I can do this under my user (not `root`) by running the following ```sh /usr/bin/vmplayer /home/myUser/vmware/myVm.vmx ``` Now, I want to set this VM to start on boot, so I created a service `/lib/systemd/system/myService.service` wi...
I'm trying to start a VMWare Workstation VM from the command line. I can do this under my user (not
root
) by running the following
/usr/bin/vmplayer /home/myUser/vmware/myVm.vmx
Now, I want to set this VM to start on boot, so I created a service /lib/systemd/system/myService.service
with the following:
[Unit]
Description=my vm service
[Service]
User=myUser
ExecStart=/usr/bin/vmplayer /home/myuser/vmware/myVm.vmx
Environment=DISPLAY=:0
[Install]
WantedBy=multi-user.target
If I run the service from the terminal (i.e. sudo systemctl restart myService
) I can see the VM window popping up and starting correctly. However, if I reboot the system the VM doesn't start and this is the status
I get
Jan 23 12:55:59 home systemd: Started myService service.
Jan 23 12:56:00 home truenas.sh: [AppLoader] Use shipped Linux kernel AIO access library.
Jan 23 12:56:00 home truenas.sh: An up-to-date "libaio" or "libaio1" package from your system is preferred.
Jan 23 12:56:00 home vmplayer: cannot open display: :0
Jan 23 12:56:00 home systemd: myService.service: Main process exited, code=exited, status=1/FAILURE
Jan 23 12:56:00 home systemd: myService.service: Failed with result 'exit-code'.
I thought DISPLAY=:0
on the environment would fix the issue but that's the error I got and I'm not able to fix it.
Victor
(163 rep)
Jan 23, 2023, 06:11 PM
• Last activity: Jan 24, 2023, 03:32 AM
4
votes
2
answers
14553
views
Linux Guest OS: open-vm-tools installed but not running, Restart VMWare Tools Greyed out
I'm trying to figure out if my VMWare tools is running and some of the solutions I found online aren't quite working. If I look at `apt list --installed | grep vm` I see open-vm-tools-desktop/kali-rolling,now 2:12.0.0-2 amd64 [installed] open-vm-tools/kali-rolling,now 2:12.0.0-2 amd64 [installed,aut...
I'm trying to figure out if my VMWare tools is running and some of the solutions I found online aren't quite working. If I look at
apt list --installed | grep vm
I see
open-vm-tools-desktop/kali-rolling,now 2:12.0.0-2 amd64 [installed]
open-vm-tools/kali-rolling,now 2:12.0.0-2 amd64 [installed,automatic]
but if I look at processes running with ps ax | grep vm
it doesn't look to be running
198 ? S 0:17 [irq/16-vmwgfx]
231502 ? Sl 0:01 /usr/bin/vmtoolsd -n vmusr --blockFd 3
231523 ? Sl 0:02 /usr/bin/vmtoolsd
237915 ? Ssl 0:04 /usr/bin/vmtoolsd
237989 ? Ssl 0:00 vmware-vmblock-fuse /run/vmblock-fuse -o rw,subtype=vmware-vmblock,default_permissions,allow_other,dev,suid
247062 pts/2 S+ 0:00 grep --color=auto vm
I've found solutions to restart VM tools with
$ sudo /etc/init.d/vmware-tools start
$ sudo /etc/init.d/vmware-tools stop
$ sudo /etc/init.d/vmware-tools restart
but I don't have any of that in my init.d. The weirdest thing is, sometimes copy/paste into and out of the VM work and then seemingly randomly it stops, that's the real root issue here if anyone knows what's ultimately wrong. The "Reinstall VMWare Tools..." is also greyed out on my licensed VMWare Workstation 15.5
Edit: additionally I tried this answer https://unix.stackexchange.com/a/312820 and now I have removed open-vm-tools but sudo apt-get install open-vm-tools-desktop fuse
is not working, saying I have broken packages:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
fuse3 : Breaks: fuse
E: Unable to correct problems, you have held broken packages.
Kardinal
(141 rep)
May 10, 2022, 11:49 PM
• Last activity: Dec 9, 2022, 09:23 AM
0
votes
0
answers
1030
views
Can't find Appstream and BaseOs folders in RHEL-8-7-0-BaseOS-x86_64
Im running Rhel 8 on my VMware Workstation 15 Pro. For some reason I'm not able to see the Appstream and Baseos folders When I tried running the `yum repolist` command, it displayed the 2 repositories but still can't find them in any folder [![enter image description here][1]][1] I also tried reconn...
Im running Rhel 8 on my VMware Workstation 15 Pro. For some reason I'm not able to see the Appstream and Baseos folders When I tried running the
I also tried reconnecting the iso but it didn't work
Please help
yum repolist
command, it displayed the 2 repositories but still can't find them in any folder


Raj Parayane
(13 rep)
Nov 25, 2022, 06:31 PM
0
votes
1
answers
86
views
How to disable time sync in a VMware shared folder?
My Windows 10 desktop has VMware. To set past time in VMware, I disabled sync options as described here: https://kb.vmware.com/s/article/1189 I just tried to set the date to past time in VMware. And it worked. However, after reading and writing files in a shared directory within Linux (VMware), the...
My Windows 10 desktop has VMware. To set past time in VMware, I disabled sync options as described here: https://kb.vmware.com/s/article/1189
I just tried to set the date to past time in VMware. And it worked.
However, after reading and writing files in a shared directory within Linux (VMware), the time is synced to the current time. How can I disable the time and date sync in the VMware shared folder?
p.s: VMware version is VMware Workstation 16 Player, and Linux is CentOS 5.0.
Carter
(136 rep)
Sep 20, 2022, 05:46 AM
• Last activity: Nov 9, 2022, 09:57 PM
1
votes
1
answers
164
views
Redhat Enterprise Linux 4 / CentOS 4 Anaconda Process Crash During Install in Virtual Machine
On a Windows 10 host with Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz I'm trying to setup a virtual machine installation of Redhat Enterprise Linux 4 to test scenarios for migration project to a modern version. However within VMWare Workstation 16, Hyper-V and Oracle VM Virtual Box 6.1 I am unable to c...
On a Windows 10 host with Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz I'm trying to setup a virtual machine installation of Redhat Enterprise Linux 4 to test scenarios for migration project to a modern version.
However within VMWare Workstation 16, Hyper-V and Oracle VM Virtual Box 6.1 I am unable to complete the install. Process anaconda terminates, call trace references vsnprintf, seq_printf, inode_has_perm, show_cpuinfo, seq_read, vfs_read and system_class.
I've tried text installation, noapic, noprobe options during install but so far have same issue.
Any suggestions if there is config change or install options that can allow this to complete?





Malcolm McCaffery
(115 rep)
Sep 15, 2021, 12:17 AM
• Last activity: Nov 3, 2022, 02:46 AM
2
votes
1
answers
6565
views
Installing VMWare Tools
I am trying to install VMWareTools 9.6.5-270 on my freshly downloaded Linux Mint 19 from OSBoxes. I am running it inside VMWare Workstation 10.0.7 build-2844087 Like many online, I cannot get past the `The path "/usr/bin/gcc" is not valid path to the gcc binary` issue. I have read a few articles her...
I am trying to install VMWareTools 9.6.5-270 on my freshly downloaded Linux Mint 19 from OSBoxes. I am running it inside VMWare Workstation 10.0.7 build-2844087
Like many online, I cannot get past the
The path "/usr/bin/gcc" is not valid path to the gcc binary
issue. I have read a few articles here and there that state there are pre-requisites that need to be installed. So far I have installed:
- gcc
- binutils
- make
- linux-source
- build-essential (12.4ubuntu1)
- linux-headers-4.15.0-20-generic
So which package did I forget to install? Or is the install script mistakenly detecting the path as wrong?
David Brossard
(195 rep)
Aug 29, 2018, 03:21 PM
• Last activity: Oct 3, 2022, 09:26 PM
0
votes
2
answers
2905
views
Gnome 42 Wayland - VMware - A white square appears when I click on the edges of the screen
A white square appears when I click on the edges of the screen if I am under `VMware Workstation 16 Pro - 16.2.3 build-19376536`. This thing only happens when I use `Wayland`, with `Xorg` the problem does not arise. I am using `Ubuntu 22.04 LTS Desktop` with `Gnome 42` (Default). This problem has al...
A white square appears when I click on the edges of the screen if I am under
Is there any way to fix it?
VMware Workstation 16 Pro - 16.2.3 build-19376536
.
This thing only happens when I use Wayland
, with Xorg
the problem does not arise.
I am using Ubuntu 22.04 LTS Desktop
with Gnome 42
(Default).
This problem has already been reported at the following link:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4601

Mario Palumbo
(261 rep)
Apr 28, 2022, 01:26 PM
• Last activity: Jul 9, 2022, 04:14 AM
1
votes
0
answers
369
views
"Could not open dev/vmmon" error - every time I start my VMware workstation starts
I use VMware Workstation 16 on my MX Linux. Each time I start it after starting my machine, I get the following error: "could not open /dev/vmmon". Yesterday and again today, I tried to solve this by following the steps mentioned [here](https://unix.stackexchange.com/questions/99388/could-not-open-d...
I use VMware Workstation 16 on my MX Linux. Each time I start it after starting my machine, I get the following error: "could not open /dev/vmmon". Yesterday and again today, I tried to solve this by following the steps mentioned [here](https://unix.stackexchange.com/questions/99388/could-not-open-dev-vmmon-no-such-file-or-directory) . The issue temoporarily gets solved, but it arises again whenever I start my laptop.
Is there any workaround to this problem which can be treated as a permanent solution? Thanks in advance.
belmont
(328 rep)
Oct 24, 2021, 05:44 AM
• Last activity: Jun 3, 2022, 10:14 AM
1
votes
1
answers
9477
views
Increase terminal scale/size on Kali Linux running in VMWare
I have a high resolution screen and I'm running the downloadable Kali VM from their site. The problem is everything looks super tiny because of my host laptop screen resolution. In the guest Kali OS, I've gone to Settings > Appearance > Settings tab > Window Scaling and changed it to 2x which seems...
I have a high resolution screen and I'm running the downloadable Kali VM from their site. The problem is everything looks super tiny because of my host laptop screen resolution. In the guest Kali OS, I've gone to Settings > Appearance > Settings tab > Window Scaling and changed it to 2x which seems to have helped almost everything *except* the terminal. Its the entire terminal program, including the File | Actions | Edit | View | Help toolbar at the top is all too small. Increasing the font size within terminal, only affects the 'main' part of the terminal, but I'd like for the entire terminal program to be scaled up.
I am running the downloadable Kali VM (the full VM, not the just the ISO file) on VMWare Workstation Pro 15.5

Tommy K
(141 rep)
Apr 28, 2022, 08:03 PM
• Last activity: Apr 28, 2022, 08:29 PM
0
votes
1
answers
110
views
Debian 8.0 Not working after installation in vm
I installed Debian 8.0 recently in vmware workstation 16. When Debian boots up after instalation I see the following picture: [![Boot Failure.][1]][1] [1]: https://i.sstatic.net/XH1Gc.png I know this version of Debian was made in 2015, but I really want to use it. Please help! (It does the same thin...
I installed Debian 8.0 recently in vmware workstation 16.
When Debian boots up after instalation I see the following picture:
I know this version of Debian was made in 2015, but I really want to use it.
Please help! (It does the same thing in live cd mode.)

Kornél Kiss
(3 rep)
Jul 10, 2021, 02:41 PM
• Last activity: Jul 11, 2021, 03:14 AM
Showing page 1 of 20 total questions