http://sourceforge.net/p/open-vm-tools/mailman/open-vm-tools-announce/ This is a development snapshot of open-vm-tools. You can get the new release from Source Forge (note that it is not the default download) or by updating your git mirrors. You can also get more detailed change logs by cloning the git tree. New in this release: * HGFS client and server improvements. * Fixes for HGFS driver to compile with newer kernels. * Tools demon now can use vsock to communicate with the host. * Other fixes and cleanups. There is also a stable release 9.4.0: This release of open-vm-tools matches the VMware Tools package released with vSphere 5.5. It's targeted at server operating systems and virtual appliances. It also contains all the desktop features such as HGFS and Drag & Drop, although those haven't been thoroughly tested in this package.
Tested on 3.10.1-hardened-r1 amd64: # cp open-vm-tools-2013.04.16.1098359-r1.ebuild open-vm-tools-2013.09.16.1328054.ebuild # diff -u open-vm-tools-kmod-2013.04.16.1098359.ebuild open-vm-tools-kmod-2013.09.16.1328054.ebuild --- open-vm-tools-kmod-2013.04.16.1098359.ebuild 2013-08-24 19:31:03.000000000 +0000 +++ open-vm-tools-kmod-2013.09.16.1328054.ebuild 2013-10-18 19:02:48.594510012 +0000 @@ -39,6 +39,24 @@ VMWARE_MOD_DIR="modules/linux" VMWARE_MODULE_LIST="vmblock vmci vmhgfs vmsync vmxnet vsock" + + if kernel_is ge 2 6 32; then + # http://sourceforge.net/p/open-vm-tools/mailman/message/24216640/ + VMWARE_MODULE_LIST=${VMWARE_MODULE_LIST/vmxnet/} + fi + + if kernel_is ge 3 0; then + # http://sourceforge.net/p/open-vm-tools/mailman/message/30762051/ + # http://sourceforge.net/p/open-vm-tools/mailman/message/30282524/ + VMWARE_MODULE_LIST=${VMWARE_MODULE_LIST/vmblock/} + VMWARE_MODULE_LIST=${VMWARE_MODULE_LIST/vmsync/} + fi + + if kernel_is ge 3 9 0; then + # http://sourceforge.net/p/open-vm-tools/mailman/message/30762051/ + VMWARE_MODULE_LIST=${VMWARE_MODULE_LIST/vmci/} + VMWARE_MODULE_LIST=${VMWARE_MODULE_LIST/vsock/} + fi MODULE_NAMES="" BUILD_TARGETS="auto-build HEADER_DIR=${KERNEL_DIR}/include BUILD_DIR=${KV_OUT_DIR} OVT_SOURCE_DIR=${S}" @@ -60,7 +78,6 @@ || die "Sed failed." epatch "${FILESDIR}/frozen.patch" epatch "${FILESDIR}/putname.patch" - epatch "${FILESDIR}/1098359-vmblock-3.10.0.patch" epatch_user }
On my to-do list. Should be able to get to it this weekend.
During startup I see the following messages: vmsvc[1464]: [ warning] [Glib-GObject] invalid (NULL) pointer instance vmsvc[1464]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance' failed vmsvc[1464]: [ warning] [vmsvc] SimpleSock: socket connect failer, error 113: No route to host vmsvc[1464]: [ warning] [vmsvc] VSockChan: Failed to create vsocket channel, err=2 And on shutdown: * start-stop-daemon: fopen '/var/run/vmtoolsd.pid': No such file or directory [ ok ] Some of these messages came up in earlier versions as well. Tested with kernel parameters: CONFIG_VMWARE_VMCI_VSOCKETS=m CONFIG_VMWARE_VMCI=m CONFIG_VMWARE_PVSCSI=y CONFIG_GRKERNSEC_CONFIG_VIRT_VMWARE=y
I have 9.4.0 working with this ebuilds from this overlay: https://github.com/Danez/open-vm-tools-overlay changes for kmod are: if kernel_is -ge 3 0; then VMWARE_MODULE_LIST="vmci vmhgfs vmxnet vsock" else VMWARE_MODULE_LIST="vmblock vmci vmhgfs vmsync vmxnet vsock" fi for the tools I added the following to get configure detecting procps again: export CUSTOM_PROCPS_NAME=procps export CUSTOM_PROCPS_LIBS=-L/usr/lib/libprocps.so
Maybe 9.4.0 is not compatible with the newest kernel...as you can read in the link 9.4.0 and maybe also the dev version are "older" or at least different branch than 9.2.3, which really sounds scary. http://sourceforge.net/mailarchive/message.php?msg_id=31473171 (In reply to Tomas Mozes from comment #3) > During startup I see the following messages: > vmsvc[1464]: [ warning] [Glib-GObject] invalid (NULL) pointer instance > > vmsvc[1464]: [critical] [GLib-GObject] g_signal_emit_by_name: assertion > 'G_TYPE_CHECK_INSTANCE (instance' failed > > vmsvc[1464]: [ warning] [vmsvc] SimpleSock: socket connect failer, error > 113: No route to host > > vmsvc[1464]: [ warning] [vmsvc] VSockChan: Failed to create vsocket channel, > err=2 > > And on shutdown: > * start-stop-daemon: fopen '/var/run/vmtoolsd.pid': No such file or > directory [ ok ] > > Some of these messages came up in earlier versions as well. > > Tested with kernel parameters: > CONFIG_VMWARE_VMCI_VSOCKETS=m > CONFIG_VMWARE_VMCI=m > CONFIG_VMWARE_PVSCSI=y > CONFIG_GRKERNSEC_CONFIG_VIRT_VMWARE=y
+ 19 Oct 2013; Mike Gilbert <floppym@gentoo.org> + +open-vm-tools-kmod-2013.09.16.1328054.ebuild: + Version bump. Exclude modules based on kernel version; thanks to Tomas Mozes + for the idea. +*open-vm-tools-2013.09.16.1328054 (19 Oct 2013) + + 19 Oct 2013; Mike Gilbert <floppym@gentoo.org> + +open-vm-tools-2013.09.16.1328054.ebuild: + Version bump, bug 487484.
(In reply to Daniel T. from comment #4) > I have 9.4.0 working with this ebuilds from this overlay: > https://github.com/Danez/open-vm-tools-overlay > > changes for kmod are: > if kernel_is -ge 3 0; > then > VMWARE_MODULE_LIST="vmci vmhgfs vmxnet vsock" > else > VMWARE_MODULE_LIST="vmblock vmci vmhgfs vmsync vmxnet vsock" > fi > > for the tools I added the following to get configure detecting procps again: > export CUSTOM_PROCPS_NAME=procps > export CUSTOM_PROCPS_LIBS=-L/usr/lib/libprocps.so For new kernels you only need vmhgfs, everything else is in the kernel.
(In reply to Mike Gilbert from comment #6) > + 19 Oct 2013; Mike Gilbert <floppym@gentoo.org> > + +open-vm-tools-kmod-2013.09.16.1328054.ebuild: > + Version bump. Exclude modules based on kernel version; thanks to Tomas > Mozes > + for the idea. > > +*open-vm-tools-2013.09.16.1328054 (19 Oct 2013) > + > + 19 Oct 2013; Mike Gilbert <floppym@gentoo.org> > + +open-vm-tools-2013.09.16.1328054.ebuild: > + Version bump, bug 487484. Thanks Mike for the bump and for a very clean implementation. Maybe consider adding: kernel_is -lt 2 6 32 && MODULES+=" vmxnet"
(In reply to Tomas Mozes from comment #8) > Thanks Mike for the bump and for a very clean implementation. > > Maybe consider adding: > kernel_is -lt 2 6 32 && MODULES+=" vmxnet" The announcement to which you linked mentions vmxnet3 being merged into linux mainline. It does not say the the original vmxnet driver was merged, and a quick look through the linux sources seems to confirm that it has not been. I don't have any VMs using a vmxnet adapter, but this KB article seems to indicate that it is quite different from vmxnet3. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805
Thanks Mike for the link, didn't know there is a difference.
