I got impatient and did something silly without thinking:  I hit the [Cancel] button on the "Cleaning up deleted files..." dialog after deleting all my snapshots.  Don't get me wrong, I wanted all the snapshots deleted; it's just that if I'd thought about it at all I would have allowed the operation to just complete normally.

It canceled right away, and I ended up with 600+ GB of .vmdk files that I couldn't see a direct way to get rid of, even though my VM has only about 200 GB of storage used.

After mulling this over a couple of days, I thought to make a new snapshot then delete it and see if the resulting cleanup would do the rest of the job.  Looks like it worked.

Thought I'd share this tidbit.  Perhaps there's a proper menu entry I didn't know about or something, but it's nice when the code actually works when tasked with doing something shall we say non-standard or atypical.  Thanks VMware!

-Noel

Hello Everyone,

I have created a Virtual Machine with Windows 10 and installed a bunch of software. A temporary license begins when I open the installed software. When I perform a full clone of the original VM the software that I installed is not there. It takes about 45 minutes to install the software so I am trying to bypass that process. Any ideas? Thanks!

So I am running a VMWare ESX virtual machine with Ubuntu Server 16.04 LTS and I was updating it today.

Then I got this message from the console at the end of sudo apt upgrade:

update-initramfs: Generating /boot/initrd.img-4.4.0-165-generic

W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

gzip: stdout: No space left on device

E: mkinitramfs failure find 141 cpio 141 gzip 1

update-initramfs: failed for /boot/initrd.img-4.4.0-165-generic with 1.

dpkg: error processing package initramfs-tools (--unpack):

subprocess installed post-installation script returned error exit status 1

E: Sub-process /usr/bin/dpkg returned an error code (1)[/code]

Worrysome, so I checked the drive space:

[code]

~$ df -h

Filesystem                         Size  Used Avail Use% Mounted on

udev                               476M     0  476M   0% /dev

tmpfs                              100M   15M   85M  15% /run

/dev/mapper/agivpnserver--vg-root   28G  4.8G   22G  18% /

tmpfs                              497M     0  497M   0% /dev/shm

tmpfs                              5.0M     0  5.0M   0% /run/lock

tmpfs                              497M     0  497M   0% /sys/fs/cgroup

/dev/sda1                          472M  461M     0 100% /boot

tmpfs                              100M     0  100M   0% /run/user/1000

# pvdisplay

  --- Physical volume ---

  PV Name               /dev/sda5

  VG Name               agivpnserver-vg

  PV Size               29.52 GiB / not usable 2.00 MiB

  Allocatable           yes (but full)

  PE Size               4.00 MiB

  Total PE              7557

  Free PE               0

  Allocated PE          7557

  PV UUID               UyylJC-4uof-Gvmz-ZscZ-vYoq-Ycbg-kyP5AF

Notice that the virtual disk I use has lots of free space but just not the boot partition on /dev/sda1...

What can I do to remedy this?

I am just about to upgrade to Ubuntu Server 18.04 LTS, so presumably I need a larger boot partition.

I am not an Ubuntu admin level user so the disk space here was allocated by the Ubuntu installer when it was set up 3 years ago.

Hello.

When I use disk utility to map virtual drive as local volume (from virtual machine settings)

I can access the drive via explorer and regular command prompt, but not from applications that run as administrator (CMD as admin).

Any suggestions how to work around this limitation?

Thanks.

Windows 10 x64 (UAC disabled)

VMWare 12.5.2

Added a screenshot

After Windows 10 Update (or VM-Workstation 15.5) I can't start the VM's

VM-Workstation 15.5

Host: Windows 10 pro (update newest) Windows 10, Version 1903

VMs: Windows 10 also

Error Message:  "Failed to power on ..."

Please Help!

RT, i upgraded the host OS to win10 1903 a few days ago. then i found vmware can't report battery info to guest OS. if the guest os is win98se, the guest OS will hang during boot. if the guest os is winme, it will hang when you open power management -> power meter tab. if the guest os are others eg. 98/2k/xp/vista/7……, it displays the battery level 0%. if you unplug the ac adapter to use battery, the guest os will say the battery is low. i tried vm 14.1.7 & 15.0.4, they are all same.

the screenshot below is winme. in this picture i switched to the power meter tab but the content is still the tab power scheme. it already hung.

this is win98 original not 98se. the battery level is 0%

Author :

URL : http:////docs.vmware.com/en/VMware-Workstation-Pro/15.0/com.vmware.ws.using.doc/GUID-0EE752F8-C159-487A-9159-FE1F646EE4CA.html

Topic Name : Using VMware Workstation Pro

Publication Name : Using VMware Workstation Pro

Product/Version : VMware Workstation Pro/15.0

Question :

nested virtualization

I have a linux guest running Debian Buster (though this problem goes much further back) under a Windows 10 host. I have "Accelerate 3D graphics" enabled, with 2GB of graphics memory allocated. This VM has most of the resources of my workstation dedicated to it.

I'm getting, fairly frequently, errors in dmesg that look like this:

[255847.503765] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command "SVGA_3D_CMD_DX_SET_QUERY_OFFSET" causing device error.                                           

[255847.503779] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer offset is 0                                                                                

[255847.503786] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command size is 16

[255847.503935] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command "SVGA_3D_CMD_DX_BEGIN_QUERY" causing device error.                                                

[255847.503942] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer offset is 0                                                                                

[255847.503950] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command size is 12

[255847.504071] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command "SVGA_3D_CMD_DX_END_QUERY" causing device error.                                                  

[255847.504079] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command buffer offset is 0                                                                                

[255847.504086] [drm:vmw_cmdbuf_work_func [vmwgfx]] *ERROR* Command size is 12

[255847.511801] code[77548]: segfault at 7f045f489fff ip 00007f036952f627 sp 00007ffddd154cd0 error 6 in vmwgfx_dri.so[7f0369176000+82e000]

There are usually a few hundred of these former errors before the segfault. Once I get a few segfaults, the entire guest locks up. Sometimes the segfaults look more directly like they came from the driver: those are the ones that fully lock the machine.

The easiest (though not only) way of recreating this is to open vscode and use it for a while. Many other electron apps will eventually cause the same issue. That said, it's probably a bad sign that

Turning off the accelerate 3D option isn't really a workable solution, as the applications become unbearably and unusably slow.

Does anyone know of a workaround or fix? I'm getting awfully close to getting rid of the workflow I've been using for many, many years.

Hello, recently there was an update for win10 and since then I can not start my VMware Workstation 15 Pro

Here is such a mistake now:

"VMware Workstation cannot connect to the virtual machine. Make sure you have rights to run the program, access all directories the program uses, and access all directories for temporary files. The VMX process exited prematurely".

Please help solve.

It's a delirium from 2 weeks to now ...

I run vmware workstation pro 15 as administrator as always in Windows 10 Professional ...

All services are active and running ...

I try to start a vm that ran from time and nothing happens but 'Internal error' ...

I try again and 'Cannot find a valid peer process to connect to.' ...

If I try again ... sometimes vm starts sometimes not ... sometimes after 1 try sometimes after 10/15

The relative log in C:\Users\<my user>\AppData\Local\Temp\vmware-<my user> shows those interesting lines :

.......

2019-09-16T18:09:49.525+02:00| vmx| I125: Module 'CPUID' initialization failed.

2019-09-16T18:09:49.525+02:00| vmx| I125: Vix: [mainDispatch.c:833]: VMAutomation_LateShutdown()

2019-09-16T18:09:49.525+02:00| vmx| I125: Vix: [mainDispatch.c:782]: VMAutomationCloseListenerSocket. Closing listener socket.

2019-09-16T18:09:49.525+02:00| vmx| I125: Flushing VMX VMDB connections

2019-09-16T18:09:49.525+02:00| vmx| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'

2019-09-16T18:09:49.525+02:00| vmx| I125: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)

2019-09-16T18:09:49.525+02:00| vmx| I125: VigorTransport_ServerDestroy: server destroyed.

2019-09-16T18:09:49.525+02:00| vmx| I125: WQPoolFreePoll : pollIx = 2, signalHandle = 768

2019-09-16T18:09:49.525+02:00| vmx| I125: WQPoolFreePoll : pollIx = 1, signalHandle = 776

2019-09-16T18:09:49.525+02:00| vmx| W115: Failed to initialize VM.

...

All solutions that I read here in communities it's useless ...

Can someone help me ???

Thanks

Hi!

my problem is the following:

Running VMware Workstation Pro 14 (14.1.1 build-7528167). None of my guest VM's can contact my host machine, and my host machine cannot contact the guest machines. This occurs when I'm using bridged mode for the guest NIC's. Other machines on my network can contact the guest VM's and the guest VM's can contact other machines on my network; they also have Internet access. This seems to just be guest to host and host to guest communication issues. If I switch from bridged to host only or NAT it works OK. I've tried to uninstall>reboot>reinstall VMware workstation. I've tried resetting the network settings to default in the Virtual network app. I can see the VMware bridge driver on my host machines physical NIC. I've tried uninstalling and reinstalling it. I've turned off the firewalls on both machines.

I am getting an error when trying to start a vm with an nonpersistent disk.

The error is:

Power on failure messages: One of the parameters supplied is invalid

Cannot open the disk '/run/media/david/External/DW/Server2016DWM_vmware.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

I see this in the log output:

2019-10-17T19:05:14.311-07:00| vmx| I125: DISK: OPEN scsi0:0 '/run/media/david/External/DW/Server2016DWM_vmware.vmdk' independent-nonpersistent R[]

2019-10-17T19:05:14.872-07:00| vmx| I125: DISKLIB-DSCPTR: Opened [0]: "Server2016DWM_vmware.vmdk" (0xe)

2019-10-17T19:05:14.873-07:00| vmx| I125: DISKLIB-LINK  : Opened '/run/media/david/External/DW/Server2016DWM_vmware.vmdk' (0xe): monolithicSparse, 4294965248 sectors / 2 TB.

2019-10-17T19:05:14.873-07:00| vmx| I125: DISKLIB-LIB   : Opened "/run/media/david/External/DW/Server2016DWM_vmware.vmdk" (flags 0xe, type monolithicSparse).

2019-10-17T19:05:14.873-07:00| vmx| I125: DISKLIB-LIB_MISC   : DiskLib_GetStorageBlockSizes: Failed to get storage block sizes, The virtual disk requires a feature not supported by this program.

2019-10-17T19:05:14.886-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE CHILD: "./Server2016DWM_vmware.vmdk.REDO_z3ujYx" -- monolithicSparse grainSize=128 policy=''

2019-10-17T19:05:14.886-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'file'

2019-10-17T19:05:14.886-07:00| vmx| I125: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)

2019-10-17T19:05:14.886-07:00| vmx| I125: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).

2019-10-17T19:05:14.892-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE CHILD: "./Server2016DWM_vmware.vmdk.REDO_pVl9Jz" -- monolithicSparse grainSize=128 policy=''

2019-10-17T19:05:14.893-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'file'

2019-10-17T19:05:14.893-07:00| vmx| I125: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)

2019-10-17T19:05:14.893-07:00| vmx| I125: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).

2019-10-17T19:05:14.896-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE CHILD: "./Server2016DWM_vmware.vmdk.REDO_UqfMIA" -- monolithicSparse grainSize=128 policy=''

2019-10-17T19:05:14.897-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'file'

2019-10-17T19:05:14.897-07:00| vmx| I125: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)

2019-10-17T19:05:14.897-07:00| vmx| I125: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).

2019-10-17T19:05:14.899-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE CHILD: "./Server2016DWM_vmware.vmdk.REDO_gAOgRy" -- monolithicSparse grainSize=128 policy=''

2019-10-17T19:05:14.899-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'file'

2019-10-17T19:05:14.899-07:00| vmx| I125: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)

2019-10-17T19:05:14.899-07:00| vmx| I125: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).

2019-10-17T19:05:14.902-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE CHILD: "./Server2016DWM_vmware.vmdk.REDO_wluojy" -- monolithicSparse grainSize=128 policy=''

2019-10-17T19:05:14.902-07:00| vmx| I125: DISKLIB-LIB_CREATE   : CREATE-CHILD: Creating disk backed by 'file'

2019-10-17T19:05:14.902-07:00| vmx| I125: DISKLIB-LIB_CREATE   : Failed to create link: One of the parameters supplied is invalid (1)

2019-10-17T19:05:14.902-07:00| vmx| I125: DISKLIB-LIB_CREATE   : DiskLib_CreateChild: failed to create child disk: One of the parameters supplied is invalid (1).

2019-10-17T19:05:14.902-07:00| vmx| I125: DISK: Failed to create child: One of the parameters supplied is invalid (1) 8689.

2019-10-17T19:05:14.902-07:00| vmx| I125: DISK: Opening disks took 591 ms.

2019-10-17T19:05:14.902-07:00| vmx| I125: Module 'Disk' power on failed.

My first guess would be the "CREATE CHILD" error. I have access to write to the location, so its not a permission issue.

Any Ideas what is causing this?

The VM boots fine when not nonpersistent. Also this vm has no snapshots at all.

Hello,

I have win 10 installed, and i have VMware Workstation 15 Player installed, where Windows XP is installed as guest OS.

When I run Windows XP on VMware, will it detect FireWire camera connected to pc, after I install driver on xp for it ?

I only need Windows xp for the camera, nothing else. As the camera driver is not working on newer OS.

It is Olympus DP25 for microscope.

I hope you can help me

Thanks

Hi guys!

I have an old motherboard GA-990FXA-D3 that I have an old Asus GeForce 9600GT graphics Nvidia graphics card....

I am running Vmware workstation 15 pro and feel that it is time to improve on the hosts graphics....

I have Linux on this machine...Debian 10...

Can someone recommend a good graphics card that will play well with vmware workstation 15 pro....

I don't play games and this machine is just a work horse for imaging customer computers....

Thanks

Automatic upgrade to 15.5 from 15.1 fails and destroy my previous installation. host OS: ubuntu 16.4

It is not possible to run again any VMware installation. Neither the previous 15.1 bundle:

Extracting VMware Installer...done.

[AppLoader] Use shipped Linux kernel AIO access library.

An up-to-date "libaio" or "libaio1" package from your system is preferred.

Gtk-Message: 10:57:23.193: Failed to load module "canberra-gtk-module"

/usr/lib/vmware-installer/3.0.0/vmis-launcher: error while loading shared libraries: libpython3.7m.so.1.0: cannot open shared object file: No such file or directory

Nor the new one (I tray to use the workaround  Re: Workstation 15.5 for linux installation fails but the bundle is not recoginec, I can t acces it as sudo ./VMware etc the file is listed in my dir with ls but in white instead in green)

Therefore I am not able to use anymore my workstation licensed product

I am very disappointing that an official upgrade let me without my computer to work.

Bonjour,

Après avoir réussi une première fois à débloquer VMWare avec unlocker j'ai été contraint pour d'autres raisons de restaurer W10 (sauvegarde Acronis) et depuis impossible de débloquer vnware donc plus de possibilité d'installer un MacOS. J'ai restauré une ancienne sauvegarde de W10,réinstallé VMWare  et là encore pas de déblocage!!! Je suis revenu à ma version de W10 donc à mon point de départ et depuis je cherche désespérément une solution.

Merci pour toute aide.

J.H.

There's a 100% reproducible bug in VMware Workstation 15.5.0 build-14665864.  I've only tested on a Windows host.

1. Install VMware Workstation 15.5.0 build-14665864 on a Windows host.
2. Install 7-zip on your host.
3. Drag a file from a 7-zip-opened archive into a VM (any OS, as long as tools are installed)
4. Enjoy your Stack Buffer Overrun (/GS Exception)

0:000> !exploitable -v

!exploitable 1.6.0.0

HostMachine\HostUser

Executing Processor Architecture is x64

Debuggee is in User Mode

Debuggee is a live user mode debugging session on the local machine

Event Type: Exception

Exception Faulting Address: 0x7ffae6bec4df

Second Chance Exception Type: STATUS_STACK_BUFFER_OVERRUN (0xC0000409)

Exception Hash (Major/Minor): 0xef80f209.0x6a72959b

Hash Usage : Stack Trace:

Major+Minor : ntdll!LdrpICallHandler+0xf

Excluded    : ntdll!RtlpExecuteHandlerForException+0xf

Excluded    : ntdll!RtlDispatchException+0x219

Major+Minor : ntdll!KiUserExceptionDispatch+0x2e

Major+Minor : ntdll!LdrpDispatchUserCallTarget+0xe

Major+Minor : vmware_vmx+0x9618c

Major+Minor : vmware_vmx+0x572d46

Minor       : vmware_vmx+0x57a352

Minor       : vmware_vmx+0x9677f

Minor       : vmware_vmx+0x96a97

Minor       : vmware_vmx+0x58b21

Minor       : vmware_vmx+0x235c50

Minor       : vmware_vmx+0x1683a

Minor       : vmware_vmx+0x16c45

Minor       : vmware_vmx+0x165f8

Minor       : vmware_vmx+0x15639

Minor       : vmware_vmx+0x499c2b

Minor       : vmware_vmx+0xe626

Minor       : vmware_vmx+0xd310

Minor       : vmware_vmx+0xdcfb

Minor       : vmware_vmx+0xb6c2

Minor       : KERNEL32!BaseThreadInitThunk+0x14

Minor       : ntdll!RtlUserThreadStart+0x21

Instruction Address: 0x00007ffae6bec4df

Description: Stack Buffer Overrun (/GS Exception)

Short Description: GSViolation

Exploitability Classification: EXPLOITABLE

Recommended Bug Title: Exploitable - Stack Buffer Overrun (/GS Exception) starting at ntdll!LdrpICallHandler+0x000000000000000f (Hash=0xef80f209.0x6a72959b)

An overrun of a protected stack buffer has been detected. This is considered exploitable, and must be fixed.

Hi

I cant install on debian 9 stretch (OVH-hosting) the VmWare 15 Pro or 12.

Id installed build-essential and kernel header too! (OVH-Kernel)

Id vmware-modconfig.. but still failed..

Everything is OK, vmware want to start .. compile.. and failed..

this is failed:

Virtual Machine Communication Interface

vSockets

Can someone help me?

What should i install? how can i enable "vSocket" and "Virtual Machine Communication Interface" (install?) ?

Thanks!

What on earth is causing this?

Fresh install of VMware 15. Snapshots work with no disks attached to the vm. when I attach a disk, I get this error trying to snapshot the system.

Any ideas whats causing it?