Build environment error a required application is missing and modconfig can not continue

Now that you mention it, there was a time many years ago when a Windows update broke VirtualBox for me.  Ever since I switched to Linux (Ubuntu) I have kept the previous kernel around.  In any case, I will be watching the kernel updates like a hawk…

So, for now I guess I will be watching for a successful install of Workstation on Ubuntu 20.04 with the current kernel (5.13.0.27-generic).  In the meantime, I have a few more questions for the experts (you) in here:

First, I have searched the VMWare KB for instructions on the uninstall of Workstation from Ubuntu.  The results are split into two camps (even in the same article).  Either I execute the bundle file again (presumably it sees the current install and gives the option of uninstalling it), or I do it from the command line.  Which is it?  I am thinking that it is six of one vs half-dozen of the other, but I want to be sure:

https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-D739F0D1-26FB-4A…

“On a Linux host, you uninstall Workstation Pro by running the bundle installer.”

vs

“In a terminal window, type ‘vmware-installer -u vmware-workstation’”

Second, coming from Windows-land, I never liked installing and uninstalling stuff over and over, because each time artifacts are left behind, either orphaned files, or registry entries no longer used.  Do it enough, and the registry becomes so messed up that a reinstall would become necessary.  I know (?) that there is no registry per se in Linux, so does either of these methods do a completely clean uninstall (i.e. leaving my OS as if Workstation had never been installed in the first place; no left over files, no nothing.)?  Are there command-line options to clean house?

Thanks everyone for your help and patience!

VMWare

Namespaces

Page actions

VMware allows you to run one or more virtual machines at the same time on one computer. VMware player is (as of 2013-10-21) free for non-commercial use.

Contents

Using VMware Player

• Download VMware Player. You get an installation file, in this example we call it VMware-Player-4.0.0-471780.x86_64.bundle.
• install some dependencies, e.g. for SUSE Linux open a console and enter:

• install VMware Player:

To run vmware player, enter

removing VMware Player

Where component can be

Installing VMWare ESX server

After installing VMWare ESX server, set in /etc/ssh/sshd_config

The vmware files

• .vmdk files hold virtual disks
• .vmx files describe a virtual machine (where to find the virtual disks etc.) in vmware’s own format. It can be opened e.g. with vmware player.
• .ovf files describe a virtual machine in a standardized format. The virtual machines can be imported e.g. with vmware player.
• .ova files describe a virtual machine in a standardized format. The virtual machines can be imported e.g. with vmware player.

Moving virtual machines

I ran out of disk space and moved my virtual machines from the SSD disk /root/vmware to another disk /mnt/vmware:

Then I put a link from /root/vmware to /mnt/vmware:

Then the virtual machines showed up twice in the inventory. I had to delete /root/.vmware to get rid of this.

TroubleShooting

mouse-keyboard-screen control

Symptom: When you start vmplayer you get a pop-up saying «Failed to initialize mouse-keyboard-screen control»

Reason You have probably tried to start your virtual machine in an nx session Solution Better use a vnc session.

Источник

How to fix VMware Modconfig can not continue

Recently, I installed a VMware workstation on a fresh Debian installation. After that, when I ran the VMware workstation to create a new virtual machine, I got the error message: Build environment error! A required application is missing, and Modconfig can not continue. XZ Check the log for more details.

This error was new to me. Before that error, I resolved the missing Linux header error for VMware Workstation, and we will find a solution for that as well.

As you know, there are a small number of packages that are available by default for use in the minimal version of Debian or any other distribution.

And the above error is caused by missing gcc and make utilities that are responsible for compiling code from source.

In Debian or Ubuntu, there is a bundle package that includes all the necessary files for development purposes. You can directly install the build-essentials package to fulfill error requirements by pasting the below command:

Or else you can install a single package by typing the below code:

Once the installation is completed, you need to relaunch the VMware workstation and you will find the error no longer exists on your system.

A man with a tech effusive who has explored some of the amazing technology stuff and is exploring more. While moving towards, I had a chance to work on Android development, Linux, AWS, and DevOps with several open-source tools.

Источник

Vmware player build environment error

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am finally upgrading my OS from Ubuntu 16.04 to 20.04, and with it Workstation 16.2.1 (coming from 12.5.7). The bundle installed with no complaints, but when I tried to run it, it crashed. The first message was that it could not find a compatible gcc compiler (version 9.3). I installed it (sudo apt install gcc) and verified the version to be 9.3 (gcc —version). Now, it gives the message «Before you can run VMWare, several modules must be compiled and loaded into the running kernel,» followed by «Build environment error! A required application is missing and Modconfig cannot continue. xzCheck the log for more details.» Am I to conclude that there are other third party packages I need to install (and what are they)? I am by no means a linux guru (I am lucky to navigate to the right place from the command line), but I have been using Ubuntu with Windows OSs in VMs for years. All of my searches suggest this is a known problem with Workstation 16, so do I need to downgrade? Please help.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am not a Linux/Ubuntu expert, not by any stretch, wouldn’t consider myself a «power user».

Yesterday, I did an in-place upgrade of one physical machine from Ubuntu 18.04 to Ubuntu 20.04. But I don’t think it upgraded the kernel. It stayed at 5.4.0.96-generic. Just for comparison, an Ubuntu 20.04 VM I have the kernel is on 5.13.0.27-generic. Workstation 16.2.1 did not have problems building vmmon/vmnet with the 5.4.0.96-generic kernel though and I also didn’t have to install packages manually.

So check the kernel version as well with uname -r and have a visit on this

Or a kernel upgrade might be necessary if the kernel version is too old for version 16.2.1.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am currently at version 5.13.0.27-generic as well. Thank you for the github link you provided. I wonder if the package installed and compiled correctly under an older kernel, and «flew under the radar» when you upgraded. With the older Workstation (12.5.7) every time I upgraded the kernel, it had to recompile. Actually, that is what kept me from upgrading from 12.5.7: The fine folks at Ubuntu broke Workstation (the networking part, IIRC) with their kernel tweaks several years ago (and didn’t bother to fix it, even though 16.04 was still supported. supposedly), and I was not in a position to upgrade beyond 12.5 at that point. If that is indeed the case here as well, I can only hope that VMWare fixes the problem soon.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I have been using an Ubuntu 18.04 host with Workstation Pro 15.x since late 2018. The Linux kernel updates will always require a rebuild of vmmon/vmnet. Here is a good explanation why

So the github updates provided by mkubecek is quite helpful. He is essentially updating it for newer kernel versions whereas VMware may not be doing it until some major release or updates to Workstation for official support of some Linux kernel version. Occasionally, you would see him reply on some threads in this forum.

If you have secure boot enabled on the host machine you have to sign the vmmon/vmnet modules and enroll MOK for every vmmon/vmnet rebuild.
https://kb.vmware.com/s/article/2146460

I don’t know why the upgrade of 18.04 host to 20.04 didn’t upgrade the kernel. That was meant to be a trial (using a machine that I hardly use) as opposed to the actual machine that I use daily. I can only guess perhaps because only a small amount of space left (less than 10% free in percentage terms and around 21GiB free in absolute terms) on that test machine. I am taking baby steps with this upgrade to Ubuntu 20.04 and Workstation 16.x. Unsure if 16.2.1 would be a good idea as it seems quite problematic judging by the threads being posted here or might start off with 16.1.2 or have that as plan B.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Well, shazzbot. As I said, I have been using Workstation for several years (most of what I do is in Windows VM environments), but it seems crazy that every kernel upgrade is a crap-shoot as to whether Workstation will work (and potentially require third-party patching). For the time being, I have established a temporary VM environment using VirtualBox, but I hope to move back up to Workstation. Are the engineers at VMWare working on this for the next major release?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Virtualbox has the same issues with new kernels; I moved away from it after too many times the VB drivers would not build. I would recommend keeping an LTS kernel around just in case.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

> but it seems crazy that every kernel upgrade is a crap-shoot as to whether Workstation will work (and potentially require third-party patching).

Get used to it — it has always been like that unless you used RedHat.
Before you upgrade your kernel always do your research in the forum.
For the mainstream distributions patching instructions are usually available within a couple of weeks.

My experience — be careful when you run Ubuntu as the host — dont expect that changing Workstation version is a task that can be done over the weekend .. 😕
Ulli

________________________________________________
Do you need support with a VMFS recovery problem ? — send a message via skype «sanbarrow»
I do not support Workstation 16 at this time .

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Now that you mention it, there was a time many years ago when a Windows update broke VirtualBox for me. Ever since I switched to Linux (Ubuntu) I have kept the previous kernel around. In any case, I will be watching the kernel updates like a hawk…

So, for now I guess I will be watching for a successful install of Workstation on Ubuntu 20.04 with the current kernel (5.13.0.27-generic). In the meantime, I have a few more questions for the experts (you) in here:

First, I have searched the VMWare KB for instructions on the uninstall of Workstation from Ubuntu. The results are split into two camps (even in the same article). Either I execute the bundle file again (presumably it sees the current install and gives the option of uninstalling it), or I do it from the command line. Which is it? I am thinking that it is six of one vs half-dozen of the other, but I want to be sure:

“ On a Linux host, you uninstall Workstation Pro by running the bundle installer. ”

“ In a terminal window, type ‘vmware-installer -u vmware-workstation’ ”

Second, coming from Windows-land, I never liked installing and uninstalling stuff over and over, because each time artifacts are left behind, either orphaned files, or registry entries no longer used. Do it enough, and the registry becomes so messed up that a reinstall would become necessary. I know (?) that there is no registry per se in Linux, so does either of these methods do a completely clean uninstall (i.e. leaving my OS as if Workstation had never been installed in the first place; no left over files, no nothing.)? Are there command-line options to clean house?

Thanks everyone for your help and patience!

Источник

VMware Player отказывается запускаться 16.04 (модули VMware не могут скомпилироваться в ядро)

Я давно использую VMware Player 14.04. Я обновил до 16.04 около 3 месяцев назад. Теперь я пытаюсь запустить VMware Player впервые после обновления, и он отказывается запускаться! Я дважды щелкаю по ярлыку на панели запуска, затем программа пытается запустить как обычно, появляясь на нижней панели задач с сообщением «Запуск VMware Player», и через несколько секунд она просто исчезает без ошибок!

Я попробовал следующее без изменений:

Я переустановил чуть более новую версию. С версии 6 до 7 (VMware-Player-7.1.2-2780323.x86_64.bundle)

Я обнаружил эту ошибку vmware после обновления до ubuntu 16.04 и отключил безопасную загрузку в BIOS.

Я читал этот пост VMware не будет работать в Ubuntu 16.04 LTS (даже без ошибок), и люди говорят, что VMware Player отстой. Но я использую его около 5 лет в Ubuntu и никогда не сталкивался с проблемой до сих пор.

Конечно, я запустил обновление на всякий случай.

Вся информация выше — исходная проблема — я запускаю VMplayer, и он не запускается без сообщения об ошибке или каких-либо диалоговых окон. Все, что ниже, является текущей проблемой, где у меня есть куча ошибок при компиляции модулей и загрузке их в ядро ​​после попытки некоторых команд терминала

Я обнаружил этот пост VMware не будет работать после обновления Ubuntu. Я побежал export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libglibmm-2.4.so.1/:$LD_LIBRARY_PATH и это выглядело так, как будто собирался начать. меня попросили обновить ядро, я ввел пароль

и процесс завершается с этим сообщением:

используя комментарии в vmware player на ubuntu 15.10 я запустил echo /usr/lib/vmware/lib/libglibmm-2.4.so.1 | sudo tee -a /etc/ld.so.conf.d/LD_LIBRARY_PATH.conf а также sudo ldconfig , Также я побежал sudo apt-get install libcanberra-gtk*

после попытки всех этих команд, когда я печатаю vmplayer в терминале у меня спрашивают пароль для компиляции ядра, и как только этот процесс запускается, происходит сбой. Изображение ниже дает вам суть того, что я вижу.

Содержимое терминала после vmplayer можно найти здесь: https://paste.ubuntu.com/24246599/

Содержимое журнала ошибок можно найти здесь: https://paste.ubuntu.com/24246694/

Мои вопросы высокого уровня: как мне заставить VMware Player версии 6 или 7 работать с 16.04?

Я уверен, что важно упомянуть, что пост во втором упорядоченном списке выше предлагал запустить sudo modprobe vmnet , Я не уверен, какую информацию предоставляет эта команда, но вот она: modprobe: FATAL: Module vmnet not found in directory /lib/modules/4.4.0-66-generic

Любые предложения или советы очень ценятся!

Источник

VMWare

Namespaces

Page actions

VMware allows you to run one or more virtual machines at the same time on one computer. VMware player is (as of 2013-10-21) free for non-commercial use.

Contents

Using VMware Player

• Download VMware Player. You get an installation file, in this example we call it VMware-Player-4.0.0-471780.x86_64.bundle.
• install some dependencies, e.g. for SUSE Linux open a console and enter:

• install VMware Player:

To run vmware player, enter

removing VMware Player

Where component can be

Installing VMWare ESX server

After installing VMWare ESX server, set in /etc/ssh/sshd_config

The vmware files

• .vmdk files hold virtual disks
• .vmx files describe a virtual machine (where to find the virtual disks etc.) in vmware’s own format. It can be opened e.g. with vmware player.
• .ovf files describe a virtual machine in a standardized format. The virtual machines can be imported e.g. with vmware player.
• .ova files describe a virtual machine in a standardized format. The virtual machines can be imported e.g. with vmware player.

Moving virtual machines

I ran out of disk space and moved my virtual machines from the SSD disk /root/vmware to another disk /mnt/vmware:

Then I put a link from /root/vmware to /mnt/vmware:

Then the virtual machines showed up twice in the inventory. I had to delete /root/.vmware to get rid of this.

TroubleShooting

mouse-keyboard-screen control

Symptom: When you start vmplayer you get a pop-up saying «Failed to initialize mouse-keyboard-screen control»

Reason You have probably tried to start your virtual machine in an nx session Solution Better use a vnc session.

Источник

VMware

Contents

ovftool

To make an OVA file from a VMware virtual machine, use the following command:

Troubleshooting

Log files are located in:

Issues

VMware complaining gcc4 9.3 was not found

I’m using Debian testing (stretch/sid). When I recently reinstalled VMware Workstation, I had an error message that said gcc-4.9.3 was not found:

If you list gcc installations available in /usr/bin/ , you will notice that gcc-4.9 exists but the default gcc command is a symbolic link to gcc-5 :

All you need to do is to temporarily change the pointer to gcc-4.9 :

Then proceed with the VMware installation and recreate the symbolic link to make it point to gcc-5 :

Failed to load module «atk-bridge»

If you have the following error:

To make the change permanent, the best is to add the above line to /usr/bin/vmware-installer .

libvmwareui.so: undefined symbol

Here is how you can fix it:

To make this permanent, add the above line to /usr/bin/vmware .

You should also apply this change to /usr/bin/vmware-netcfg , the network configuration panel.

«Failed to build vmnet. Failed to execute the build command.»

Issue affecting following environments:

• kernel 4.6.0-1 on Debian Stretch
• kernel 4.6.1-2 on Archlinux

Symptoms: compilation fails:

When manually trying to compile, we notice that this is due to the get_user_pages function:

It fails to compile because there has been a change in the get_user_pages function. To fix that, do as follows (scripted from this post):

Fedora specific installation procedure

Compilation issue VMWare 12.5.2 with Kernel 4.9.5

build environment error! a required application is missing and modconfig can not continue. xzcheck the log for more details

If you have the following error message on Fedora:

Install the following dependencies:

Can’t open OVA

If you are not able to open OVA files (nothing happens), check the errors reported by ovftool:

stddef.h and stdarg.h files not found while compiling VMware Workstation 16.2.1 with Kernel 5.16.0-1

If you have compilation issues claiming that stddef.h and stdarg.h are not found, try this:

Compilation error with VMware Workstation 16.2.3 and kernel 5.18.0-2

If you have the following compilation error with kernel 5.18.0.2 and VMware Workstation 16.2.3:

You can fix as follows:

Compilation error with VMware Workstation 16.2.4 and kernel 5.19.0-1

If you have compilation errors while trying to build VMWare Workstation 16.2.4 and kernel 5.19.0-1, like the one below:

Источник

How to fix VMware Modconfig can not continue

Recently, I installed a VMware workstation on a fresh Debian installation. After that, when I ran the VMware workstation to create a new virtual machine, I got the error message: Build environment error! A required application is missing, and Modconfig can not continue. XZ Check the log for more details.

This error was new to me. Before that error, I resolved the missing Linux header error for VMware Workstation, and we will find a solution for that as well.

As you know, there are a small number of packages that are available by default for use in the minimal version of Debian or any other distribution.

And the above error is caused by missing gcc and make utilities that are responsible for compiling code from source.

In Debian or Ubuntu, there is a bundle package that includes all the necessary files for development purposes. You can directly install the build-essentials package to fulfill error requirements by pasting the below command:

Or else you can install a single package by typing the below code:

Once the installation is completed, you need to relaunch the VMware workstation and you will find the error no longer exists on your system.

A man with a tech effusive who has explored some of the amazing technology stuff and is exploring more. While moving towards, I had a chance to work on Android development, Linux, AWS, and DevOps with several open-source tools.

Источник

Vmware build environment error

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am finally upgrading my OS from Ubuntu 16.04 to 20.04, and with it Workstation 16.2.1 (coming from 12.5.7). The bundle installed with no complaints, but when I tried to run it, it crashed. The first message was that it could not find a compatible gcc compiler (version 9.3). I installed it (sudo apt install gcc) and verified the version to be 9.3 (gcc —version). Now, it gives the message «Before you can run VMWare, several modules must be compiled and loaded into the running kernel,» followed by «Build environment error! A required application is missing and Modconfig cannot continue. xzCheck the log for more details.» Am I to conclude that there are other third party packages I need to install (and what are they)? I am by no means a linux guru (I am lucky to navigate to the right place from the command line), but I have been using Ubuntu with Windows OSs in VMs for years. All of my searches suggest this is a known problem with Workstation 16, so do I need to downgrade? Please help.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am not a Linux/Ubuntu expert, not by any stretch, wouldn’t consider myself a «power user».

Yesterday, I did an in-place upgrade of one physical machine from Ubuntu 18.04 to Ubuntu 20.04. But I don’t think it upgraded the kernel. It stayed at 5.4.0.96-generic. Just for comparison, an Ubuntu 20.04 VM I have the kernel is on 5.13.0.27-generic. Workstation 16.2.1 did not have problems building vmmon/vmnet with the 5.4.0.96-generic kernel though and I also didn’t have to install packages manually.

So check the kernel version as well with uname -r and have a visit on this

Or a kernel upgrade might be necessary if the kernel version is too old for version 16.2.1.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am currently at version 5.13.0.27-generic as well. Thank you for the github link you provided. I wonder if the package installed and compiled correctly under an older kernel, and «flew under the radar» when you upgraded. With the older Workstation (12.5.7) every time I upgraded the kernel, it had to recompile. Actually, that is what kept me from upgrading from 12.5.7: The fine folks at Ubuntu broke Workstation (the networking part, IIRC) with their kernel tweaks several years ago (and didn’t bother to fix it, even though 16.04 was still supported. supposedly), and I was not in a position to upgrade beyond 12.5 at that point. If that is indeed the case here as well, I can only hope that VMWare fixes the problem soon.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I have been using an Ubuntu 18.04 host with Workstation Pro 15.x since late 2018. The Linux kernel updates will always require a rebuild of vmmon/vmnet. Here is a good explanation why

So the github updates provided by mkubecek is quite helpful. He is essentially updating it for newer kernel versions whereas VMware may not be doing it until some major release or updates to Workstation for official support of some Linux kernel version. Occasionally, you would see him reply on some threads in this forum.

If you have secure boot enabled on the host machine you have to sign the vmmon/vmnet modules and enroll MOK for every vmmon/vmnet rebuild.
https://kb.vmware.com/s/article/2146460

I don’t know why the upgrade of 18.04 host to 20.04 didn’t upgrade the kernel. That was meant to be a trial (using a machine that I hardly use) as opposed to the actual machine that I use daily. I can only guess perhaps because only a small amount of space left (less than 10% free in percentage terms and around 21GiB free in absolute terms) on that test machine. I am taking baby steps with this upgrade to Ubuntu 20.04 and Workstation 16.x. Unsure if 16.2.1 would be a good idea as it seems quite problematic judging by the threads being posted here or might start off with 16.1.2 or have that as plan B.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Well, shazzbot. As I said, I have been using Workstation for several years (most of what I do is in Windows VM environments), but it seems crazy that every kernel upgrade is a crap-shoot as to whether Workstation will work (and potentially require third-party patching). For the time being, I have established a temporary VM environment using VirtualBox, but I hope to move back up to Workstation. Are the engineers at VMWare working on this for the next major release?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Virtualbox has the same issues with new kernels; I moved away from it after too many times the VB drivers would not build. I would recommend keeping an LTS kernel around just in case.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

> but it seems crazy that every kernel upgrade is a crap-shoot as to whether Workstation will work (and potentially require third-party patching).

Get used to it — it has always been like that unless you used RedHat.
Before you upgrade your kernel always do your research in the forum.
For the mainstream distributions patching instructions are usually available within a couple of weeks.

My experience — be careful when you run Ubuntu as the host — dont expect that changing Workstation version is a task that can be done over the weekend ..
Ulli

________________________________________________
Do you need support with a VMFS recovery problem ? — send a message via skype «sanbarrow»
I do not support Workstation 16 at this time .

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Now that you mention it, there was a time many years ago when a Windows update broke VirtualBox for me. Ever since I switched to Linux (Ubuntu) I have kept the previous kernel around. In any case, I will be watching the kernel updates like a hawk…

So, for now I guess I will be watching for a successful install of Workstation on Ubuntu 20.04 with the current kernel (5.13.0.27-generic). In the meantime, I have a few more questions for the experts (you) in here:

First, I have searched the VMWare KB for instructions on the uninstall of Workstation from Ubuntu. The results are split into two camps (even in the same article). Either I execute the bundle file again (presumably it sees the current install and gives the option of uninstalling it), or I do it from the command line. Which is it? I am thinking that it is six of one vs half-dozen of the other, but I want to be sure:

“ On a Linux host, you uninstall Workstation Pro by running the bundle installer. ”

“ In a terminal window, type ‘vmware-installer -u vmware-workstation’ ”

Second, coming from Windows-land, I never liked installing and uninstalling stuff over and over, because each time artifacts are left behind, either orphaned files, or registry entries no longer used. Do it enough, and the registry becomes so messed up that a reinstall would become necessary. I know (?) that there is no registry per se in Linux, so does either of these methods do a completely clean uninstall (i.e. leaving my OS as if Workstation had never been installed in the first place; no left over files, no nothing.)? Are there command-line options to clean house?

Thanks everyone for your help and patience!

Источник

From Linuxintro

yast -i kernel-source make gcc

sh VMware-Player-4.0.0-471780.x86_64.bundle

vmplayer

vmware-installer --gtk --uninstall-component component

 vmware-installer
 vmware-player-setup
 vmware-vmx
 vmware-network-editor
 vmware-usbarbitrator
 vmware-player-app
 vmware-ovftool
 vmware-player

PermitRootLogin yes

mkdir /mnt/vmware
mv /root/vmware/* /mnt/vmware

ln -s /mnt/vmware /root

# uname -a 
Linux tweedleburg 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qv kernel-desktop
kernel-desktop-2.6.37.1-1.2.2.x86_64
# rpm -qv kernel-source
kernel-source-2.6.37.1-1.2.2.noarch

A compatible version of gcc was not found.

yast -i gcc

Build environment error! A required application is missing and Modconfig can not continue. xzCheck the log for more details.

yast -i make