> It's a naughty thing to do but we could simply pick a new constant and > support LZO as an incompatible option. The file is then no longer compatible > with existing vmdk tools but at least we then have a choice of using > compatible deflate or the LZO extension.
To be 100% incompatible to existing tools? That would remove any advantage. > VMDK already has 99% of what you need and we already have a bunch of > code to handle this format. This seems like a good opportunity to flesh out > VMDK support and avoid reinventing the wheel. Using 'probably' patented software is a bad idea - I will not go that way.
