open-vm-tools-kmod-2013.09.16.1328054 fails to compile against linux-3.16. The error is: make[1]: Entering directory `/usr/src/linux-3.16.0' CC [M] /var/tmp/portage/app-emulation/open-vm-tools-kmod-2013.09.16.1328054/work/open-vm-tools-2013.09.16-1328054/modules/linux/vmxnet/vmxnet.o /var/tmp/portage/app-emulation/open-vm-tools-kmod-2013.09.16.1328054/work/open-vm-tools-2013.09.16-1328054/modules/linux/vmxnet/vmxnet.c: In function 'vmxnet_probe_device': /var/tmp/portage/app-emulation/open-vm-tools-kmod-2013.09.16.1328054/work/open-vm-tools-2013.09.16-1328054/modules/linux/vmxnet/vmxnet.c:1148:7: error: 'struct net_device' has no member named 'do_ioctl' dev->do_ioctl = vmxnet_ioctl; ^ I will attach the build log, emerge --info and -pqv, and the environment file. While I am rather clueless, I will happily provide more info or test things. Reproducible: Always Steps to Reproduce: 1. emerge -1 =open-vm-tools-kmod-2013.09.16.1328054 Actual Results: Compilation fails. Expected Results: Compile.
Created attachment 382830 [details] build log
Created attachment 382832 [details] emerge --info
Created attachment 382834 [details] emerge -pqv
Created attachment 382836 [details] build's environment file
I updated portage's ebuilds to work with the recently released open-vm-tools-9.4.6. 9.4.6 needs patches to work with Linux 3.16, so I brought in those from ArchLinux: https://github.com/davispuh/open-vm-tools-dkms The ebuilds are available from my overlay: https://github.com/madsl/fol4 Because of the non-standard number versioning scheme, portage will think that this version is older than the one in portage tree. So you might need this in package.mask: > app-emulation/open-vm-tools-kmod::gentoo > app-emulation/open-vm-tools::gentoo The kernel module vmhgfs is not auto-loaded. I don't know if the init scripts lacks something regarding this or not.
It seems like VM_DRAG_AND_DROP has to be set to "no" with this version. If left enabled, vSphere Client will not be able to see that VMware Tools is running...
Hi Mads, thanks for your work, and sorry for me being unreactive (a.k.a. on holidays). Sad to say, either me or the vphere client has eaten my gentoo system disk, so I cannot properly test your ebuild right now. Oh well. If needed, I can setup a new gentoo VM to test the ebuild... ...but would rather not have to do it so soon. Please ping me if my test is more than marginally helpful. Thanks and apologies, Andre
Created attachment 385400 [details] build log
Created attachment 385402 [details] emerge --info
Created attachment 385404 [details] emerge -pqv
Created attachment 385406 [details] build's envirorments file
@abstr4kt: That error has nothing to do with this bug; for one thing, this is about linux-3.16, you are building against 3.15. You are just _running_ 3.16. I guess you forgot updating the linux symlink. Also, according to the build.log, the build fails because your kernel source tree is unconfigured. You should retry with a proper .config. Finally, you also should try building the current version from Mads' Repo, as referenced above. The 2013.* versions are known to not compile against 3.16 anyway.
@Andre Muller You are right i forgot to update the symlink sorry about that. I update it and than tryed again to emerge open-vm-tools-kmod but as you said it won't build against 3.16 . I didn't tryed Mads's ebuilds i can't do it for now. I attached here my log just because the status of this BUG say UNCONFIRMED. Hoping that may help i'll attach the new build.log with the correct symlink to 3.16.
Created attachment 385438 [details] build log 3.16
I am having an unfortunate side problem and I am wondering if anyone else is seeing this issue, with the latest open-vm-tools on a virtual gentoo machine I cannot logout, restart or shutdown without freezing. Has anyone else seen this?
(In reply to Billy DeVincentis from comment #15) > I am having an unfortunate side problem and I am wondering if anyone else is > seeing this issue, with the latest open-vm-tools on a virtual gentoo machine > I cannot logout, restart or shutdown without freezing. > Has anyone else seen this? Have you tried what I mentioned in comment #6? Talking about /etc/conf.d/vmware-tools ...
Tried that but no difference, still freezes, I need to go to the tray icon and hit shutdown all vms 2 or 3 times to get it to shutdown
Please try to limit discussion to the issue reported. Keep in mind that several people get an email every time you reply to this bug; please seek support in another venue.
*** Bug 526636 has been marked as a duplicate of this bug. ***
Your ebuilds seem to be working here is the command to check the svn svn checkout https://github.com/madsl/fol4/trunk
Created attachment 387772 [details] build log
I need this patch in the stable portage to run 3.16 stable kernel. When is this getting fixed? And why the hell is this still unconfirmed??
(In reply to ixuz from comment #22) > I need this patch in the stable portage to run 3.16 stable kernel. When is > this getting fixed? And why the hell is this still unconfirmed?? Comments like this do not encourage me to spend time on this. You probably don't even need this package for anything; it installs kernel modules that are not particularly useful on modern VMWare systems.
(In reply to Mike Gilbert from comment #23) > (In reply to ixuz from comment #22) > > I need this patch in the stable portage to run 3.16 stable kernel. When is > > this getting fixed? And why the hell is this still unconfirmed?? > > Comments like this do not encourage me to spend time on this. > Sorry about that, but that's just the frustation with using gentoo in productive environments. Almost every kernel upgrade (or any other system upgrade) seems to be more and more a pain. I know it's not the right place here, but seeing how smooth and easy it is to administer systems like e.g. Ubuntu LTS Server nowadays, gentoo is just way too time expensive. And I say that although I really really like gentoo (but more often less in business...)! > You probably don't even need this package for anything; it installs kernel > modules that are not particularly useful on modern VMWare systems. Tell me more please. I thought we need a kind of VMware tools to have for e.g. pvscsi, vmxnet3 and ballooning support. And how can I shutdown/reboot machines without VM tools from vCenter?
(In reply to ixuz from comment #24) > > You probably don't even need this package for anything; it installs kernel > > modules that are not particularly useful on modern VMWare systems. > > Tell me more please. I thought we need a kind of VMware tools to have for > e.g. pvscsi, vmxnet3 and ballooning support. And how can I shutdown/reboot > machines without VM tools from vCenter? open-vm-tools-kmod currently only installs 2 modules on a modern kernel: vmxnet - The original vmxnet driver vmhgfs - Something to do with drag-and-drop? Not sure what this is. If you don't need either of those, just install open-vm-tools; if you set USE="-modules", it will not pull in open-vm-tools-kmod. The pvscsi, vmxnet3, and ballooning have been part of the mainline kernel for some time now. See the config options below. CONFIG_VMWARE_VMCI CONFIG_VMWARE_VMCI_VSOCKETS CONFIG_VMWARE_PVSCSI CONFIG_VMXNET3 CONFIG_VMWARE_BALLOON
(In reply to Mike Gilbert from comment #25) > (In reply to ixuz from comment #24) > > > You probably don't even need this package for anything; it installs kernel > > > modules that are not particularly useful on modern VMWare systems. > > > > Tell me more please. I thought we need a kind of VMware tools to have for > > e.g. pvscsi, vmxnet3 and ballooning support. And how can I shutdown/reboot > > machines without VM tools from vCenter? > > open-vm-tools-kmod currently only installs 2 modules on a modern kernel: > > vmxnet - The original vmxnet driver > vmhgfs - Something to do with drag-and-drop? Not sure what this is. > > If you don't need either of those, just install open-vm-tools; if you set > USE="-modules", it will not pull in open-vm-tools-kmod. > > The pvscsi, vmxnet3, and ballooning have been part of the mainline kernel > for some time now. See the config options below. > > CONFIG_VMWARE_VMCI > CONFIG_VMWARE_VMCI_VSOCKETS > CONFIG_VMWARE_PVSCSI > CONFIG_VMXNET3 > CONFIG_VMWARE_BALLOON Thank you for that information. It solved my problem!
Comment 25 the module hgfs is for the access from the client os to the hostsystem see https://www.vmware.com/support/ws4/doc/running_sharefold_ws.html (see bug 507026 for the patches and instructions)
Probably a bump to 2015.0 release will help: http://www.open-mesh.org/projects/open-mesh/wiki/2015-04-28-batman-adv-2015-0-release
(In reply to Pacho Ramos from comment #28) > Probably a bump to 2015.0 release will help: > http://www.open-mesh.org/projects/open-mesh/wiki/2015-04-28-batman-adv-2015- > 0-release Hm. I don't get it, why do you link this? Anyway, I guess this bug can be marked as WONTFIX, as Mike points out, vmxnet is not needed and you should just use the in-kernel driver instead.
CCing treecleaners
IMO open-vm-tools can have the kernel supported modules ripped out leaving things like vmhgfs and enterprise features in the package. i can get the ebuild up to speed on this change but will still need to clean out older version that are not supported by any current supported gentoo kernel version.
We cannot treeclean this until reverse deps are dropped :S $ grep -r app-emulation/open-vm-tools-kmod */*/*.ebuild app-emulation/open-vm-tools/open-vm-tools-9.10.0_p2476743.ebuild: modules? ( app-emulation/open-vm-tools-kmod ) app-emulation/open-vm-tools/open-vm-tools-9.4.0.1280544.ebuild:RDEPEND="app-emulation/open-vm-tools-kmod
dropped