Mageia forum

Since I upgraded to Mageia 6 I can't start VMware Workstation 12.5.
In MCC-System I can see that vmware is started. I can also see that vmware-USBArbitrator is started.
But vmware-workstation-server is stopped. When I try to start vmware-workstation-server nothing happens, vmware-workstation-server does not start.
I have tried to uninstall and reinstall VMware Workstaion but that doesn't help.
I'm running Mageia 6 with kernel 4.4.74-desktop-1. (None of later kernels will start Mageia in KDE Plasma, that's why I use 4.4.74).
I have a lots of guests installed and whish to use them.
Anyone that have time to help me solv my problem?
Regards// Jan

I use vmware ESXi , but see no point in vmware workstation.

vmware provides a tool, https://www.vmware.com/support/developer/ovf/

ovftool to export vmware images to an independent format.

virtualbox wich runs fine on mageia 6 will import these images, and run them.

virtualbox is free and gets updates from the mageia repos regularly.

and many more people are using it as a result of it being free.

worth trying one to see if it works.

by the way,, mageia 6 needs a 4.9 kernel, so I cant see why you are running a mageia 5 kernel with mageia 6.

that will also stop virtualbox that comes with mageia 6 running.

regards peter

If the problem depends on which kernel I use then I have to Mageia Buggzilla, https://bugs.mageia.org/show_bug.cgi?id=21483.
There I try to explain why I use kernel 4.4.74, kernel 4.9 will not start KDE Plasma and until now I haven't get any solution of that.

according to that the issue was solved due to a 16gig sd card being in the reader?

so im still confused.

also mageia 6 never came with that version of kernel.

"Then I get back to Mageia 6 kernel-desktop-4.4.74-1.mga5" its a 5 kernel

sounds like this is an upgrade that went wrong somewhere.

often after an upgrade mageia hangs onto the old kernel, Ive had that myself.

causes all sorts of issues with graphics drivers.

there are a few steps you can take to fix that, but they may be complex.

ie make sure the latest kernel is installed and boot from it in the boot menu.

then remove the mageia 5 kernel.

then select the right graphics card setup

then reboot.

or more drastic approach

would suggest that perhaps its time to backup everything carefully to an external USB harddisk and do a fresh install, from USB/CD

regards peter

I have not yet upgraded from Mageia 5. I have been frantically busy and have been afraid of having to debug any issues from the upgrade...I simply don't have the time.

I did just upgrade my laptop from OpenSUSE Leap 42.1 to OpenSUSE Leap 42.3 (and it went very badly, but that is not a story I need to get into here). At the same time, I upgraded VMware Workstation from 11 to 12.5. Workstation 12.5 would not start on the upgraded OpenSUSE installation until I patched it.

Most commonly, Workstation needs to be patched due to changes in the kernel that Workstation has not kept up with, and that probably is the situation you face.

Usually someone has already made a patch available. Occasionally, I have had to patch it myself - which I hate, because, once again, it takes a lot of time to sort out and do correctly.

This time, I was fortunate. There was already a patch.

Look here: http://www.hendrik-woltersdorf.de/linux ... index.html

The patch is listed for vmware player, but that is OK; it patches vmmon.ko and vmnet.ko and those are the same in both workstation and player. It also specifies OpenSUSE Leap 42.3 as the host, but again this should be irrelevant - it is kernel drivers getting patched and that should be appropriate for any kernel with the proper revision level.

So I would say give it a try.

I follow the instuctions but when trying to compile I get the following errormessage:

Code: Select all

[root@Humlan source]# vmware-modconfig --console --install-all
Failed to setup build environment.
[root@Humlan source]# exit
exit
[jan@Humlan source]$

Please place command-output between [CODE]-tags, to improve readability, thanks ahead!!!
Demo: ftp://ftp5.gwdg.de/pub/linux/mandriva/m ... e_tags.ogv

when you start vmware, it should tell you it needs to compile some things, then should try to compile. This is where you need the patched files, IF you need the patched files.

My OpenSUSE installation has kernel 4.4.85-22 in it.

So I am not sure what your situation is.

Try these commands, as root:

Code: Select all

lsmod | grep vmmon
lsmod | grep vmnet


This will tell if the vmmon and vmnet drivers are loaded in the kernel. If they are loaded then you do not need that patch.

If those modules are not loaded, then that explains why you can't get a VM to start. In that event, try these commands:

Code: Select all

insmod vmmon
insmod vmnet


If those don't work, try these:

Code: Select all

insmod vmmon.ko
insmod vmnet.ko


If the modules are not loaded and do not load, then you have some configuration issue. If they failed because they were not found, then you should try to manually compile them and install them in the kernel. If they failed with an error message, then you need the patch.

Hard to tell. Run those commands and report back, then we can proceed.

This is the result:

Code: Select all

[root@Humlan jan]# lsmod | grep vmmon
[root@Humlan jan]#
[root@Humlan jan]# lsmod | grep vmnet
[root@Humlan jan]#

[root@Humlan jan]# insmod vmmon
insmod: ERROR: could not load module vmmon: No such file or directory
[root@Humlan jan]# insmod vmnet
insmod: ERROR: could not load module vmnet: No such file or directory
[root@Humlan jan]#

[root@Humlan jan]# insmod vmmon.ko
insmod: ERROR: could not load module vmmon.ko: No such file or directory
[root@Humlan jan]# insmod vmnet.ko
insmod: ERROR: could not load module vmnet.ko: No such file or directory
[root@Humlan jan]#


So what to do?

2017-09-18
Today I tried to find why VMware Workstation refuse to start.

This is what i did:

Code: Select all

[root@Humlan jan]# systemctl start vmware-workstation-server.service
Job for vmware-workstation-server.service failed because the control process exited with error code.
See "systemctl status vmware-workstation-server.service" and "journalctl -xe" for details.
[root@Humlan jan]#


and

Code: Select all

[root@Humlan jan]# journalctl -xe
sep 18 15:56:17 Humlan.localdomain systemd[1]: Starting SYSV: This services starts and stops the Workstation as a Server daemon....
-- Subject: Unit vmware-workstation-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vmware-workstation-server.service has begun starting up.
sep 18 15:56:17 Humlan.localdomain vmware-workstation-server[14286]: [42B blob data]
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Control process exited, code=exited status=1
sep 18 15:56:17 Humlan.localdomain systemd[1]: Failed to start SYSV: This services starts and stops the Workstation as a Server daemon..
-- Subject: Unit vmware-workstation-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vmware-workstation-server.service has failed.
--
-- The result is failed.
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Unit entered failed state.
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Failed with result 'exit-code'.
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.801974,  0] ../source3/libsmb/nmblib.c:873(send_udp)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   Packet send failed to 192.168.122.255(137) ERRNO=Operationen inte tillåten
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.802061,  0] ../source3/nmbd/nmbd_packets.c:179(send_netbios_packet)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   send_netbios_packet: send_packet() to IP 192.168.122.255 port 137 failed
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.802094,  0] ../source3/nmbd/nmbd_namequery.c:245(query_name)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   query_name: Failed to send packet trying to query name MYGROUP<1d>
...skipping...
sep 18 15:56:17 Humlan.localdomain systemd[1]: Starting SYSV: This services starts and stops the Workstation as a Server daemon....
-- Subject: Unit vmware-workstation-server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vmware-workstation-server.service has begun starting up.
sep 18 15:56:17 Humlan.localdomain vmware-workstation-server[14286]: [42B blob data]
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Control process exited, code=exited status=1
sep 18 15:56:17 Humlan.localdomain systemd[1]: Failed to start SYSV: This services starts and stops the Workstation as a Server daemon..
-- Subject: Unit vmware-workstation-server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit vmware-workstation-server.service has failed.
--
-- The result is failed.
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Unit entered failed state.
sep 18 15:56:17 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Failed with result 'exit-code'.
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.801974,  0] ../source3/libsmb/nmblib.c:873(send_udp)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   Packet send failed to 192.168.122.255(137) ERRNO=Operationen inte tillåten
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.802061,  0] ../source3/nmbd/nmbd_packets.c:179(send_netbios_packet)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   send_netbios_packet: send_packet() to IP 192.168.122.255 port 137 failed
sep 18 15:56:26 Humlan.localdomain nmbd[11095]: [2017/09/18 15:56:26.802094,  0] ../source3/nmbd/nmbd_namequery.c:245(query_name)
sep 18 15:56:26 Humlan.localdomain nmbd[11095]:   query_name: Failed to send packet trying to query name MYGROUP<1d>


Anyone that understand the respons?

Today I installed Mageia 6 in an other PC (Zotac, 64-bit).
After installationen I downloaded the latest VMware Workstation (12.5.7) and installed it with success.
BUT, it refuse to start. It is the vmware-workstation-server that doesn't start when I try in MCC-Service.

I'm very confused!

It looks like you do not have the required kernel drivers available. These need to be compiled the first time you start vmware, and that is supposed to happen automatically.

You should have received an error message someplace when you tried to do this.

Do you have the gcc C compiler environment installed? IIRC this is not installed with a default installation of Mageia. Without it installed so those drivers can be compiled, you are dead in the water with vmware workstation.

You should find logs in /var/log/vmware. There will be information in those about your problem, though those logs are rather hard to read.

gcc (GNU Compiler Collection) 5.4.0 5.mga6 is installed.
gcc-cpp (The C Preprossesor) 5.4.0 5.mga6 is installed.

The installation succeded without any error messages shown on the screen.

You are right, the log is very difficult to read and understand for me. For me it looks like that some files is missing?
I have no knowleges to do anything to correct what maybe wrong, I can't understand the message.

I'm runing a ThinkPad W701 with i7 CPU and Nvidia Quadro FX2800M graphiccard.

Today I upgrade to VMware Workstation 14.0.
VMware Workstation started.
But when I try to start a guest I get the following error:

This host does not support
virtualizing real mode. The Intel
"VMX Unrestricted Guest" feature is
necessery to run this virtual machine
on an Intel Processor.
Module 'CPUIDEarly' power on failed.
Failed to start the virtual mashine.

I don't know what to do now!
Anyone that know now?

1) wait until vmware has lost enough customers to fix that stupid decision,
1a) downgrade to 12.5x until they fix 14, which is legal.
2) buy a new laptop, or
3) switch to Virtualbox, which is free and Libre if you don't use the extension pack.

There are also settings tweaks to allow it to work, but WS14 will run at ~glacial speed unless your processor supports the calls that provide the .1% speedup in a couple tasks they did this for.

Also note that for Mageia6, you must install sudo or vmware 12.5x or 14 will crash out when adding the registration#.
You don't have to configure sudo, just had to be there if installing as root..

Thanks for replay,
For now I have decided to avoid vmware and only use VirtualBox.
Tghanks// Jan

Dear Mageians who would like to use VMware,

I have managed to get VMware 12.5.9 running on Mageia 6 (with kernel 4.14.65-desktop-1.mga6 )
and I have documented how to install it here:

https://wiki.mageia.org/en/Installing_VMware_workstation_12.5.9_in_Mageia_6

Enjoy!


Kind Regards
Paul
[tree|code|news|wiki]gazer