VMWare tools for unRAID

[Zeron]

Updated packages for 5.0b7 added.

[Zeron]

Updated to open-vm-tools-2011.06.27-437995 for 5.0Beta

[EasyME]

Zeron, Thanks for keeping it fresh.

will add it to my stash as I play with the UnRaid upgrade this weekend.

[axeman]

so if i'm on 4.7 and then upgrade to a 5.0x beta, is it possible ?

i'm a linux newb, so don't know if it's easy to just undo/uninstall this and then install the appropriate 5.0x version ?

[madburg]

I noticed open vm tools posted a new release, figured I would give it a try to compile so we have more than one person on this.
Running ESXi 4.1u1, working on a dev unRAID 5.0beta10 VM.

I get the following when running configure:

Code: [Select]

configure: error: glib >= 2.6.0 is required.
I dont see any version of glib 2.6 or greater as slackware package. Can you assist in what you used to compile this package, please.
Many thanks.

I also exploded the last package you made and renamed the directory /lib/modules/2.6.37.6-unRAID to 2.6.39.3-unRAID, made a new package (this is for 5.0Beta10) and tested installing it and received:

Code: [Select]

Loading VMWare modules.
FATAL: Error inserting vmblock (/lib/modules/2.6.39.3-unRAID/kernel/fs/vmblock/v
mblock.ko): Invalid module format
FATAL: Error inserting vmhgfs (/lib/modules/2.6.39.3-unRAID/kernel/fs/vmhgfs/vmh
gfs.ko): Invalid module format
FATAL: Error inserting vmxnet (/lib/modules/2.6.39.3-unRAID/kernel/drivers/net/v
mxnet.ko): Invalid module format
FATAL: Error inserting vmsync (/lib/modules/2.6.39.3-unRAID/kernel/drivers/misc/
vmsync.ko): Invalid module format
FATAL: Error inserting vmci (/lib/modules/2.6.39.3-unRAID/kernel/drivers/misc/vm
ci.ko): Invalid module format
FATAL: Error inserting vsock (/lib/modules/2.6.39.3-unRAID/kernel/net/vsock/vsoc
k.ko): Invalid module format
Starting VMWare Tools Daemon.
Enabling Time-Sync.
Attempting to mount /mnt/hgfs
Package open-vm-tools-unRaid50beta10.tgz installed.
I was able to suspend and resume. Tried to test "Restart" but once it shutdown it did not restart. web gui did have the VMTools tab, nice touch!.

Lastly, love that you shared this with us!

[gfjardim]

vmtools modules are compiled against a specific kernel, changing the directory path is not enough to make it work, you need to recompile those modules.

[madburg]

vmtools modules are compiled against a specific kernel, changing the directory path is not enough to make it work, you need to recompile those modules.

Thank makes sense as the kernel did change in 5.0Beta10 (still learning). So I guess then the most important is were does one get the  glib >= 2.6.0 version? OR what dev tools did you use Zeron to compile.

[gfjardim]

I don't know if Tom changed the development platform, but it was Slackware 13.1 last time I checked.

[Zeron]

open-vm-tools-2011.07.19-450511-unRaid50beta10-dan1.tgz Added.  Will post an update to open-vm-tools-2011.07.19-450511 for 4.7 soon.

[Zeron]

so if i'm on 4.7 and then upgrade to a 5.0x beta, is it possible ?

i'm a linux newb, so don't know if it's easy to just undo/uninstall this and then install the appropriate 5.0x version ?

Yes - just remove the version for 4.7 and put the 5.0Beta on in it's place.  Just make sure to remove the 4.7 one before you upgrade - you do not want it to load under V.5

[madburg]

open-vm-tools-2011.07.19-450511-unRaid50beta10-dan1.tgz Added.  Will post an update to open-vm-tools-2011.07.19-450511 for 4.7 soon.

Thanks for this lastest!

No errors now when I installed. Tried to restart via vSphere Client, it shutdown unRAID but did not restart, any idea?

Would you be willing to share the dev tools you use and their version to get this to compile (or work around)? No pressure, it would be nice though.

[Zeron]

Thanks for this lastest!

No errors now when I installed. Tried to restart via vSphere Client, it shutdown unRAID but did not restart, any idea?

Both the reboot event and shutdown event call the same script:
/etc/vmware-tools/scripts/poweroff-vm-default.d/01-halt

I have not found how to get the reboot event to call a different one, or found a way to detect that the event is reboot instead of shutdown.

Would you be willing to share the dev tools you use and their version to get this to compile (or work around)? No pressure, it would be nice though.

I install the following packages on my development VM in order to do the build (for v. 5.0beta-10):
binutils-2.20.51.0.8-i486-1.txz
cpio-2.9-i486-2.txz
cxxlibs-6.0.13-i486-2.txz
gcc-4.4.4-i486-1.txz
glib2-2.22.5-i486-1.txz
glibc-2.11.1-i486-3.txz
kernel-headers-2.6.33.4_smp-x86-1.txz
make-3.81-i486-1.txz
nano-2.2.4-i486-1.txz
ncurses-5.7-i486-1.txz
patch-2.5.4-i486-1.txz
perl-5.10.1-i486-1.txz
pkg-config-0.23-i486-2.txz
pkgtools-13.1-noarch-1.tgz
libdnet-1.11-i486-5sl.txz

linux-2.6.39.3.tar.gz
open-vm-tools-2011.07.19-450511.tar.gz

I compile the kernel using the files from /usr/src/linux-2.6.39.3-unRAID/ merged with the files from linux-2.6.39.3.tar.gz

Then open-vm-tools can be compiled.

[ftp222]

Thank you for keeping up with these tool packages, they are much appreciated!

[madburg]

I install the following packages on my development VM in order to do the build (for v. 5.0beta-10):
binutils-2.20.51.0.8-i486-1.txz
cpio-2.9-i486-2.txz
cxxlibs-6.0.13-i486-2.txz
gcc-4.4.4-i486-1.txz
glib2-2.22.5-i486-1.txz
glibc-2.11.1-i486-3.txz
kernel-headers-2.6.33.4_smp-x86-1.txz
make-3.81-i486-1.txz
nano-2.2.4-i486-1.txz
ncurses-5.7-i486-1.txz
patch-2.5.4-i486-1.txz
perl-5.10.1-i486-1.txz
pkg-config-0.23-i486-2.txz
pkgtools-13.1-noarch-1.tgz
libdnet-1.11-i486-5sl.txz

linux-2.6.39.3.tar.gz
open-vm-tools-2011.07.19-450511.tar.gz

I compile the kernel using the files from /usr/src/linux-2.6.39.3-unRAID/ merged with the files from linux-2.6.39.3.tar.gz

Then open-vm-tools can be compiled.

I highlighted the ones i had installed, the rest I did not have. Thanks for sharing, I will add them (is perl really needed?). Learning here, why would you need the linux 2.6.39.2 tar? if the that is what Tom already installed? and how does one merge them?


Went looking for the event id of a restart:

In addition to the scripts outlined above, an additional mechanism is provided on Linux, Solaris and FreeBSD guests for executing commands when a virtual machine is either shut down or rebooted. These are specified in the /etc/vmware-tools.conf file using the halt-command = and reboot-command = directives.

But I dont see open vm tools supplying it.

Looking throught the source I found the following line of code in "powerOps.c" dont know if it helps:

state->scriptEnabled[GUESTOS_STATECHANGE_HALT] =
         state->scriptEnabled[GUESTOS_STATECHANGE_REBOOT] = enabled;

I found references that it works just fine on our linux versions.
Best I could find http://www.mail-archive.com/open-vm-tools-devel@lists.sourceforge.net/msg00615.html

[Zeron]

I install the following packages on my development VM in order to do the build (for v. 5.0beta-10):
binutils-2.20.51.0.8-i486-1.txz
cpio-2.9-i486-2.txz
cxxlibs-6.0.13-i486-2.txz
gcc-4.4.4-i486-1.txz
glib2-2.22.5-i486-1.txz
glibc-2.11.1-i486-3.txz
kernel-headers-2.6.33.4_smp-x86-1.txz
make-3.81-i486-1.txz
nano-2.2.4-i486-1.txz
ncurses-5.7-i486-1.txz
patch-2.5.4-i486-1.txz
perl-5.10.1-i486-1.txz
pkg-config-0.23-i486-2.txz
pkgtools-13.1-noarch-1.tgz
libdnet-1.11-i486-5sl.txz

linux-2.6.39.3.tar.gz
open-vm-tools-2011.07.19-450511.tar.gz

I compile the kernel using the files from /usr/src/linux-2.6.39.3-unRAID/ merged with the files from linux-2.6.39.3.tar.gz

Then open-vm-tools can be compiled.

I highlighted the ones i had installed, the rest I did not have. Thanks for sharing, I will add them (is perl really needed?). Learning here, why would you need the linux 2.6.39.2 tar? if the that is what Tom already installed? and how does one merge them?

Yes; linux-2.6.39.3.tar.gz is needed.  We need to have the kernel sources for open-vm-tools to compile.

Some of those packages are not required - don't think you really need perl.  I just have it because I use the same script to install packages to compile a few things.

You do need to add pkgtools, pkg-config and libdnet for open-vm-tools.  I will experiment when I have some time to see what packages from that list can be removed.

once you get everything in place you can compile open-vm-tools using this configure command:

./configure \
   --enable-static \
   --disable-multimon \
   --disable-unity \
   --disable-docs \
   --disable-tests \
   --without-gtk2 \
   --without-gtkmm \
   --without-x \
   --without-pam \
   --without-icu \
   --host=i686-pc-linux-gnu \
   --build=i686-pc-linux-gnu