pgaltieri's Posts

I upgraded to WP 17.5 which ended up causing major headaches when starting VMs.  During this process I upgraded 2 Windows 11 VMs this required re-encryption.  When going back to 17.0.2 these Windows 11 VMs no longer boot, I get a message that says the .vmx file was created by a VMware product incompatible with this version of Vmware Workstation and cannot be used. What do I need to do to be able to use this VM with version 17.0.2 of WP? Paolo  

I'm running Fedora 37 with kernel 6.5.7.  I recently upgraded VMware Workstation Pro to 17.5. Now as soon as I start a VM my laptop locks up solid.  The only option I have is to power cycle.  I have waited up to an hour to see if it recovers, but it doesn't.  This happens with Windows VM or Linux VM.  It happens whether I upgrade the VM or not.  These are all VMs that worked fine before I upgraded VMware.  As a comparison I have no problems running VMs with VirtualBox on the same system. Is there a way to go back to the prior release of VMware Workstation Pro? Paolo

Some time ago I uninstalled workstation pro on one of my Fedora Linux systems.  That system has since been updated to Fedora 37.  Today during an update to the system I got the following error: Cloning into 'vmware-host-modules'... fatal: Remote branch workstation- not found in upstream origin /etc/kernel/install.d/99-vmmodules.install: line 20: cd: vmware-host-modules: No such file or directory make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target 'install'. Stop. warning: %posttrans(kernel-core-6.0.15-300.fc37.x86_64) scriptlet failed, exit status 2 Error in POSTTRANS scriptlet in rpm package kernel-core The error occurs as a result of this line: VMWARE_VERSION=$(cat /etc/vmware/config | grep player.product.version | sed '/.*\"\(.*\)\".*/ s//\1/g') Even though Workstation Pro has been uninstalled /etc/vmware/config still exists with the following data: .encoding = "UTF-8" installerDefaults.componentDownloadEnabled = "yes" installerDefaults.autoSoftwareUpdateEnabled.epoch = "8066165664" installerDefaults.dataCollectionEnabled.epoch = "9436500008" installerDefaults.transferVersion = "1" installerDefaults.autoSoftwareUpdateEnabled = "yes" product.name = "VMware Workstation" telemetryUUID = "b0e8b526-887e-11e9-b472-4cd98f6d8721" acceptEULA = "yes" acceptOVFEULA = "yes" installerDefaults.dataCollectionEnabled = "no" installerDefaults.dataCollectionEnabled.initialized = "yes" How do I make sure there is no trace of VMware on the system? I have reported this problem to Fedora as well. Paolo

Folks,    I have an HP Envy laptop running Windows 11 Pro.  I installed Workstation Pro 16.2 on it and everything worked fine for a while.  After rebooting the system the wireless adapter no longer worked.  I ran the HP hardware tests and it confirmed that the wireless had failed.  I uninstalled Workstation Pro and rebooted the system and now the wireless adapter works fine.  I re ran the HP hardware tests and now it reports the wireless adapter as fine.  So what's going on?  A wired adapter works fine. Paolo

I' running Workstation Pro 16.2.4 of Fedora 35.  Over the last several days I have been getting BSOD on my Windows 11 VMs.  I have also had vmware hang and not display anything.  This has lasted as long as 30 minutes, at which time I rebooted my Linux box.  None of my other VMs are accessible when in this state.  I have attached the screen shots.  Also at this time I have sometimes seen vmware (the program) consuming 100% cpu. Has anyone else experienced this?  On at least one of the Windows 11 VMs I'm running update 22h2. Paolo

I'm running WS 16.2.4 build-20089737 on Fedora 35 with kernel 5.19.12-100.fc35.x86_64.  I've had a Windows 11 VM running for several months and I created a second Windows 11 VM a couple of days ago.  Today both of these VMs crashed due to unrecoverable errors.  I've had Linux VMs running for months without problems.  What would cause this to happen so suddenly? Paolo

I was trying to clone a VM and it faile with the following error: An error occurred while cloning: Read beyond end of object. I tried cloning another VM and it worked fine.  The difference I could see is that the VM that failed to clone had a sub-directory called mksSandbox which the other one did not. This sub-directory mksSandbox also caused another issue.  I decided to delete a VM.  So I selected the "Delete from Disk" option under manage and confirmed I wanted to delete it.  When I went and looked in the directory where my VMs are the one I deleted was still present.  It deleted all the vmx and vmdk files but it left the mksSandbox directory. So I ended up having to delete the VM manually. The cloning issue was reported back in 2014, but I never saw a resolution. I am running Workstation Pro 16.2.4 build-20089737. Paolo

I upgraded to WS 16.2.1 this morning and I have encountered an issue.  I have a Fedora 35 VM running under WS 16.2.1.  The bottom right shows all the devices available to this VM, all are currently marked with a red x.  I try to mount one of the external disk drives, first I get the following message: The device 'Seagate RSS Backup+ Hub BK' was unable to connect to its ideal host controller. An attempt will be made to connect this device to the best available host controller. This might result in undefined behavior for this device. when I click OK I get the following message: The specified device is claimed by another driver (uas) on the host operating system. The device might be in use. To continue, the device will first be disconnected from its current driver. when I click OK the red x goes away and it shows that the disk is connected, however no icon shows up on the desktop for that drive as it did under 16.1.2.  Running fdisk -l does not show the drive either, so how do I access it?  I have tried the same thing on a Fedora 33 and a Fedora 34 VM with the same result. Paolo

My problem is I cannot power on a VM. Here is what happened to get into this state.  I had a VM running, and in the bottom right of workstation pro it displays the devices that can be attached to this VM.  All are currently marked with a red x indication they are currently attached to the host.  Four of these devices are external disk drives, all display "Seagate RSS Portable" when I mouse over them.  One of these drives happens to be the one that contains my VMs.  Since the mouse over does not display the drive label )why?) I ended up trying to mount the drive containing the VMs onto the VM.  This did not work well :-).  However, after restarting vmware I was able to access all of my VMs except one.  This one refused to start and displayed the following error: Unable to change virtual machine power state: Failed to power on '/run/media/pgaltieri/SDNVIRTLAB02/VirtualMachines/VMware/VMs/f34-server-vm/f34-server-vm.vmx'. I ran fsck on SDNVIRTLAB02 disk and there where no errors.  So I tried to create a new VM.  When I got to the Virtual Machine Name section the location was blank, even though I have the location configured in settings.  I complete the rest of the configuration and then it says "loading..." This continues for a few minutes and then display the VM info.  At this point if I try to start the VM so I can install the software I get the same error as above. I have been creating VMs with Workstation Pro for several years and have never encountered this issue. What do I need to do to be able to create a VM and start it? Any assistance is greatly appreciated.  I have attached the vmx file. Paolo

I have a virtual machine to which I added 2 virtual disks which I called opststorage-ubuntu-01 and opststorage-ubuntu-02.  I then added a third disk called opststorage-ubuntu-03.  I then removed disk 01., and it no longer shows up in the virtual machine settings. I then added another disk which I named opstorage-ubuntu-01, since having removed it previously I thought I could re-use the name.  This failed.  I got the message  The path /run/media/pgaltieri/SDNVIRTLAB02/VirtulMachines/opststorage-ubuntu/opststorage-ubuntu-01.vmdk cannot be written to. The problem is that the disk is still there.  In fact every drive that I created and then removed is still there. I'm running Fedora 34 on the VM and on several occasions I got input/output error message when trying to access the new virtual disk which is what prompted me to remove the drive. So why does choosing to remove a drive not actually remove it, and is doing an rm of the file(s) sufficient? Paolo