WS 6.5 and Ubuntu Jaunty 9.04

[Noel]

Yes, yes, Jaunty is only in Alpha. Actually, as of today, not even Alpha 1 is out (it is late). HOWEVER, I have successfully installed WS 6.5, so that's good news. No problems getting the modules built. That happened just fine. Some quirks, such as audio being non-existent and vmnet networks appearing in the Gnone network manager, but I've only just started testing the pre-alpha code.

[Noel]

Some quirks, such as audio being non-existent

It was a bug in Jaunty, now fixed. No problem in VMware other than that it still uses an archaic and barely supported approach to linux audio.

[Noel]

vmnet<x> networks appearing in the Gnone network manager

OK, guys, this one may bite you. What is working for me, and what I believe to be the correct solution, is to add the following to /etc/network/interfaces:

#VMware networks that we do not want managed
iface vmnet1 inet manual
iface vmnet8 inet manual

After that, you should see the Gnome NetworkManager applet identify the networks as "device is unmanaged". This will prevent it from doing such stupid things as adding that network interface to /etc/resolv.conf and making one of them the default route.

I had a different workaround earlier, which no longer works, but the easier and more correct one is the above.

[Noel]

For whatever reason, vmnet-bridge is now only picking up eth0 by default. I need to manually run it with -i wlan0 -i eth0, and then it works properly.

Any idea from those who can see the source code as to what might be going wrong?

[ddalton]

I am trying to run WS 6.5 on Jaunty 9.04 and I am getting the error:

Apr 24 11:57:38 Bubbles kernel: http:// 86.248160 vmware-modconfi[3963]: segfault at 0 ip 00007fff9eebcb84 sp 00007fffae1a4480 error 4 in libc-2.9.so[7fff9ee3b000+168000]

Apr 24 11:58:53 Bubbles kernel: http:// 161.470886 vmware-modconfi[5819]: segfault at 0 ip 00007f408225bb84 sp 00007fff91545830 error 4 in libc-2.9.so[7f40821da000+168000]

[gsh1133]

I had a similar problem, and I found this related thread:

http://communities.vmware.com/message/1083916#1083916

In particular, I followed the suggestion of doing:

mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

before running vmware, and it did the trick.