Bug #1373
VMware volatile disks do not work
| Status: | Closed | Start date: | 07/18/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Drivers - Auth | |||
| Target version: | Release 3.8 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 3.6 |
Description
TM SHARED mkimage needs to be separated and fix.
Also, the scripts_common mkfs_command needs to be fix for "vmdk_"
Associated revisions
Bug #1373: Volatile disks can now be created in VMware
feature #1373: Refine volatile disk generation in vmware
feature #1373: Refine volatile disk generation in vmware
(cherry picked from commit 4e3a37401d84e65116763cafbb1a11440dee7f8b)
Conflicts:
src/tm_mad/vmware/mkimagebug #1373: VMware volatile disks do not work
Bug #1373: Volatile disks can now be created in VMware
(cherry picked from commit 273005648c35616b1e368e9e2d5fb9d0e71e085e)
feature #1373: Refine volatile disk generation in vmware
bug #1373: VMware volatile disks do not work
(cherry picked from commit f4d19d9a42e6d614967a51e3c87a8fdd4ce3ee38)
History
#1
Updated by Ruben S. Montero almost 9 years ago
- Target version set to Release 3.8
#2
Updated by Tino Vázquez almost 9 years ago
- Category set to Drivers - Auth
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
Updated repo and documentation