From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ram Pai Subject: Re: qcow2 relative paths Date: Thu, 16 Jul 2009 00:51:22 -0700 Message-ID: <1247730682.14246.144.camel@localhost> References: <1246511321.6429.31.camel@localhost> <4A4C754D.10109@redhat.com> <4A4CAD86.9020607@us.ibm.com> <4A4CB39F.5070506@redhat.com> <1247041831.6297.12.camel@localhost> <1247644283.14246.3.camel@localhost> <4A5DA1B7.5000204@siemens.com> <1247677395.14246.38.camel@localhost> <20090715182025.GC3056@shareable.org> <1247683475.14246.90.camel@localhost> <20090715210459.GJ3056@shareable.org> <1247711285.14246.116.camel@localhost> <4A5ED906.500@redhat.com> Reply-To: linuxram@us.ibm.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Jamie Lokier , Jan Kiszka , Anthony Liguori , qemu-devel@nongnu.org, kvm-devel To: Kevin Wolf Return-path: Received: from e36.co.us.ibm.com ([32.97.110.154]:57882 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752637AbZGPHvZ (ORCPT ); Thu, 16 Jul 2009 03:51:25 -0400 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e36.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n6G7np4F026550 for ; Thu, 16 Jul 2009 01:49:51 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n6G7pPZp216808 for ; Thu, 16 Jul 2009 01:51:25 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n6G7pO5O005343 for ; Thu, 16 Jul 2009 01:51:25 -0600 In-Reply-To: <4A5ED906.500@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2009-07-16 at 09:38 +0200, Kevin Wolf wrote: > Ram Pai schrieb: > > On Wed, 2009-07-15 at 22:04 +0100, Jamie Lokier wrote: > >> What an unhelpful error message... There isn't even a way to find out > >> the backing file path which the tool is looking for. > > > > Ok. i have introduced a message towards the effect, in the next revision > > of the patch. Hope that will make things a little easier. > > Please don't include it here - one patch for one problem. I agree that > this error message isn't exactly helpful, but it must be fixed in a > different patch. Oops. I already sent out the patch containing that message. Should we freeze this patch and commit it, if there are no fundamental issues? I will provide subsequent patches to any bugs uncovered because of this patch. RP > > Kevin