Hello Bernd,
Am 02.02.2014, 13:58 Uhr, schrieb Bernd Zeimetz <[email protected]>:
Hi Norbert!
Thanks a lot for your research!
After some research and alot more trial and error, I found that there
are multiple Issues:
1. the vmblock filesystem is never started
2. the file /usr/bin/vmware-user-suid-wrapper is missing the
apparently critical suid bit (I never knew about this bit before)
3. the vmtoolsd instances spawned by vmware-user-suid-wrapper dont
handle SIGUSR1 and SIGUSR2 as they should.
[...]
For Point 1 I attached a fixed etc/init.d/open-vm-tools. It has some
things commented out because of Point 3.
Actually I'm not sure if all of these changes should go into the init
script
of open-vm-tool - for running VMs in ESX and managing them via vcenter
- especially when they don't have a Desktop enabled at all - I'm not sure
if one really wants to have all the drag&drop features and other fancy
stuff.
It might make more sense to put these things into an extra init script
in the open-vm-tools-desktop package, which should ship what you need
if you run a Debian installation with a full blown desktop, at least
in non-esx installations (vmware player, or however that thing was
called :))
Ok, my bad, the bugreport should be about open-vm-toolbox.
We use VMWare Workstation at the office, but in terms of drivers
it seems rather similar to VMWare Player which I use at home.
Point 2 is easily fixed with chmod 04555
/usr/bin/vmware-user-suid-wrapper.
Makes sense. I'll add a dpkg-statoverride.
Point 3 is likely for upstream?
The issue here is that you cant stop/start the vmblock filesystem as
long as anyone is using it. Supposedly you would send a signal to the
user daemons, telling them to give up any references to it - but its
not handled and instead the user daemon terminates.
And another bug would be that the vmxnet driver is not picked up
automatically, for this to work you would need to add the module to
the initital ramdisk. Along with other m0dules which should have the
same problem, but I cant verify it:
which version of open-vm-tools are you using now? There is a pre-inst
hook in the current version which should load vmxnet before loading
pcnet32.
I'd guess it should find its way into the initrd, too. But I don't have
any oldish vmware installations to give vmxnet a try. These days vmxnet3
is being used, which is shipped with the upstream kernel and happily
put into the initrd by default as it is a used module.
I am using the packages from Wheezy:
http://packages.debian.org/wheezy/open-vm-toolbox
And I think you are wrong about vmxnet, its still the actually used driver
in the
non-server Versions of VMWare. I dont even know if you can use vmxnet3 in
those.
I crosschecked with the official VMWare-Tools and its the same there,
unless vmxnet
is in the initrd it will not be picked up automatically.
vmw_pvscsi
Actually I've never seen that module in use bevore, I'll have to
investigate what I have to do to use it - I guess I have to pass a full
disk device into the VM. As it is shipped with the vanilla kernel I would
not expect problems.
Cant say I fully understand the startup processes (especially transition
from initrd to final kernel),
I just went with what VMWare-Tools are doing, and those 3 modules are in
"their" initrd,
maybe if the ethernet got configured as "pcnet32" during initrd startup
then it wont get reconfigured later?
I am not using the server versions so I just assume I am not even able to
utilize all of those drivers.
I'm thinking about organizing a bug squashing party here in salzburg
around the end of may - maybe you'd like to come so we can bring the
package into a useful shape together? I can handle the server/vm
parts, but I'm not really a desktop/gui user.
Thanks for your work,
Bernd
I see this "maintainance" of a single packet as some sort of filler
inbetween,
so I think my presence there would primary dimish your food reserves ;)
Thanks for your offer though and I will still help and test per mail
Kind regards,
Norbert
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
