From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52469) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSArW-00055z-9J for qemu-devel@nongnu.org; Sun, 01 Mar 2015 15:53:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSArS-0002Er-9F for qemu-devel@nongnu.org; Sun, 01 Mar 2015 15:53:18 -0500 Received: from nm43-vm0.bullet.mail.ne1.yahoo.com ([98.138.120.224]:60160) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSArR-0002El-Vl for qemu-devel@nongnu.org; Sun, 01 Mar 2015 15:53:14 -0500 Date: Sun, 1 Mar 2015 20:50:05 +0000 (UTC) From: Sunil Kumar Message-ID: <290178097.682155.1425243005241.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] vmdk: improve streamOptimized vmdk support Reply-To: Sunil Kumar List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Milos Vyletel , Kevin Wolf Cc: Fam Zheng , Markus Armbruster , qemu-devel Any update on this Milos? Thanks. 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