Bug #254
VMware server properties vary from those in ESXi
| Status: | Closed | Start date: | 06/09/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: | OpenNebula 3.0 |
Description
The ideal solution would be to find its equivalents, but at the very least we should try-catch them so it doesn't fail and, maybe, provide defaults.
Associated revisions
History
#1
Updated by Tino Vázquez about 11 years ago
It looks like there may be subtle variations between VMware server versions. Xavier reported (http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002167.html) an exception from "hardware.memorySize" property retrieving, while (http://lists.opennebula.org/pipermail/users-opennebula.org/2010-June/002164.html) claims to have the IM working with VMware server 2 as well.
#2
Updated by Ruben S. Montero over 9 years ago
- Status changed from New to Closed
- Resolution set to worksforme
- Affected Versions OpenNebula 3.0 added
This does not apply for the new VMware drivers. Closing...