vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

SoFarSoGood · 2011-01-28 15:22:20

Hi all,

After upgrading on 2011-01-27 (bunch of packages, see below),
vmware player failed with a "machine busy" error requester.

The vmware logfile showed this error:

vmx| NOT_IMPLEMENTED /build/mts/release/bora-324285/bora/lib/user/utilPosix.c:128
vmx| Unable to get core dump limit: Operation not permitted.
vmx| Child process 4175 failed to dump core (status 0x6).

I had to downgrade the following packages:

linux-api-headers (2.6.37-1 -> 2.6.36.2-1)
glibc (2.13-1 -> 2.12.2-1) (dependency)
binutils (2.21-3 -> 2.21-2) (dependency)

Now it works again. Still kept the newer kernel26 2.6.36.3-2 installed.

Strange, why are linux-api-headers 2.6.37-1 installed while the kernel
is still a 2.6.36.x?

Off-topic:

Registering to this forum is tricky when you're on a Windows machine,
confronted with a question like:

What is the output of "date -u +%W$(uname)|sha256sum|sed 's/\W//g'"?>

Hmmmmm.

... and better don't ask "What is the output of "rm -rf /*"

Cheers.

Last edited by SoFarSoGood (2011-01-28 15:54:20)

Inxsible · 2011-01-28 15:38:54

2.6.37 is still in testing. You must have enabled testing in pacman.conf which is why it installed 2.6.37.

SoFarSoGood · 2011-01-28 15:42:59

Definitely not enabled testing; only core, extra and community.

The 2.6.37 kernel and kernel-headers are not installed via pacman -Syu,
but the linux-api-headers 2.6.37-1 are!

the package is in /var/lib/pacman/sync/core/linux-api-headers-2.6.37-1

(i686 btw.)

Last edited by SoFarSoGood (2011-01-28 15:46:05)

xl666 · 2011-01-28 18:38:36

I had the exact same problem. I did the downgrades that SoFarSoGood said and now my vmware works. Thanks SoFarSoGood, and as you said, is pretty weird that the api headers are on version 2.6.37 since all the other kernel related packages are on 2.6.36 (I don't have test enabled).

jeroenh · 2011-01-29 12:54:08

I did not have to remove linux-api-header. Downgrading glibc and binutils was enough to bring Workstation back to life.

SoFarSoGood · 2011-01-30 11:00:50

Ah, good to know. I figured it must have to do with either the kernel or one of the three other packages. It wasn't the kernel, so i uninstalled
the others and my vmware worked again. Alright, one down..

falconindy · 2011-01-30 14:58:23

Likely related to the glibc 2.12.2 rebuild you overstepped which bumped the minimum kernel version to 2.6.27, thereby deprecating/removing old functionality (which vmware still depends on).

http://projects.archlinux.org/svntogit/ … 9931cd7706

firewalker · 2011-01-31 13:07:56

The current glibc is 2.13.1. Is there a way to maintain the functionality of Vmware? Re enable a patch perhaps?

Allan · 2011-01-31 21:25:26

falconindy wrote:

Likely related to the glibc 2.12.2 rebuild you overstepped which bumped the minimum kernel version to 2.6.27, thereby deprecating/removing old functionality (which vmware still depends on).
http://projects.archlinux.org/svntogit/ … 9931cd7706

That should have no effect, as the functionality is provided by the kernel rather than glibc.

firewalker · 2011-02-01 18:20:05

the two packets I had to change was glibc and binutils. Any, ideas/solution?

dhave · 2011-02-07 20:17:02

firewalker wrote:

the two packets I had to change was glibc and binutils. Any, ideas/solution?

I'm in the same boat. I'd prefer not to revert major packages if I can help it.

firewalker · 2011-02-09 11:36:31

Did anyone found a solution?

Mr.Elendig · 2011-02-09 11:48:07

firewalker wrote:

Did anyone found a solution?

There are patches on the vmware forum for kernel .37 and so on.

A much better solution though is to use qemu, since it doesn't break everytime there is a kernel/xorg/glibc update.

firewalker · 2011-02-09 11:59:04

Mr.Elendig wrote:

firewalker wrote:
Did anyone found a solution?
There are patches on the vmware forum for kernel .37 and so on.
A much better solution though is to use qemu, since it doesn't break everytime there is a kernel/xorg/glibc update.

I have already used .37 kernel patches in order to compile the modules. It it something new?

meijin · 2011-02-13 19:17:20

I Have the same problem. any other option instead of downgrading?

Assaf

Claj · 2011-02-14 02:26:28

I have the same problem, but if I run as root (or sudo), vmware works fine.

meijin · 2011-02-14 08:11:43

Claj wrote:

I have the same problem, but if I run as root (or sudo), vmware works fine.

I have the same problem. do i have i686 or X86_64?

Assaf

firewalker · 2011-02-14 09:46:20

I have tried to make vmware to load the old libc with LD_PRELOAD but it doesn;t seem to work.

With out LD_PRELOAD:

ldd /usr/lib/vmware/bin/vmware-vmx /home/firewalker/vmware/ArchLinux/ArchLinux.vmx

linux-gate.so.1 =>  (0xb771b000)
        libm.so.6 => /lib/libm.so.6 (0xb76c2000)
        libdl.so.2 => /lib/libdl.so.2 (0xb76be000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb76a4000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xb7589000)
        libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb7583000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xb7575000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb756e000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7566000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0xb7559000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7544000)
-->   libc.so.6 => /lib/libc.so.6 (0xb73f7000)
        /lib/ld-linux.so.2 (0xb771c000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb73df000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xb73dc000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb73d7000)

NOT_IMPLEMENTED /build/mts/release/bora-324285/bora/lib/user/utilPosix.c:128

With LD_PRELOAD:

LD_PRELOAD=/home/firewalker/Desktop/glibc-2.12/lib/libc.so.6 ldd /usr/lib/vmware/bin/vmware-vmx /home/firewalker/vmware/ArchLinux/ArchLinux.vmx

usr/lib/vmware/bin/vmware-vmx:
        linux-gate.so.1 =>  (0xb78d7000)
-->   /home/firewalker/Desktop/glibc-2.12/lib/libc.so.6 (0xb778a000)
        libm.so.6 => /lib/libm.so.6 (0xb7732000)
        libdl.so.2 => /lib/libdl.so.2 (0xb772e000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb7714000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xb75f8000)
        libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb75f3000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xb75e5000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb75de000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb75d6000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0xb75c9000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb75b3000)
        /lib/ld-linux.so.2 (0xb78d8000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb759b000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xb7598000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7593000)

NOT_IMPLEMENTED /build/mts/release/bora-324285/bora/lib/user/utilPosix.c:128

Claj · 2011-02-14 22:43:51

meijin wrote:

Claj wrote:
I have the same problem, but if I run as root (or sudo), vmware works fine.
I have the same problem. do i have i686 or X86_64?
Assaf

I have x86 kernel.

spookykid · 2011-02-15 17:02:03

yep, if I run with root everything is ok

firewalker · 2011-02-15 18:21:31

The thing is that vmware-vmx has the suid set.

meijin · 2011-02-20 07:39:35

firewalker wrote:

The thing is that vmware-vmx has the suid set.

is thats help?
did any one open a bug report on this?

Assaf

Claj · 2011-03-09 22:57:49

The problem is fixed with glibc 2.13-4 and kernel26-headers 2.6.37.2-1

firewalker · 2011-03-09 23:06:55

Claj wrote:

The problem is fixed with glibc 2.13-4 and kernel26-headers 2.6.37.2-1

Nice!

Arch Linux

#1 2011-01-28 15:22:20

vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#2 2011-01-28 15:38:54

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#3 2011-01-28 15:42:59

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#4 2011-01-28 18:38:36

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#5 2011-01-29 12:54:08

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#6 2011-01-30 11:00:50

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#7 2011-01-30 14:58:23

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#8 2011-01-31 13:07:56

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#9 2011-01-31 21:25:26

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#10 2011-02-01 18:20:05

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#11 2011-02-07 20:17:02

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#12 2011-02-09 11:36:31

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#13 2011-02-09 11:48:07

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#14 2011-02-09 11:59:04

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#15 2011-02-13 19:17:20

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#16 2011-02-14 02:26:28

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#17 2011-02-14 08:11:43

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#18 2011-02-14 09:46:20

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#19 2011-02-14 22:43:51

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#20 2011-02-15 17:02:03

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#21 2011-02-15 18:21:31

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#22 2011-02-20 07:39:35

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#23 2011-03-09 22:57:49

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

#24 2011-03-09 23:06:55

Re: vmware fails after linux-api-headers ->2.6.37 [solved by downgrading]

Board footer