Summary: | [mkimg] Add support for Stream-Optimized (compressed) VMDK | ||
---|---|---|---|
Product: | Base System | Reporter: | Enji Cooper <ngie> |
Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | New --- | ||
Severity: | Affects Some People | CC: | benno, bms, emaste, marcel |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Enji Cooper
![]() ![]() What exactly is not working? Put differently: why is version 5 support needed or desirable? It’s impossible to make changes to mkimg without knowing what problem is being solved and thus without a way to test that the change is good. So let's collect evidence for why VMDK 5 is good to have and when we have it "overwhelmingly", adding VMDK 5 shouldn't be too hard. See also: https://www.vmware.com/support/developer/vddk/vmdk_50_technote.pdf (In reply to Marcel Moolenaar from comment #1) Sorry for not adding more context sooner. It's been a busy day. Basically, there are some features like the "Stream-Optimized Compressed" support which is a performance enhancement ("sparse VMDKs for networks"). Marcel, Totally needed. I haven't checked recently but I think pfSense may even be shipping their virtual appliance this way. I use VMDK streamOptimized to get FreeBSD VMs down to a reasonable size for archival. You may want to look at: http://sanbarrow.com/vmdk-handbook.html cheers Bruce Reset assignee as Marcel has handed in his commit bit |