failure to start message should be explicit about non-VMware hypervisor
Bug #1289564 reported by
Ben Howard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| open-vm-tools (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
open-vm-tools emits "Not starting as we're not running in a vm" when it fails to start on due to not being on VMware. The message should be specific, i.e. "open-vm-tools: not starting as this is not a VMware VM"
| Changed in open-vm-tools (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in open-vm-tools (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package open-vm-tools - 2:9.4.0-
---------------
open-vm-tools (2:9.4.
* Change startup message failure to state the reason why open-vm-tools
does not start on non-VMware hypervisors (LP: #1289564).
-- Ben Howard <email address hidden> Fri, 07 Mar 2014 17:21:03 -0700