From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48756) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNLJe-0005Fb-Lh for qemu-devel@nongnu.org; Mon, 07 Nov 2011 04:16:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNLJd-0000EH-O9 for qemu-devel@nongnu.org; Mon, 07 Nov 2011 04:16:30 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNLJd-0000CU-EZ for qemu-devel@nongnu.org; Mon, 07 Nov 2011 04:16:29 -0500 Message-ID: <4EB7A22C.4000006@redhat.com> Date: Mon, 07 Nov 2011 10:17:32 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <4EB78CE9.4030305@linux.vnet.ibm.com> In-Reply-To: <4EB78CE9.4030305@linux.vnet.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] backing_file Path List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Zhi Hui Li Cc: zhihuili@cn.ibm.com, Stefan Hajnoczi cowcoww , QEMU-devel Am 07.11.2011 08:46, schrieb Zhi Hui Li: >=20 > when I trace the code of qemu-img.c=EF=BC=8C I found in the image file,= the=20 > backing_file use the relative path, I think Maybe it has some problems. >=20 > for example: >=20 > 1: qemu-img create -o backing_file=3D../xxxx aa.img 5G >=20 > 2: qemu-system-x86_64 aa.img >=20 > if you change aa.img's the path, the exec is wrong,it can't find the=20 > backing_file path, because the backing_file use the relative path, > Could we change the relative path to the absolute path? No, we can't. That would break compatibility of qemu-img create with older versions. Relative paths have well-defined semantics, they are relative to the image file. Kevin