[MIR] open-vm-tools
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libdumbnet (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
open-vm-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
zerofree (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
[Availability] open-vm-tools is currently in universe and has been in Ubuntu since Lucid. It is currently in Debian Main.
[Rationale]: open-vm-tools is the open source method of installing tools for VMware guests. VMware is a popular hypervisor for both desktop and server workloads. VMware is the defacto hyper-visor for some industries, and supporting them by adding open-vm-tools will enable Ubuntu easier.
Further, VMware is promoting the use of open-vm-tools as the preferred way for hyper-visor interaction with Linux. With the 3.9 kernel, the open-vm-tools-dkms is no longer needed for the tools to run.
Starting with Fedora 19 (released April 2013), open-vm-tools ships on CD and installs automatically on appropriate hardware.
[Security]: There have been no CVE's in the last two years, with the latest being CVE-2011-1681 and CVE-2009-2692.
[Quality assurance]:
Debian Main: https:/
Upstream Bug Tracker: http://
[UI standards]: N/A
[Dependencies]: zerofree and libdumnet will need to be promoted as well.
zerofree: e2fslibs and libc6, dependencies in main
libdumnet: libc6, dependency in main
[Background]: For the last several years, there has been the request to include open-vm-tools in the cloud-images. By having this promoted to main, it will allow us to ship with the default image; the main reason for not including this in the cloud image is due to the package provenance.
Related branches
Changed in ubuntu: | |
milestone: | none → ubuntu-13.10 |
Changed in open-vm-tools (Ubuntu): | |
assignee: | Jamie Strandboge (jdstrand) → Seth Arnold (seth-arnold) |
Changed in open-vm-tools (Ubuntu): | |
milestone: | ubuntu-13.10 → saucy-updates |
Changed in zerofree (Ubuntu): | |
status: | Incomplete → New |
Changed in open-vm-tools (Ubuntu): | |
importance: | Undecided → High |
Changed in zerofree (Ubuntu): | |
importance: | Undecided → High |
Changed in libdumbnet (Ubuntu): | |
importance: | Undecided → High |
Changed in open-vm-tools (Ubuntu): | |
milestone: | saucy-updates → ubuntu-14.04 |
Hm..
It seems this may not be necessary even as soon as 13.10 (kernel 3.11).
https:/ /lkml.org/ lkml/2012/ 11/5/502 /lkml.org/ lkml/2013/ 1/8/552
and
https:/
The vmw_vmci driver is in the Saucy (3.11) kernel tree and is configured as a kernel module.
I have heard rumor that "vmblock and vmxnet are going to be carried in the kernel for 13.10".
If we have disk and network drivers, and 'vmw_vmci', what do we get out of open-vm-tools ? Are those things necessary?