All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sunil Kumar <internet_everyone@yahoo.com>
To: Milos Vyletel <milos.vyletel@gmail.com>, Kevin Wolf <kwolf@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vmdk: improve streamOptimized vmdk support
Date: Sun, 1 Mar 2015 20:50:05 +0000 (UTC)	[thread overview]
Message-ID: <290178097.682155.1425243005241.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <CAAFXRd2QELgx73jjz9sh+ranP=eBjS6V01JHoUvEA=YZT6ZwqA@mail.gmail.com>

Any update on this Milos?

Thanks.



On Monday, February 23, 2015 5:50 AM, Milos Vyletel <milos.vyletel@gmail.com> wrote:
On Mon, Feb 23, 2015 at 11:57 AM, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 23.02.2015 um 09:10 hat Markus Armbruster geschrieben:
>> Perhaps Fam (cc'ed) can help you.
>>
>> Sunil Kumar <internet_everyone@yahoo.com> 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

  reply	other threads:[~2015-03-01 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22  1:00 [Qemu-devel] (no subject) Sunil Kumar
2015-02-22  1:02 ` [Qemu-devel] vmdk: improve streamOptimized vmdk support Sunil Kumar
2015-02-23  8:10   ` Markus Armbruster
2015-02-23 10:57     ` Kevin Wolf
2015-02-23 13:50       ` Milos Vyletel
2015-03-01 20:50         ` Sunil Kumar [this message]
2015-03-03  8:36           ` Milos Vyletel
2015-03-03  8:53             ` Fam Zheng
2015-03-04 21:44               ` Sunil Kumar
2015-04-17 18:25               ` devsk
2015-04-21  6:09                 ` Fam Zheng
2016-04-09 14:19                   ` devsk
2016-04-19 13:03                     ` Fam Zheng
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21 23:59 Sunil Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=290178097.682155.1425243005241.JavaMail.yahoo@mail.yahoo.com \
    --to=internet_everyone@yahoo.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=milos.vyletel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.