From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36423) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R4BWg-00005w-Lg for qemu-devel@nongnu.org; Thu, 15 Sep 2011 08:58:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R4BWf-0006jB-6N for qemu-devel@nongnu.org; Thu, 15 Sep 2011 08:58:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2983) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R4BWe-0006ie-UX for qemu-devel@nongnu.org; Thu, 15 Sep 2011 08:58:45 -0400 Message-ID: <4E71F67B.3@redhat.com> Date: Thu, 15 Sep 2011 14:58:35 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1315628610-28222-1-git-send-email-ronniesahlberg@gmail.com> <1315628610-28222-2-git-send-email-ronniesahlberg@gmail.com> <20110912091408.GA3465@stefanha-thinkpad.localdomain> <4E71956B.6030902@redhat.com> <4E71BBE3.5000207@redhat.com> <4E71C146.6070406@redhat.com> <4E71E4B2.9060304@redhat.com> <4E71E854.10302@redhat.com> <1316090109.29180.43.camel@dhcp-1-120.tlv.redhat.com> In-Reply-To: <1316090109.29180.43.camel@dhcp-1-120.tlv.redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] This patch adds a new block driver : iSCSI List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Orit Wasserman Cc: kwolf@redhat.com, Stefan Hajnoczi , dlaor@redhat.com, qemu-devel@nongnu.org, fujita.tomonori@lab.ntt.co.jp, Ronnie Sahlberg , hch@lst.de On 09/15/2011 02:34 PM, Orit Wasserman wrote: >> > Then you need an iSCSI*target* that understands qcow2, like qemu-nbd >> > but for iSCSI... that's exactly the thing you were worried about >> > implementing. > > Not really , this is just part of the target configuration. > For each file in the chain we create a lun in the target that is backed > by the file and we number the luns in chronological order (base is lun > 1) . you can look at a tgtd configuration here > http://wiki.qemu.org/Features/LiveBlockMigration#Example_single_base_master_image. That's surely a weird way to use iSCSI. :) It's clever, but I would call that shared storage, since you need to share the details of the snapshot chain between the source and destination, down to the file names. We need a more precise nomenclature. Paolo