valerio_vanni's Posts

Some month ago I upgraded from Workstation Pro 14 to 17 on a Linux host (Debian 10). At the time of upgrade I used kernel 4.20.17, and everything was running fine. Then I tried with a 5.15 kernel (also a 5.10, same outcome), and soon I noticed guest slowing down. With casual occurring, but enough often to be annoying (3-4 times per hour). Lags of 10-15 seconds, guest totally unresponsive. No mouse click nor key press. When guest was lagging, host was ok and responded as usual. Since I still have 4.20.17, I did many test and can confirm: 4 is ok, 5 lags. Since I knew that 5 introduced some mitigation for security issues, I tried disable one of them with tsx=on on boot line.   And this way also 5 works without lags. Has anyone experienced something similar?

I mean internal help, opened from UI. Workstation is 17 Pro.   In my Debian Buster, default browser in kde control panel is firefox. Workstation help is opened in Epiphany. Not a real issue. If I try updating to Bullseye, default browser is still Firefox. But Workstation help stops working. I see a message telling "abiword not found". Abiword? Why does it call Abiword?   I don't find any options in vmware settings.  

I'm looking at this page: https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-41311258-4AAD-42B9-B0DE-CE7457298BFA.html#GUID-41311258-4AAD-42B9-B0DE-CE7457298BFA Is it something updated, or (as it seems to me) a bunch of copy and past from various ages? It's unlikely that someone upgrade such versions, while the latest are not mentioned. -------------------------------- Verify that all virtual machines are Workstation 7.x, 8, 9, 10 or 11 virtual machines. Direct upgrades from Workstation 2 and 3 virtual machines are not supported  No mention for 4-5-6. And it seems that 12 and on are not ok, that's absurd. If a virtual machine was created with a version of Workstation earlier than Workstation 5.5 and it has a snapshot, delete the snapshot. But if just said that less than 7 is not supported... If you are upgrading from Workstation 4, 5.x, 6.x, or 7.x, and the previous version of Workstation used bridged settings to map virtual networks to specific physical or virtual adapters, record those settings. The same. If you are upgrading Workstation 6.x on Windows XP to the current version of Workstation Pro on Windows Vista or Windows 7, verify that Service Pack 2 is installed and then upgrade the host operating system to Windows Vista or Windows 7. But it seems that Vista and 7 are not supported as host, so why write lines about them?  

Some month ago I did some test of Workstation 17.0.0 on linux kernel 5.*. On 5.10.* it worked out of the box, on 5.15.* module compile failed and I had to use these patches: https://github.com/mkubecek/vmware-host-modules/ Some day ago I did another test, with Workstation 17.0.2 on kernel 5.15.114: it worked without patches. Have there been some changes on vmware side? Or on kernel side?

It's a Workstation 14 Pro, and the issue happens only with this virtual machine (or, better, with this virtual disk, see later). I tried to clone other VMs, and it works. The VM itself works. It starts, it shuts down etc. vmdk is single file, not preallocated. "Defrag" and "Compact" return no error. But when I try to clone it I get this error. Both from specified snapshot and current state. In the end, I tried to delete all snapshot and now I have none of them, only current state. I got no error during snapshot deletion / consolidation phase. I'm trying a full clone. I also tried to delete VM, create another and mount the same disk: it fails again to clone, so it seems that the issue is inside vmdk and not in VM config. vmware.log is untouched at the time of cloning attempt, and inside ui-log in /tmp/ I find these lines:   2023-05-28T14:29:08.581+02:00| vthread-12| I125: VTHREAD initialize thread 12 "vthread-12" tid 19613 2023-05-28T14:29:08.585+02:00| vthread-12| I125: DISKLIB-DSCPTR: Opened [0]: "Ravenna-orig.vmdk" (0xe) 2023-05-28T14:29:08.585+02:00| vthread-12| I125: DISKLIB-LINK : Opened '/mnt/sata2/WinXP-RA/Ravenna-orig.vmdk' (0xe): monolithicSparse, 117247536 sectors / 55,9 GB. 2023-05-28T14:29:08.585+02:00| vthread-12| I125: DISKLIB-LIB : Opened "/mnt/sata2/WinXP-RA/Ravenna-orig.vmdk" (flags 0xe, type monolithicSparse). 2023-05-28T14:29:08.615+02:00| vthread-12| I125: SNAPSHOT: SnapshotClone: Failed to set the mode for the new config file: 2 2023-05-28T14:29:08.615+02:00| vthread-12| I125: SNAPSHOT: SnapshotConfigInfoOpenVmsd: Creating new snapshot dictionary, '/home/valerio/vmware_machines/Clone of WinXP-RA/Clone of WinXP-RA.vmsd'. 2023-05-28T14:29:08.616+02:00| vthread-12| I125: DISKLIB-DSCPTR: Opened [0]: "Ravenna-orig.vmdk" (0xe) 2023-05-28T14:29:08.616+02:00| vthread-12| I125: DISKLIB-LINK : Opened '/mnt/sata2/WinXP-RA/Ravenna-orig.vmdk' (0xe): monolithicSparse, 117247536 sectors / 55,9 GB. 2023-05-28T14:29:08.616+02:00| vthread-12| I125: DISKLIB-LIB : Opened "/mnt/sata2/WinXP-RA/Ravenna-orig.vmdk" (flags 0xe, type monolithicSparse). 2023-05-28T14:29:08.616+02:00| vthread-12| I125: DISKLIB-LIB_CLONE : Couldn't get adapter type of src disk while creating clone param : One of the parameters supplied is invalid (1). 2023-05-28T14:29:08.616+02:00| vthread-12| I125: SNAPSHOT: SnapshotCloneDisk: Failed to get createParam for '/home/valerio/vmware_machines/Clone of WinXP-RA/Ravenna-orig-cl1.vmdk': One of the parameters supplied is invalid (1).SNAPSHOT: SnapshotCloneDisk failed: One of the parameters supplied is invalid. 2023-05-28T14:29:08.616+02:00| vthread-12| I125: SNAPSHOT: SnapshotCloneDisks failed: One of the parameters supplied is invalid (5) 2023-05-28T14:29:08.616+02:00| vthread-12| I125: SNAPSHOT: SnapshotClone failed: One of the parameters supplied is invalid (5) 2023-05-28T14:29:08.616+02:00| vthread-12| I125: SNAPSHOT: Snapshot_CloneWithFlags failed: One of the parameters supplied is invalid (5) 2023-05-28T14:29:08.616+02:00| vthread-12| I125: Vix: [19613 hostAgentStuff.c:347]: Error VIX_E_FAIL in VixVM_CloneObsolete(): Unknown error 2023-05-28T14:29:08.616+02:00| vthread-12| I125: Cmd /vm/#e389d50c39d7a6fb/cmd/##410/op/snapshotClone/ failed: Cloning failed: 2023-05-28T14:29:08.616+02:00| vthread-12| I125+ One of the parameters supplied is invalid 2023-05-28T14:29:08.616+02:00| vthread-12| I125:  

I run Vmware Workstation 14 on a Linux Debian host. I find, on many virtual machines, an excessive disk space usage. For example, I analyze a Windows 10 Guest. Virtual disk is 60 GB, single file not preallocated. Vmware says "Current size 22.5 GB used". But the VM folder is 127 GB: why? I've already deleted all snapshot, "defragment disk" and "compact disk" from Vmware WS. I find inside VM directory many vmdk files. The referenced one in VM properties is Windows10-cl2.vmdk, 23 GB. But I find also 5 Windows10-cl2-0000***.vmdk, that account for the rest. The latest is 2 month old, the others older than it. Can I delete them?   If I take a full clone, result is 25 GB.  

I am one of the old cpu owners that cannot use 14. So I have to buy 14 and use 12 (now I have 10, and I need to upgrade it). I've searched but I was not able to understand how downgrading licenses works. Here I find an howto about technical downgrade: Downgrading from VMware Workstation Pro 14 to VMware Workstation 12 (2128613) | VMware KB  And here another one about license, but it's not about Workstation. How to downgrade license keys in My VMware (2006975) | VMware KB How do I downgrade? Can I buy 14 and use directly its license key on 12?