VMware Communities
dmanus
Contributor
Contributor

Workstation 6.5.1 on openSUSE 11.1 - VMCI fails

I am trying to install Workstation 6.5.1 under openSUSE 11.1. A clean install segfaults trying to compile the modules, but I found elsewhere to try removing /usr/lib/vmware/modules/binary. That got it to compile, but vmci and the blocking file system fail to load. It worked fine under openSUSE 11.0. Any ideas?

Reply
0 Kudos
9 Replies
str
Contributor
Contributor

No idea, but the same problem.

str.

Reply
0 Kudos
str
Contributor
Contributor

.

Message was edited by: str

Reply
0 Kudos
dmanus
Contributor
Contributor

Well at least you made me feel less crazy, but still this is just confusing. I have it working like a charm on my laptop (ubuntu hardy 32bit), so either this is a suse problem, or a 64 bit problem (or so I think)

Reply
0 Kudos
str
Contributor
Contributor

Yes, I posted it to make you feel less «crazy». I tryed it sveral times.

vmware produces a message during building the modules, that a sign is missinterpreted.

Anyway, VMCI missing Windows 2000 runs under SuSe 11.1 in VMmare, but not Windows XP.

str.

Reply
0 Kudos
dmanus
Contributor
Contributor

thats odd. I know that workstation can be installed (on suse 11.1 64 bit, i believe). My brother has had no problems with his install, and he can't figure out why it wont config properly

Reply
0 Kudos
dmanus
Contributor
Contributor

Fixed it--

After a quick turn on google, I found (for Fedora 10beta 64 bit) the fix

Here is the original forum

all you have to do is

download the attached script

cd directory_with_script

chmod +x vmware-build-modules

sudo ./vmware-build-modules

Let the script run, and just start up vmware

Reply
0 Kudos
str
Contributor
Contributor

Many thanks. I will try it.

str.

PS: Thanks! Now vmware runs very well. str.

Reply
0 Kudos
R_Lerch
Contributor
Contributor

I had a similar problem - the installation of VMware-Workstation-6.5.1-126130.x86_64.bundle "worked",

but then vmware bombed on execution with:

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

modinfo: could not find module vmmon

modinfo: could not find module vmnet

modinfo: could not find module vmblock

modinfo: could not find module vmci

modinfo: could not find module vsock

/usr/bin/vmware: line 31: 13260 Segmentation fault

Running the script helped. If you have the same problem you may need to install the kernel-source and kernel-syms

packages to run it. I pretty sure the "vmware-any-any-update packages" of old (which did something quite similar)

required them, too.

Thank you, dmanus!

Reply
0 Kudos
gkuenning
Contributor
Contributor

Thanks again to this thread for saving all of us.

<rant>

I think the larger problem here is VMware's continued inability/refusal to work with major software vendors to make sure its products work correctly. If you upgrade your OS and ask VMware for help, their answer is "we don't support the latest release." Gee, thanks. Since when did I need your permission to keep my OS updated?

What really sucks is that the fixes are so simple. That script is a whopping 796 bytes. What, the people at VMware couldn't figure it out on their own? They couldn't have downloaded OpenSuSE 11.1 beta and Fedora and run a few tests? They're now shipping a "simple" installer that gives you no feedback and provides no documentation, and fails by SEGFAULTING?

I've been a VMware user and advocate since 1.0, but I'm really getting tired of having to spend hours searching for solutions every time I make a little configuration change. It's just not that hard to write portable software. I'd love to have an alternative to this stuff.

</rant>

Reply
0 Kudos