jdb2's Posts

jdb2 · ‎11-02-2023

Well, I just upgraded to VMware Workstation Pro 17.5.0 build-22583795 and I also updated the software and kernel in the Linux Mint 21.1 VM. At first I successfully completed a 9600bps Kermit transfer...

Well, I just upgraded to VMware Workstation Pro 17.5.0 build-22583795 and I also updated the software and kernel in the Linux Mint 21.1 VM. At first I successfully completed a 9600bps Kermit transfer to one of my HP48GXs. Then, I tried it again and the transfer failed in the same was as described in my original post -- the Intel NUC running Linux Mint 19.2 x64 still has *no* problems - there's something wrong with VMWare. Also, there's another symptom : VMWare will randomly lock up, usually when all the VMs are paused or powered off, and I'll have to kill the VMWare VMX process which will generate an error dialog that reads as follows : "Transport (VMDB) error -14: Pipe connection has been broken." Any help would be appreciated. jdb2

jdb2 · ‎10-15-2023

I have several Linux VMs on which I run CKermit to transfer data to and from my HP48 calculators. I've been using a Keyspan USA-19HS USB to 9-pin RS-232 adapter for years for this purpose with no pro...

I have several Linux VMs on which I run CKermit to transfer data to and from my HP48 calculators. I've been using a Keyspan USA-19HS USB to 9-pin RS-232 adapter for years for this purpose with no problems. Now, with a recent update to VMWare Workstation, when I run Kermit and initiate a transfer the transfer fails after the maximum number of retries has been hit and I get a "Protocol Error". I've tested the above with two different calculators, and two different Linux VMs with no change. I also tested it on a native Linux install on an Intel NUC and the transfer worked fine, so, this points to a problem with VMWare. I've tried a Linux Mint 19.1 Tessa x64 VM and a Linux Mint 21.1 Vera x64 VM with no success. I'm running on the latest version of Windows 10 64-bit and my VMWare version is 17.0.2 build-21581411 . Any help would be appreciated. jdb2

jdb2 · ‎02-09-2023

I have been using VMware for *years* and I have had VMs in numerous different states, such as paused, hibernated, suspended, powered off etc. and I have *never* encountered this error condition. If t...

I have been using VMware for *years* and I have had VMs in numerous different states, such as paused, hibernated, suspended, powered off etc. and I have *never* encountered this error condition. If this is something in which data loss can happen, then why, prior to the upgrade starting, doesn't the VMware installer display a warning dialog? Also, I'm pretty sure that the problem is somehow associated with me clicking the checkbox telling the installer to automatically install the "Windows hypervisor platform." Unfortunately, I disabled said platform and rebooted but the problem persists. According to VMware : "Your virtual machine did not resume because of a correctable error. Preserve the suspended state and correct the error." So, the error is apparently correctable, but, how? Can I downgrade VMware to say, version 15 ( and VMware reports that the VM giving me problems is a version 15.x VM ), and then resume the VM and shut it down? I have important data that I don't want to lose by discarding the latest snapshot. The error I'm receiving is usually associated when a paused VM is copied or cloned to different hardware. This did not happen in my case : All I did was upgrade VMware -- the hardware is the same so I don't know why I'm receiving this error. What I plan on doing is backing up all the files associated with this VM and then resuming it with my fingers crossed. Anyways, I payed extra for support when I upgraded to VMware Workstation 17 Pro, so I think I'll create a support ticket. jdb2

jdb2 · ‎02-04-2023

Yesterday, I upgraded my VMware installation to the latest version of VMware Workstation 16 Pro. I think I checked something to do with "automatically install Windows Hypervisor Platform" during the ...

Yesterday, I upgraded my VMware installation to the latest version of VMware Workstation 16 Pro. I think I checked something to do with "automatically install Windows Hypervisor Platform" during the install. After the installation was complete, I attempted to resume a paused VM which I've had installed on my laptop for at least 5 years and I received the following messages : --------------------------- Ubuntu 64-bit - VMware Workstation --------------------------- You are running this virtual machine with side channel mitigations enabled. Side channel mitigations provide enhanced security but also lower performance. To disable mitigations, change the side channel mitigations setting in the advanced panel of the virtual machine settings. Refer to VMware KB article 79832 at https://kb.vmware.com/s/article/79832 for more details. [ ] Do not show this hint again --------------------------- OK --------------------------- The above message is not an error, but I had never received it before the upgrade. --------------------------- Ubuntu 64-bit - VMware Workstation --------------------------- The features supported by the processors in this machine are different from the features supported by the processors in the machine on which the virtual machine state was saved. You may attempt to resume this virtual machine, but doing so may result in unpredictable behavior. Do you wish to resume this virtual machine? --------------------------- Yes No --------------------------- The above is the error / warning message. --------------------------- Ubuntu 64-bit - VMware Workstation --------------------------- An error occurred while restoring the CPU state from file "D:\Users\[censored]\Documents\Virtual Machines\Ubuntu 64-bit\Ubuntu 64-bit-3bdbb6b7.vmss". Your virtual machine did not resume because of a correctable error. Preserve the suspended state and correct the error, or discard the suspended state. --------------------------- Preserve Discard --------------------------- I chose to not resume the VM and preserve the state. The final error message is : --------------------------- VMware Workstation --------------------------- Failed to start the virtual machine. --------------------------- OK --------------------------- I thought that upgrading VMware to version 17 might solve the problem, but it didn't. I'm running VMware Workstation 17 Pro 17.0.1 build-21139696 on a Dell Alienware 17 R5 laptop with the latest and updated version of Windows 10 Pro 64-bit installed. Any help in resolving this issue would be gratefully appreciated. Thanks, jdb2

jdb2 · ‎01-12-2020

I have made a little progress : $ sudo vmhgfs-fuse -o allow_other -o uid=1001 .host:/[censored] /mnt/share $ sudo mount -l zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /...

I have made a little progress : $ sudo vmhgfs-fuse -o allow_other -o uid=1001 .host:/[censored] /mnt/share $ sudo mount -l zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local, multilabel) zroot/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot on /zroot (zfs, local, noatime, nfsv4acls) zroot/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/var/mail on /var/mail (zfs, local, nfsv4acls) zroot/usr/src on /usr/src (zfs, local, noatime, nfsv4acls) zroot/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) zroot/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) zroot/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) zroot/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls) zroot/var/audit on /var/audit (zfs, local, noatime, noexec, nosuid, nfsv4acls) /dev/fuse on /mnt/share (fusefs) $ cd /mnt/share cd: /mnt/share: No such file or directory $ cd /mnt/freebsd-share/ $ ls test.txt $ ls -lah total 3 drwxrwxrwx 2 root wheel 3B Jan 12 12:18 . drwxr-xr-x 4 root wheel 4B Jan 12 12:13 .. -rw-r--r-- 1 jdb2 wheel 0B Jan 12 12:18 test.txt $ touch test2.txt $ ls -lah total 4 drwxrwxrwx 2 root wheel 4B Jan 12 12:22 . drwxr-xr-x 4 root wheel 4B Jan 12 12:13 .. -rw-r--r-- 1 jdb2 wheel 0B Jan 12 12:18 test.txt -rw-r--r-- 1 jdb2 wheel 0B Jan 12 12:22 test2.txt $ It seems I can now mount the shared directory, but, anything I do to it doesn't show up in the host directory Any help would be appreciated Thanks, jdb2

jdb2 · ‎01-12-2020

I have VMware® Workstation 15 Pro 15.5.1 build-15018445 which I'm running on a Linux Mint 19.2 Cinnamon 64-bit host on an Intel NUC8i7BEH. I've successfully installed FreeBSD 12.1 as a guest in V...

I have VMware® Workstation 15 Pro 15.5.1 build-15018445 which I'm running on a Linux Mint 19.2 Cinnamon 64-bit host on an Intel NUC8i7BEH. I've successfully installed FreeBSD 12.1 as a guest in VMware and I *almost* have everything working except for shared folders. I've tried just about everything but, although they're enabled, went I try to mount a shared folder from within the guest OS, I get an error of "file not found" or something like that. Any help would be appreciated. Thanks, jdb2

jdb2 · ‎01-06-2019

Hello. I have an Alienware 17 R5 laptop with Windows 10 Pro x64 installed. I recently installed VMware Workstation 15 Pro and then I installed Linux Mint 19 Cinnamon x64 as a new VM. Everything i...

Hello. I have an Alienware 17 R5 laptop with Windows 10 Pro x64 installed. I recently installed VMware Workstation 15 Pro and then I installed Linux Mint 19 Cinnamon x64 as a new VM. Everything is fine and shared folders work, but, both copy and paste and drag and drop do not work, no matter the direction ( ie. to/from guest/host ). I'm using VMware Workstation 15 Pro version 15.0.2 build 10952284 and I have the latest, I believe, VMware Tools installed with a version of 10.3.2-9925305. In the VM's setting under "Guest isolation" I have both "drag and drop" and "copy and paste" checked. Any help would be appreciated. Thanks, jdb2

jdb2 · ‎10-08-2009

The problem for me turned out to be that when you click the power on button it makes a little 'boomp' sound, and playing that sound caused vmware to not be able to access the sound card. Th...

The problem for me turned out to be that when you click the power on button it makes a little 'boomp' sound, and playing that sound caused vmware to not be able to access the sound card. The setting for this is actually in the gnome settings, not the KDE settings, even on kubuntu. These steps resolved the sound problem for me: 1. Go to a terminal (or hit alt-F2) and run: gnome-control-center 2. Under the Hardware section there is a Sound icon, click that. Click the Sounds tab and uncheck "Play alerts and sound effects". I can play sound in either the host or the guest while the VM is running, just not at the exact same time. Unfortunately for me, everything under the sounds tab is greyed out. jdb2

jdb2 · ‎04-24-2009

Sure, I understood that much. But the guest OS looking at /dev/dsp is really pointing to a virtual device created for its benefit by Vmware Workstation. Its not looking at THE REA...

Sure, I understood that much. But the guest OS looking at /dev/dsp is really pointing to a virtual device created for its benefit by Vmware Workstation. Its not looking at THE REAL /dev/dsp of the host. This virtual /dev/dsp gets routed whereever vmware workstation sends it based on the config file for that VM. So I'm just as confused as ever. ?:| I neither stated nor implied any such idea. The guest OS is *encapsulated within a VMware virtual machine* -- *it does not and cannot directly access the host machine's hardware;* it is isolated from the host machine's hardware and software by the VM and is consequently oblivious to their existence. jdb2

jdb2 · ‎04-24-2009

I found a partial solution here : . The only problem is that the host and guest can't access /dev/dsp at the same time, so you can't have, say, a CD playing in the backgrou...

I found a partial solution here : . The only problem is that the host and guest can't access /dev/dsp at the same time, so you can't have, say, a CD playing in the background on the host while you're playing eg. a flash shoot-em-up game on the guest and get a mixture of audio out of your sound card from both sources. From what I've seen ( or heard ) it looks like the host takes precedence. jdb2 I don't quite understand why the VM would be accessing the host's hardware. I thought that was all virtualized, and the vmware running in the host merely handed sound from the guest off to the host os. When I said "guest" I of course meant the guest's virtual machine. From the guest VM's OS's point of view it thinks it's accessing a physical sound card. jdb2

jdb2 · ‎04-13-2009

I found a partial solution here : . The only problem is that the host and guest can't access /dev/dsp at the same time, so you can't have, say, a CD playing in the background on the host while...

I found a partial solution here : . The only problem is that the host and guest can't access /dev/dsp at the same time, so you can't have, say, a CD playing in the background on the host while you're playing eg. a flash shoot-em-up game on the guest and get a mixture of audio out of your sound card from both sources. From what I've seen ( or heard ) it looks like the host takes precedence. jdb2

jdb2 · ‎04-12-2009

I enabled "Settings->Options->Advanced->Gather debugging information: full" and "Settings->Options->Advanced->Log virtual machine progress periodically." After powering on the VM I grepped vmware...

I enabled "Settings->Options->Advanced->Gather debugging information: full" and "Settings->Options->Advanced->Log virtual machine progress periodically." After powering on the VM I grepped vmware.log for 'sound' . Here are the results : Apr 12 22:46:42.817: vmx| DICT tag.soundConfig = devices_sound.htm Apr 12 22:46:42.818: vmx| DICT sound.present = TRUE Apr 12 22:46:42.818: vmx| DICT sound.fileName = -1 Apr 12 22:46:42.818: vmx| DICT sound.autodetect = TRUE Apr 12 22:46:42.818: vmx| DICT sound.pciSlotNumber = 33 Apr 12 22:46:42.819: vmx| DICT tag.soundConfig = devices_sound.htm Apr 12 22:46:57.289: vcpu-0| [http://msg.pciSound.DspOpenFailed|http://msg.pciSound.DspOpenFailed] Failed to open sound device /dev/dsp1: Invalid argument Apr 12 22:46:57.289: vcpu-0| [http://msg.device.startdisconnected|http://msg.device.startdisconnected] Virtual device sound will start disconnected. Maybe someone more knowledgeable about VMware internals can make some sense of this. Regards, jdb2

jdb2 · ‎04-11-2009

Hello. I use VMware Workstation 6.5 version "6.5.2 build-156735" on Kubuntu Linux. Ever since Kubuntu 8.04 I have been unable to get the virtual sound device working in a Windows XP guest -- VM...

Hello. I use VMware Workstation 6.5 version "6.5.2 build-156735" on Kubuntu Linux. Ever since Kubuntu 8.04 I have been unable to get the virtual sound device working in a Windows XP guest -- VMware would complain about insufficient permissions on /dev/dsp. Well, I've upgraded my OS to Kubuntu 9.04 Jaunty Beta 1 and the same problem is back in a slightly different form : Now when I attempt to resume or power-on the guest I get the following messages : "Failed to open sound device /dev/dsp1: Invalid argument" and "Virtual device sound will start disconnected." Does anyone have a clue about how to solve the above? I've done some searching, but all I could find was the same question, unanswered. You would think VMware would have given this bug a high priority by now. Any help would be appreciated, Regards, jdb2

All

jdb2's Posts

Re: Latest version of VMWre Workstation doesn't work with Keyspan USB to RS-232 adapter...

Latest version of VMWre Workstation doesn't work with Keyspan USB to RS-232 adapter...

Re: Can't resume VM after upgrading VMware

Can't resume VM after upgrading VMware

Re: Can't get shared folders working in FreeBSD 12.1 guest

Can't get shared folders working in FreeBSD 12.1 guest

Copy, paste, drag and drop not working in VMware Workstation 15 Pro with Linux Mint 19 Cinnamon x64

Re: The return of the infamous /dev/dsp bug

Re: The return of the infamous /dev/dsp bug

Re: The return of the infamous /dev/dsp bug

Re: The return of the infamous /dev/dsp bug

Re: The return of the infamous /dev/dsp bug

The return of the infamous /dev/dsp bug