From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjAxt-0007Ey-Ge for qemu-devel@nongnu.org; Fri, 17 Apr 2015 14:26:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjAxp-0005wd-EH for qemu-devel@nongnu.org; Fri, 17 Apr 2015 14:26:09 -0400 Received: from nm11-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.104]:60119) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjAxp-0005w2-7X for qemu-devel@nongnu.org; Fri, 17 Apr 2015 14:26:05 -0400 Date: Fri, 17 Apr 2015 18:25:59 +0000 (UTC) From: devsk Message-ID: <214818157.4829998.1429295159595.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <20150303085332.GB29800@ad.nay.redhat.com> References: <20150303085332.GB29800@ad.nay.redhat.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4829995_258448177.1429295159589" Subject: Re: [Qemu-devel] vmdk: improve streamOptimized vmdk support Reply-To: devsk List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng , Milos Vyletel Cc: Kevin Wolf , qemu-devel , Markus Armbruster ------=_Part_4829995_258448177.1429295159589 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Fam: Any updates on this? Thanks On Tuesday, March 3, 2015 12:54 AM, Fam Zheng wrote: On Tue, 03/03 09:36, Milos Vyletel wrote: > On Sun, Mar 1, 2015 at 9:50 PM, Sunil Kumar 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 wrote: > > On Mon, Feb 23, 2015 at 11:57 AM, Kevin Wolf wrote: > >> Am 23.02.2015 um 09:10 hat Markus Armbruster geschrieben: > >>> Perhaps Fam (cc'ed) can help you. > >>> > >>> Sunil Kumar 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 ------=_Part_4829995_258448177.1429295159589 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Fam: Any updates on this?

Thanks



<= div style=3D"font-family: lucida console, sans-serif; font-size: 13px;" id= =3D"yui_3_16_0_1_1429040935899_30420">
On Tuesday, March 3, 2015 12:54 AM, Fam Zhe= ng <famz@redhat.com> wrote:


On Tue, 03/03 = 09:36, Milos Vyletel wrote:
> On Sun, Mar 1, 2015 at 9= :50 PM, Sunil Kumar <internet_everyone= @yahoo.com> wrote:
> > Any update on this Mi= los?
> >
> > 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 commen= ts in v3)
> writing to vmdk's revolve around sectors i= nstead of offset and that
> does not work very well wi= th 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 t= he test
> environment since I've changed jobs in the m= eantime.

I'll see if I can roll some p= atches later. :)

Sunil, do you have an= environment to run the tests later?


Fam

>
> Milos
>
> >
> >
> = > On Monday, February 23, 2015 5:50 AM, Milos Vyletel <milos.vyletel@gmail.com> wrote:
> &= gt; On Mon, Feb 23, 2015 at 11:57 AM, Kevin Wolf <kwolf@redh= at.com> wrote:
> >> Am 23.02.2015 um 09:1= 0 hat Markus Armbruster geschrieben:
> >>> Pe= rhaps Fam (cc'ed) can help you.
> >>>
> >>> Sunil Kumar <internet_everyone@yahoo.com> writes:
> >= >>
> >>> [...]
> &= gt;>> > 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
> &g= t;>> > supported disk format (sparse VMDK too old)". I was looking= through
> >>> > the archives and found th= is:
> >>> >
> >>= ;> > http://lists.gnu.org/archiv= e/html/qemu-devel/2014-08/msg01028.html
> >>= > >
> >>> > That's exactly my issue = and the patch will resolve it. But this patch
> >&g= t;> > 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?
> >>
> &g= t;> 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 iss= ues Fam found.
> >>
> >&= gt; Milos, are you still interested in this patch or should someone else> >> pick it up?
> >>> >
> > Oh, shame on me. I'v= e completely forgot about this. I did quickly
> > p= orted 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 wil= l post v4 asap. I hope to find some
> > time to loo= k at this properly this week.
> >
> >
> > Milos



------=_Part_4829995_258448177.1429295159589--