radamstw's Posts

Looks like it's creating a dump when it fails.  Attaching the log. 
After upgrading to VMware workstation 17.5, one of my VMs is hitting this error when I start it.  Transport (VMDB) error -14: Pipe connection has been broken The VM is a Windows 2019 server. Other ... See more...
After upgrading to VMware workstation 17.5, one of my VMs is hitting this error when I start it.  Transport (VMDB) error -14: Pipe connection has been broken The VM is a Windows 2019 server. Other VMs running Windows 10 and Linux don't seem to have this issue.   
I was able to find a potential solution in the following post: https://communities.vmware.com/t5/VMware-Workstation-Pro/VMWare-Workstation-16-Pro-Ubuntu-22-04-1-VM-unresponsive-with/m-p/2930676/high... See more...
I was able to find a potential solution in the following post: https://communities.vmware.com/t5/VMware-Workstation-Pro/VMWare-Workstation-16-Pro-Ubuntu-22-04-1-VM-unresponsive-with/m-p/2930676/highlight/false#M177704 Specifically, I did the following, which seems to be working: Ran powercfg powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe" Changed virtual hardware for host to 10.x   
I was having this issue on Workstation 17.0.1 running on Win 10.0.19043 and a rancher/k3os linux (based on Ubuntu 20.04).  It would run for about 15 minutes, then freeze up. I tried disabling all H... See more...
I was having this issue on Workstation 17.0.1 running on Win 10.0.19043 and a rancher/k3os linux (based on Ubuntu 20.04).  It would run for about 15 minutes, then freeze up. I tried disabling all Hyper-V features plus Credential Guard and nothing really seemed to work.  It seems to be working now after I did the following: Ran powercfg Changed virtual hardware to 10.x  We'll see if after I reboot if the "fix" is retained. 
Also tried changing the BIOS to use UEFI, but the VM would not boot when I did that. Could not find media. 
Tried changing to UEFI Bios and it would not boot.
Recently updated to VMWare Workstation 17.0.1 and I have noticed one of my VMs which is a custom Linux node based on Ubuntu, is extremely slow to boot, and then will only run for about 10-15 minutes ... See more...
Recently updated to VMWare Workstation 17.0.1 and I have noticed one of my VMs which is a custom Linux node based on Ubuntu, is extremely slow to boot, and then will only run for about 10-15 minutes before it completely freezes.  I have disabled Windows Hyper-V features, and Credential Guard, but this seems to keep getting re-enabled. Everything seems to run better when the CredGuard is disabled, but I need to find a way for it to run without having to check that every time I reboot.