These instructions worked as well for me with VMWare Player 12.5.9 after
upgrading to Ubuntu 18.04.5 LTS Desktop with Linux kernel 4.15, thanks!
However, I'm now prepping for further upgrade to the latest Ubuntu 21.04
(kernel 5.11), and there seems to be more problems! The distro's shared
I don't have anything useful to contribute to this bug, but I still wanted to
thank iLugo for comment #26
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/comments/26
This was the solution that got VMWare Player 12.5.9 working properly on
my Intel Core 2 Duo machine and older version
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
Running Ubuntu 18.04.1 LTS with Workstation 12.5.9 installed.
Encountered the dreaded error:
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
Following @iLugo directions exactly, VMware
Many thanks, iLugo!
I followed your instructions from 2018-07-09 and wmplayer 12.5.9 worked at
once! I run ubuntu 18.04.
Before that it wouldn't start with this error: Relink `/lib/x86_64
-linux-gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for
IFUNC symbol `clock_gettime'.
Great
Really the update is very usefull...Awsome!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
It works with VMware 14.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
@Michael Harmon, you are very welcome.
I can confirm that my above procedure also works for Workstation Pro 14.1.2.
>> Updated instructions to successfully install Workstation Pro 14.1.2
in (K)ubuntu 18.04
1. Do the normal installation of VMWare Workstation. Do not run vmware
yet. It will fail
Thank you iLugo, your workaround instructions work for me with 18.04 and
VMPlayer 12.5.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications
A small correction to the step 2 above:
In the example, after you do the 'git clone ...' command, you have to change
directory to the git repo dir (e.g. 'cd vmware-host-modules') before issuing
the 'git checkout workstation-x.y.z'. Else, you'd get a git error like this:
'fatal: not a git
To successfully install VMware Workstation 12.5.9 (and probably 14.x also) in
Ubuntu 18.04, follow this procedure:
1. Do the normal installation of VMWare Workstation. Do not run vmware yet. It
will fail anyway.
2. Do a git clone (or download as zip package) of the vmware-host-modules
project
the only thing needed for the bug referenced here, is the line (already
commented on the Patrick's fix):
ln -s /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/vmware/lib/libz.so.1/libz.so.1
The other stuff in the fix relates to patch the modules, but has nothing
to do with the problem of this thread,
Yes +1 on patrick, qorks for me, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
+1 on Patrick's fix. Thanks for the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
I confirm that the recipe listed by Patrick (thanks!) works.
Some additional notes:
It is necessary to re-run `sudo vmware-networks --start` if you reboot
the host machine.
I used the code in https://github.com/mkubecek/vmware-host-modules.git
for vmnet/vmmon (checkout the branch
Oscar: I only have player 14. But maybe you can test this:
##
As root in /usr/lib/vmware/modules/source:
Extract vmmon.tar and vmnet.tar
wget -O ./vmmon-only/linux/hostif.c
https://raw.githubusercontent.com/mkubecek/vmware-host-
modules/b50848c985f1a6c0a341187346d77f0119d0a835/vmmon-
Upgrading to vmware workstation 14 is inconvenient because:
1. You have to pay for the upgrade.
2. Version 14 only works on "modern" cpus. It rejects my cpu, which
otherwise ran 12.5.7 fine until I upgraded to ubuntu 17.10.
--
You received this bug notification because you are a member of
with vmware-player 14.0.0 it works for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
Patrick: are you sure you fixed the bug described on this report? The
commit you mention is for fixing a problem with memory handling, which
is a different issue altogether. This bug is about VMware WS 12.5.7
failing to start on Ubuntu 17.10. AFAIK WS 14 starts fine on 17.10.
Furthermore, the
I´ve found a workaround on superuser.com
(https://superuser.com/questions/1261885/vmware-workstation-14-not-
enough-physical-memory-available-to-start-this-vm-w)
They refer to this Github Commit: https://github.com/mkubecek/vmware-
Confirmed on Ubuntu 17.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
This occurs also with Kubuntu 17.10 RTM and VMware Workstation Pro
12.5.7-5813279.
I remember that on 17.04 it didn't occur.
I used to install the same version of VMWare Workstation in Kubuntu 17.04,
running inside a virtual machine (just for testing purposes).
--
You received this bug
I am stuck on 12.5.7 for the time being so if anyone gets past the:
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
problem, please post the workaround.
--
You received this bug
After testing further, I actually see the same thing with VMWare Player
14.0.0:
Could not lock 790528 bytes of memory at 7FAB5BE8A000 (page 7FAB5BE8A000).
Cannot allocate memory.
I, as well, have plenty of memory available.
--
You received this bug notification because you are a member of
I installed VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle
it *Starts* fine.
However, after logging on, I get an error (see screenshot)
Then, when trying to actually start VM, I get things like:
"Could not lock 962560 bytes of memory at 7F767EE48000 (page 7F767EE48000).
Cannot allocate
At the time VMWare Player 14 was unavailable for Linux at least. For the
record, I just tested VMWare Player 14.0.0 for Linux on Ubuntu 17.10 and
it launches fine for me now. Can anybody else confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
VMWare currently ships version 14 of its software. They probably have no
interest to fix this issue.
This is unfortunate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does
** Description changed:
Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
Works under Ubuntu 17.04
ProblemType:
** Tags removed: needs-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage notifications about this bug go to:
Is there a known way to work around the problem? Maybe something like
downgrading libbsd0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715552
Title:
VMWare does not start
To manage
@Joseph Salisbury re: #3
Tried kernel 4.13.0-10
$ uname -a
Linux mbpr13b 4.13.0-10-generic #11-Ubuntu SMP Sun Sep 10 23:39:40 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ vmware
/usr/lib/vmware/bin/vmware-modconfig: Relink
`/lib/x86_64-linux-gnu/libbsd.so.0' with
$ ldd libbsd.so.0
linux-vdso.so.1 => (0x7ffcdafe6000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fda779ee000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fda7760e000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
same error here
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
i did what the error asked me to do and create a symlink for librt.so.1
but the ubuntu did not boot
zam@zam-HP:~$ uname
I agree with Seth:
/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
symbol `clock_gettime'
seems to be an issue related to the build process of librt and libbsd
--
You received this bug notification because you
vmware-modconfig is segfaulting.
[ 6891.596635] vmware-modconfi[23619]: segfault at 2360 ip
2360 sp 7fffebc89488 error 14 in
appLoader[5587e1e3c000+ad000]
I don't see any reason to think this is a kernel issue though, am I
missing something?
--
You received this bug
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
36 matches
Mail list logo
