Re: [Qemu-devel] vmdk: improve streamOptimized vmdk support

[devsk]

Fam,

Was this work ever completed?

Thanks,
Sunil



On Monday, April 20, 2015 11:10 PM, Fam Zheng <address@hidden> wrote:
On Fri, 04/17 18:25, devsk wrote:
> Fam: Any updates on this?

Hi, I'm still working on the patchset. Will send to the list once it's done.


Fam

> Thanks 
> 
> 
>      On Tuesday, March 3, 2015 12:54 AM, Fam Zheng <address@hidden> wrote:
>    
> 
>  On Tue, 03/03 09:36, Milos Vyletel wrote:
> > On Sun, Mar 1, 2015 at 9:50 PM, Sunil Kumar <address@hidden> wrote:
> > > Any update on this Milos?
> > >
> > > Thanks.
> > >
> > 
> > I did look at this yesterday and unfortunately it will be harder to
> > adapt to new head as previously thought. Since the addition of
> > next_cluster_sector (which is one of last Fam's comments in v3)
> > writing to vmdk's revolve around sectors instead of offset and that
> > does not work very well with streamOptimized format.
> > 
> > I'm sorry but I don't think I'll have enough time to spend in near
> > future to get this properly working. Plus I no longer have the test
> > environment since I've changed jobs in the meantime.
> 
> I'll see if I can roll some patches later. :)
> 
> Sunil, do you have an environment to run the tests later?
> 
> Fam
> 
> > 
> > Milos
> > 
> > >
> > >
> > > On Monday, February 23, 2015 5:50 AM, Milos Vyletel <address@hidden> 
> > > wrote:
> > > On Mon, Feb 23, 2015 at 11:57 AM, Kevin Wolf <address@hidden> wrote:
> > >> Am 23.02.2015 um 09:10 hat Markus Armbruster geschrieben:
> > >>> Perhaps Fam (cc'ed) can help you.
> > >>>
> > >>> Sunil Kumar <address@hidden> writes:
> > >>>
> > >>> [...]
> > >>> > Hi,
> > >>> >
> > >>> > I ran into an issue where the OVA created from the VMDK file created
> > >>> > by qemu-img is rejected by vSphere with a message like "Not a
> > >>> > supported disk format (sparse VMDK too old)". I was looking through
> > >>> > the archives and found this:
> > >>> >
> > >>> > http://lists.gnu.org/archive/html/qemu-devel/2014-08/msg01028.html
> > >>> >
> > >>> > That's exactly my issue and the patch will resolve it. But this patch
> > >>> > has not been merged yet and it does not apply on top of 2.2.0
> > >>> > cleanly. Any ideas what happened to the patch there?
> > >>
> > >> Fam had review comments in the mailing list thread that you refer to
> > >> above, so it seems we're still waiting for a v4 patch by Milos that
> > >> addresses the issues Fam found.
> > >>
> > >> Milos, are you still interested in this patch or should someone else
> > >> pick it up?
> > >>
> > >
> > > Oh, shame on me. I've completely forgot about this. I did quickly
> > > ported the patch to current upstream and did some basic testing.
> > > Something is little bit off so I will have to figure that out as well
> > > as look at Fam's comments and I will post v4 asap. I hope to find some
> > > time to look at this properly this week.
> > >
> > >
> > > Milos
> 
> 
> 
>