Bug 21259

Thanks for your report.

How did you upgrade? Using a classical iso?

* If so, please attach

   /root/drakx/report.bug 

from that install which has the time stamp of the upgrade, after compressing with xz 



* If you started the upgrade by clicking on the mgaapplet upgrade notification, then please find the path to where the journalctl logs are stored, that is on the / partition of your install, in /var/log/journal/<some very long hexadecimal string>/

and run, as root (assuming you installed yesterday, _change_ the dates if that was Saturday or today):

 journalctl -D /path/to/logs/ --since=2017-07-16 --until=2017-07-17 > journal.txt

compress with xz and attach journal.txt.xzq

Assignee: bugsquad => mageiatools
CC: (none) => marja11
Keywords: (none) => NEEDINFO

minus the q at the end

Created attachment 9502 [details]
Asked file /root/drakx/report.bug

First i tried to use mgaapplet but doesn't successed.
Then I burned a DVD and done a classical upgrade.

(In reply to Jan Pihlgren from comment #3)
> Created attachment 9502 [details]
> Asked file /root/drakx/report.bug

I discover that I sent wrong file. I will send the wright file now.

Created attachment 9503 [details]
The correct file asked

report.bug.Z created july 17 2017 13:32

I have found a vmware log: vmware-usbarb-15130.log
I attache the file.

Created attachment 9530 [details]
Vmware logfile

I uninstall Vmware Workstation 12.5 and then installed it again.
Result: Still unable to start VMware Workstation.

Created attachment 9565 [details]
After trying to start vmware with systemctl

Trying to start vmware with command systemctl start vmware.service
Then run systemctl status vmware.service
Nothing happends, no vmware appears.

Created attachment 9601 [details]
Errormessage when try start vmware-workstation-server

I tried to use MCC - System to start vmware-workstation-server.
The attachment shows the result

thierry, thomas, do you have any ideas about this ?

CC: (none) => mageia, thierry.vignaud, tmb

Still can't start vmware-workstation-server after update systemd

[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]# systemctl status vmware-workstation-server.service
● vmware-workstation-server.service - SYSV: This services starts and stops the Workstation as a Server daemon.
   Loaded: loaded (/etc/rc.d/init.d/vmware-workstation-server; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since tis 2017-08-22 06:13:52 CEST; 41s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 11807 ExecStart=/etc/rc.d/init.d/vmware-workstation-server start (code=exited, status=1/FAILURE)

aug 22 06:13:51 Humlan.localdomain systemd[1]: Starting SYSV: This services starts and stops the Workstation as a Serve
aug 22 06:13:52 Humlan.localdomain vmware-workstation-server[11807]: [42B blob data]
aug 22 06:13:52 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Control process exited, code=exited s
aug 22 06:13:52 Humlan.localdomain systemd[1]: Failed to start SYSV: This services starts and stops the Workstation as 
aug 22 06:13:52 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Unit entered failed state.
aug 22 06:13:52 Humlan.localdomain systemd[1]: vmware-workstation-server.service: Failed with result 'exit-code'.

So you need to figure out why it fails...

As vmware apparently has not really made it systemd aware (they only wrapped a a call their old init.d script in a systemd service file) then systemd cant really do much...

try to run  "/etc/rc.d/init.d/vmware-workstation-server start" directly to see if it produces any more info when it fails (also check logs if there is any vmware specific logging there)

If that does not help, check if there is any debug options in /etc/rc.d/init.d/vmware-workstation-server or what it's actually trying to do in order to figure out where it breaks down

Created attachment 9622 [details]
Info about start-error for vmware

Mybee this can help understan why vmware does not start.
Myself have not enaough knowledges to understand the information.

After much researching I found a workaround to enable VMware Workstation 12 to run on Mageia 6.

I documented how to install and apply the workaround here:
https://wiki.mageia.org/en/Installing_VMware_workstation_12_in_Mageia_6

It seems to be working OK for me. Please can someone else test and confirm if OK?

CC: (none) => paul.blackburn

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD

An up-to-date page for running VMware workstation 12.5.9 on Mageia 7 is:
https://wiki.mageia.org/en/Installing_VMware_workstation_12.5.9_in_Mageia_7

I am working on updating this method for Mageia 8.
I can confirm VMware workstation 12.5.9 runs on the latest beta release of Mga8.

Reminder: VMware is commercial virtual machine software.
It is not ported to Mageia. It is available for a free 30 day trial use.

I only have a license for VMware workstation 12 (to test and verify).
It is very likely that the method described in our wiki page will also work for more recent releases of VMware.

Kind regards
Paul