****tl;dr:** VMWare WS is oddly resilient to rm -rf. Help?**
OS: Linux Mint 14
The problem:
- VMWare WS 9 reports that an ACE VM is running
- An instance of VMWare VMX is running, somewhere.
- The UI for VMWare WS 9 isn't even open
Suggested VMWare W 9 deinstall procedure:
- Stop
vmware
service - Check if
vmware
service has stopped - All guidelines assume that the
vmware
service has stopped.
1) Stop the service:
/etc/init.d/vmware stop
Stopping VMware services:
VMware Authentication Daemon done
At least one instance of VMware VMX is still running.
Please stop all running instances of VMware VMX first.
VMware Authentication Daemon done
1.1) Well, that didn't work. I'll try to stop another service.
/etc/init.d/vmware-workstation-server stop
Stopping Workstation Server: done
2) Did it work? (no).
lsmod | grep vm
vmnet 55800 13
vmci 87583 1 vsock
vmmon 76095 1
kvm_intel 132759 0
kvm 414070 1 kvm_intel
The kernel modules for vmmon, and vmnet are still active (bad).
Maybe I can just use the uninstaller?
/usr/bin/vmware-installer -u vmware-workstation
The VMWare Installer could not shut down all running virtual machines. If you have ACE VMs open, please shut them down or suspend them now and press 'Retry' to continue.
As far as I know, I do not have any VMs open. VMWare Workstation 9 isn't even open. Maybe the purported ACE VM is a manifestation of the vmware daemon that I can't kill.
killall vmware && killall vmware-vmx
{vmware, vmware-vmx} no process found
/var/run:
acpid.pid motd sshd.pid
acpid.socket mount udev
atd.pid mysqld udisks2
avahi-daemon network user
console NetworkManager.pid utmp
ConsoleKit nm-dhclient-wlan0.conf vmblock-fuse
console-kit-daemon.pid nm-dns-dnsmasq.conf vmnat.4087
crond.pid plymouth vmnet-bridge-0.pid
crond.reboot pm-utils vmnet-dhcpd-vmnet1.pid
cups pppconfig vmnet-dhcpd-vmnet8.pid
dbus resolvconf vmnet-natd-8.pid
initramfs rsyslogd.pid vmnet-netifup-vmnet1.pid
libvirt samba vmnet-netifup-vmnet8.pid
libvirtd.pid sdp vmware
lock sendsigs.omit.d wpa_supplicant
mdm.pid shm
mdm_socket sshd
Maybe vmblock-fuse contains something interesting?
vmblock-fuse
├── blockdir
└── dev
1 directory, 1 file
less /var/run/vmblock-fuse/dev
I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am VMBLOCK-FUSE^@I am
This is getting silly
Any suggestions?
killall vmware-vmx
? Or check /var/run for any vmware PIDs andkill -9
them.