From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan de Konink Subject: Re: Almost working iSCSI booting, need advice Date: Sat, 23 Aug 2008 00:16:07 +0200 Message-ID: <48AF3AA7.6010409@xs4all.nl> References: <8061073.65491219442474965.JavaMail.root@bos-dom-zbox3.bos.lycos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8061073.65491219442474965.JavaMail.root@bos-dom-zbox3.bos.lycos.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: jpranevich@kniggit.net Cc: Stephan Seitz , xen-devel List-Id: xen-devel@lists.xenproject.org jpranevich@kniggit.net schreef: > This is the code that I've mimiced. Here, > "BOOTLOADER_LOOPBACK_DEVICE" is always "/dev/xvdp". But, in the case > of 'tap' devices, it gets destroyed later. (I don't want to destroy > it later since the iSCSI mount needs to be kept around.) You are working at the wrong layer... there are block-scripts... don't edit the xend python stuff! And you understand that /dev/xvdp is for INSIDE the host? But there is some other news... with Xen 3.3 pvSCSI is possible. Thus it might be better to pass along a scsi generic device instead of a disk. Stefan