Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: FC17, RHEL 6.3, Ubuntu 10.10, Linux Mint 12, Linux Mint 13
Posts: 11
Rep:
Help uninstalling VMware 9 on Fedora 17
I can not get VMwaer 9 to run properly, I keep getting an error stating im missing my kernel headers. I know my headers are installed as I installed them manually, but still no luck. I am at the point I just want to remove VMware from my machine, but I am running into an issue with that now. I keep getting an error saying the component did not register an installer....
Code:
[root@Fedora-HP8760 ~]# vmware-installer --list-productsProduct Name Product Version
==================== ====================
vmware-workstation 9.0.0.812388
[root@Fedora-HP8760 ~]# vmware-installer -u vmware-workstation 9.0.0.812388
Traceback (most recent call last):
File "/tmp/tmpudysv-.vmis.env", line 135, in <module>
raise ComponentError(u'Component did not register an installer', component)
NameError: name 'ComponentError' is not defined
[root@Fedora-HP8760 ~]#
I Googled this error, but was unable to find anything related to this situation. A search of the forums yielded no help. I found one post, but it has gone unanswered, and was for an older version of VMware.
I love VMware, but they just have too many issues with systems that are running the latest kernels so now I will just go back to VirtualBox.
Distribution: FC17, RHEL 6.3, Ubuntu 10.10, Linux Mint 12, Linux Mint 13
Posts: 11
Original Poster
Rep:
I probably should have listed how I installed it.
When I installed VMware I used a script called VMware-Workstation-Full-9.0.0-812388.x86_64.bundle.
I did try a yum remove, but no packages were found, so then I also tried a rpm -e vmware but still told nothing to do.
I probably should have listed how I installed it. When I installed VMware I used a script called VMware-Workstation-Full-9.0.0-812388.x86_64.bundle. I did try a yum remove, but no packages were found, so then I also tried a rpm -e vmware but still told nothing to do.
Package names are case sensitive so if it isn't called "VMware-Workstation" or "VMware-workstation" then you could try listing package names with 'rpm -qa|grep -i vmw'. Before you remove VMware, that is if you still want to give it a try, kernel headers errors aren't uncommon and once in a while a patch is released. See if this thread http://communities.vmware.com/message/2117818 gets you going. If unsure try the commands and post the output / errors.
Distribution: FC17, RHEL 6.3, Ubuntu 10.10, Linux Mint 12, Linux Mint 13
Posts: 11
Original Poster
Rep:
OK I followed your link to the kernel patch and no go (VMware would not even start). I then followed your rpm suggestion and still rpm can not find vmware.
Code:
[root@Fedora-HP8760 vmware9_kernel3.5_patch]# ./patch-modules_3.5.0.sh
patching file vmmon-only/linux/hostif.c
Stopping vmware (via systemctl): Error: No space left on device
[ OK ]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-ht018s/vmmon-only'
/bin/make -C /lib/modules/3.5.4-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
CC [M] /tmp/modconfig-ht018s/vmmon-only/linux/driverLog.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/linux/hostif.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/memtrack.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/linux/driver.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/apic.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/hashFunc.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/vmx86.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/cpuid.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/task.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/comport.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/common/phystrack.o
CC [M] /tmp/modconfig-ht018s/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/modconfig-ht018s/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ht018s/vmmon-only/vmmon.mod.o
LD [M] /tmp/modconfig-ht018s/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-ht018s/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-ht018s/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/modconfig-ht018s/vmmon-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-ht018s/vmnet-only'
/bin/make -C /lib/modules/3.5.4-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
CC [M] /tmp/modconfig-ht018s/vmnet-only/driver.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/hub.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/userif.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/netif.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/bridge.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/filter.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/procfs.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/smac_compat.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/smac.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/vnetEvent.o
CC [M] /tmp/modconfig-ht018s/vmnet-only/vnetUserListener.o
LD [M] /tmp/modconfig-ht018s/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ht018s/vmnet-only/vmnet.mod.o
LD [M] /tmp/modconfig-ht018s/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-ht018s/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-ht018s/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/modconfig-ht018s/vmnet-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-ht018s/vmblock-only'
/bin/make -C /lib/modules/3.5.4-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/filesystem.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/file.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/block.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/module.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/super.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/control.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/stubs.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/inode.o
CC [M] /tmp/modconfig-ht018s/vmblock-only/linux/dentry.o
LD [M] /tmp/modconfig-ht018s/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ht018s/vmblock-only/vmblock.mod.o
LD [M] /tmp/modconfig-ht018s/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-ht018s/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-ht018s/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/modconfig-ht018s/vmblock-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-ht018s/vmci-only'
/bin/make -C /lib/modules/3.5.4-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
CC [M] /tmp/modconfig-ht018s/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-ht018s/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-ht018s/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-ht018s/vmci-only/driverLog.o
LD [M] /tmp/modconfig-ht018s/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ht018s/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-ht018s/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-ht018s/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-ht018s/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-ht018s/vmci-only'
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-ht018s/vsock-only'
/bin/make -C /lib/modules/3.5.4-1.fc17.x86_64/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/util.o
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-ht018s/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-ht018s/vsock-only/driverLog.o
LD [M] /tmp/modconfig-ht018s/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ht018s/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-ht018s/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/3.5.4-1.fc17.x86_64'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-ht018s/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-ht018s/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-ht018s/vsock-only'
Starting vmware (via systemctl): Error: No space left on device
[ OK ]
All done, you can now run VMWare WorkStation.
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation9.0.0-2012-09-27-09:52:08-backup' directory
[root@Fedora-HP8760 vmware9_kernel3.5_patch]# vmware
[root@Fedora-HP8760 vmware9_kernel3.5_patch]# cd ..
[root@Fedora-HP8760 Vmware 9 for liux]# ./VMware-Workstation-Full-9.0.0-812388.x86_64.bundle
Extracting VMware Installer...done.
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -qa|grep -i vmw
xorg-x11-drv-vmware-12.0.2-1.fc17.x86_64
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -e xorg-x11-drv-vmware*
error: package xorg-x11-drv-vmware* is not installed
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -e xorg-x11-drv-vmware-12.0.2-1.fc.x86_64
error: package xorg-x11-drv-vmware-12.0.2-1.fc.x86_64 is not installed
[root@Fedora-HP8760 Vmware 9 for liux]#
* If unsure, first read the label on the tin. As in 'rpm -qi xorg-x11-drv-vmware' because I never told you to remove an Xorg driver.
* Be damn sure to read read ALL labels the tin shows. If there's a warning like
Quote:
Originally Posted by armans
Code:
Error: No space left on device
then you fix that warning before doing anything else. Clean up, try again.
* I don't know how it works with VMware Workstation but with VMware Server I often had to run vmware-config.pl and re-initialize the configuration before I could use it again.
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -qa|grep -i vmw
xorg-x11-drv-vmware-12.0.2-1.fc17.x86_64
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -e xorg-x11-drv-vmware*
error: package xorg-x11-drv-vmware* is not installed
[root@Fedora-HP8760 Vmware 9 for liux]# rpm -e xorg-x11-drv-vmware-12.0.2-1.fc.x86_64
error: package xorg-x11-drv-vmware-12.0.2-1.fc.x86_64 is not installed
[root@Fedora-HP8760 Vmware 9 for liux]#
and the only reason you failed to remove it was because you didn't type the package name right. Not that it's a crucial driver but next time you try something like that run 'yum remove [packagename]' (or at least 'rpm --test -e [packagename]') so you get a chance to review changes. As in "act before you think" ;-p
Quote:
Originally Posted by armans
I will try your other suggestion regarding the vmware-config.pl and post me results after that time.
It would be best if you clean up /tmp and ensure there's enough free disk space for the process to properly build and install the modules and then see if you need to run vmware-config.pl. I don't know how it works with VMware Workstation but the VMware Server daemon process dumps its own logs in /var/log and checking log files often helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
