Bug 27648 - open-vm-tools dokumentieren
open-vm-tools dokumentieren
Status: RESOLVED DUPLICATE of bug 31085
Product: UCS manual
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Docu maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-19 17:46 CEST by Moritz Muehlenhoff
Modified: 2013-11-11 11:36 CET (History)
5 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2012-06-19 17:46:12 CEST
Die Einrichtung sollte in einem Cool Solutions-Artikel beschrieben werden.

+++ This bug was initially created as a clone of Bug #26041 +++

Wir sollten die open-vm-tools für UCS 3.0 mit Paketieren:


http://open-vm-tools.sourceforge.net/
http://packages.debian.org/source/squeeze/open-vm-tools
Comment 1 Moritz Muehlenhoff univentionstaff 2013-06-14 13:47:52 CEST
These modules are now shipped in UCS. Maybe we should add a note to the manual that these modules are avaialble
Comment 2 Jan Christoph Ebersbach univentionstaff 2013-06-14 15:07:13 CEST
I've tested the installation as follows:
univention-install open-vm-tools (unmaintained has to be enabled)

The following modules are built automatically:
vmblock
vmci
vmhgfs
vmsync
vmxnet
vsock

The following modules were loaded automatically:
vmsync                 12721  0 
vmhgfs                 52452  0 
vmwgfx                 99161  0 
ttm                    57013  1 vmwgfx
drm                   183339  2 vmwgfx,ttm
vmw_balloon            12558  0 
vmci                   73350  1 vmhgfs
vmw_pvscsi             17376  4 

I'm not sure why the very important vmxnet modules isn't loaded.  The tests were performed with VMware ESXi Version 5.1.0.
Comment 3 Moritz Muehlenhoff univentionstaff 2013-06-17 06:58:56 CEST
(In reply to Jan Christoph Ebersbach from comment #2)
> I'm not sure why the very important vmxnet modules isn't loaded.  The tests
> were performed with VMware ESXi Version 5.1.0.

vmxnet is part of the standard kernel, I suppose the in-kernel module version has precedence:

jmm@vurm:~$ dpkg -L linux-image-3.2.0-4-amd64 | grep vmxnet
/lib/modules/3.2.0-4-amd64/kernel/drivers/net/vmxnet3
/lib/modules/3.2.0-4-amd64/kernel/drivers/net/vmxnet3/vmxnet3.ko
Comment 4 Moritz Muehlenhoff univentionstaff 2013-11-11 11:36:52 CET

*** This bug has been marked as a duplicate of bug 31085 ***