View previous topic :: View next topic |
Author |
Message |
njcwotx Guru
Joined: 25 Feb 2005 Posts: 587 Location: Texas
|
Posted: Wed May 22, 2013 6:41 pm Post subject: 3.7 kernel and no good vmware tools found |
|
|
I have been trying various vmware-tools packages. In this case I tried Open-vm-tools and Open-vm-tools-kmod. When I start vmware-tools I get this...
Code: | # /etc/init.d/vmware-tools start
* Loading vmblock module ...
modprobe: ERROR: could not insert 'vmblock': Unknown symbol in module, or unknown parameter (see dmesg) [ !! ]
* Mounting vmblock device ...
mount: mount point /proc/fs/vmblock/mountPoint does not exist [ !! ]
* Starting vmtoolsd ... [ ok ]
#
|
I have been having all sorts of trouble with vmwrae tools and 3.7 kernel (really any of the latest) and have dont quite a bit of research and trying new things. I have read a lot about a putname bug and used patches but the vmbock putname error wont go away.
I have tried vmware-modules, vmware tools from vmware, and open-vm-tools. They all have the same issue with vmblock, and supposedly its an issue with newer kernels that is really the culprit. I read that there is vmware-vmblock-fuse command that is the more modern way to mount the filesystem needed but I cant figure out how to get that working. Has anyone gotten a clean vmware tools on a 3.x kernel going? _________________ Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting. |
|
Back to top |
|
|
njcwotx Guru
Joined: 25 Feb 2005 Posts: 587 Location: Texas
|
Posted: Fri May 24, 2013 8:53 pm Post subject: |
|
|
bugzilla had reference to this and I added myself to that case. _________________ Drinking from the fountain of knowldege.
Sometimes sipping.
Sometimes gulping.
Always thirsting. |
|
Back to top |
|
|
gemi n00b
Joined: 10 Oct 2012 Posts: 31
|
Posted: Mon Nov 11, 2013 7:25 am Post subject: |
|
|
any news on this one? I run kernel 3.10.17 and still have problems with vmblock not being available |
|
Back to top |
|
|
hydrapolic Tux's lil' helper
Joined: 07 Feb 2008 Posts: 126
|
|
Back to top |
|
|
libertytrek Apprentice
Joined: 18 Jul 2007 Posts: 258
|
Posted: Sat Feb 01, 2014 3:20 pm Post subject: |
|
|
Just installed open-vm-tools and am having this same problem.
It does say it starts successfully after the error, and vCenter Server Status tab says it is running, but I get this error when restarting it manually or when rebooting.
So, the big question is, will it WORK? I'm only really concerned about ESXi being able to safely shut down and start my gentoo guest OS. |
|
Back to top |
|
|
hydrapolic Tux's lil' helper
Joined: 07 Feb 2008 Posts: 126
|
Posted: Sun Feb 02, 2014 7:25 am Post subject: |
|
|
libertytrek wrote: | Just installed open-vm-tools and am having this same problem.
It does say it starts successfully after the error, and vCenter Server Status tab says it is running, but I get this error when restarting it manually or when rebooting.
So, the big question is, will it WORK? I'm only really concerned about ESXi being able to safely shut down and start my gentoo guest OS. |
Can you please post the output of `emerge --info`? What error do you see? |
|
Back to top |
|
|
libertytrek Apprentice
Joined: 18 Jul 2007 Posts: 258
|
Posted: Sun Feb 02, 2014 11:44 am Post subject: |
|
|
Actually, it turned out to be a simple USE flag issue (bug)...
The default installed it with the -fuse USE flag set. I reinstalled after adding app-emulation/open-vm-tools fuse to package.use and the problem was solved.
I opened a bug, and it will apparently be fixed soon, by making it unconditionally depend on sys-fs/fuse. |
|
Back to top |
|
|
|