VMWare Tools 6.5.0, build-118116, and Ubuntu 8.10 guests

이글도 참조하시길.. :  http://ubuntu.or.kr/viewtopic.php?f=6&t=3183

It seems that VMWare Tools 6.5.0, build-118166, and hence VMWare Workstation 6.5.0, are broken for Ubuntu 8.10 Intrepid Ibex hosts. I discussed the problem briefly in this post.

Intrepid installs flawlessly as a guest into Workstation 6.5.0. After installing, I next updated the system and installed the build-essential packages:

sudo aptitude install build-essential

I then installed VMWare Tools from the menu VM/Install VMWare Tools… This nets an icon on the desktop for the virtual CD. Double-click on the CD icon to bring up the file manager:

Contents of the VMWare Tools CD image

Double-click on the .tar.gz file to open the archive:

VMWare Tools archive contents

Select the vmware-tools-distrib folder, click on Extract at the top:

Extracting the Tools installation directory

Chose the /tmp/ directory for the target, check the All Files box at the bottom right, then click on the Extract button on the lower right. This will take a few seconds to complete.

When Extract completes, you can close all the open windows because you won’t be needing them again. Open the Terminal and type:

cd /tmp/vmware-tools-distrib
sudo ./vmware-install.pl

At this point, simply answer all the prompts. I recommend accepting the defaults for all the answers. Some steps take much longer than others, so be patient. One of the questions will be if you want to run the Tools setup script, /usr/bin/vmware-config-tools.pl. That answer is yes as well. Again, accept all the defaults. However, when it gets to the vsock module, you will get this error:

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vsock-only’
make -C /lib/modules/2.6.27-7-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.27-7-generic’
CC [M] /tmp/vmware-config0/vsock-only/linux/af_vsock.o
CC [M] /tmp/vmware-config0/vsock-only/linux/driverLog.o
CC [M] /tmp/vmware-config0/vsock-only/linux/util.o
/tmp/vmware-config0/vsock-only/linux/util.c: In function ‘VSockVmciLogPkt’:
/tmp/vmware-config0/vsock-only/linux/util.c:157: warning: format not a string literal and no format arguments
CC [M] /tmp/vmware-config0/vsock-only/linux/vsockAddr.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
WARNING: “VMCIDatagram_CreateHnd” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_DestroyHnd” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Subscribe” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_DeviceGet” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyFromQueueV” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Detach” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_GetContextID” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_Send” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Alloc” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Unsubscribe” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyToQueueV” [/tmp/vmware-config0/vsock-only/vsock.ko] undefined!
CC /tmp/vmware-config0/vsock-only/vsock.mod.o
LD [M] /tmp/vmware-config0/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.27-7-generic’
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config0/vsock-only’
Unable to make a vsock module that can be loaded in the running kernel:
insmod: error inserting ‘/tmp/vmware-config0/vsock.o’: -1 Unknown symbol in module
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.

The advice in this error message is bogus on how to solve the issue. If it were correct, none of the other modules would have compiled, either. There is no way of which I know to solve this. The virtual machine will work, but you won’t be able to cut-and-paste between the host and guest, nor will the mouse will not move seamlessly between the guest and host. In any event, continue the installation by accepting the default answers.

And that’s not all. Whether it is because of the bad/missing vsock module or not I cannot say, but the Tools installation apparently failed to activate the accelerated 3D graphics as well. This is the short error that results, although you may get a much longer error with the same bottom line:

Detected X.org version 7.4.2

No drivers for X.org version: 7.4.2

This obviously isn’t good. Again, I have no workaround to suggest. When Tools finishes installing, it will tell you that the install is successful although it obviously wasn’t. You will need to start your X-server, which is easiest if you close all programs and hit ctrl-alt-Backspace. That will enable the mouse and video changes to work, although most of the mouse ones won’t anyway.

VMWare has yet to even acknowledge these two issues on their forums. Your virtual machines will work, but they will have the limitations listed above. The video resolution and file sharing do still work, so you can pass data between the host and guest through the share director(y)(ies). It’s annoying, but it works. I find the lack of seamless mouse mobility between the host and guest the most annoying problem.

I’ll post back when a solution to the vsock module compilation and 3D video problems in Intrepid guests have fixes or workarounds.