WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Exporting a PCI Device

To: Joris Dobbelsteen <Joris@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Exporting a PCI Device
From: Jan Kalcic <jandot@xxxxxxxxxxxxxx>
Date: Tue, 19 Feb 2008 14:30:20 +0100
Cc: deshantm@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Feb 2008 05:29:16 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=/hujBjYS7W3Qabt9DsSeUscKbcJY0T76MJPZIbdjvxM=; b=U9HJ5StOqBjURhtePItQC8XZfcAsjvAxbXiZqLS+COQVsi9+YhZzp9MnkBNPXRBrzC09RuiKMVMyaz4q0chqd4ItQ/s+hB4yAxIFQcaZGxvdOvdUg8MQ/PnJ8AnWBdB9SYcphZDu68WeCxtPbc5wFn0P9gycod00iZSr3GeDvCA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=vMup4DHCpZJjG12ww+6RwiSJlHxM/T7W2wEbOtm3bF+gEmM7lGQwEKp9iD0S1Sk1EvZAe5TPEGuTv58lXHDxPoOZXhKisPzoM0VQ6MEvvq5Od4iAUIEoVDXWP4gfax3+00ysjaXoH66tbG/0TGe/xMy5XIMkah58Gq5kp3xD8qc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <E4953B65D9E5054AA6C227B410C56AA9C379@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <47B8C482.5050600@xxxxxxxxxxxxxx><1e16a9ed0802171801n591a4949r4ee5e362c2f80f05@xxxxxxxxxxxxxx> <47B965A9.4040300@xxxxxxxxxxxxxx> <E4953B65D9E5054AA6C227B410C56AA9C379@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20070801)
>> Hi Todd,
>>
>> the PCI device which I would need to "share" is the fibre 
>> channel card connected to two different storage, on of this is 
>> the VMs repository which has to be visible to dom0 and the 
>> other one is the data storage for VMs which, obviously, has to 
>> be visibile to VMs. So the solution would be using two 
>> different fibre channel cards, right?
>>     
>
> What I would do is make all storage available to the dom0 and use
> regular methods to export it to the domU.
> In other words: treat dom0 as a very fancy piece of hardware that's
> between your kernel and the fibre-channel attached storage. For generic
> solutions the Virtual Block Device should be fast enough, otherwise you
> should probably consider a separate server, dedicated to that single
> task.
>
>   
Exporting the device to domU as a Physical Block Device, let's suppose
/dev/sda, when I migrate the VMs to another server I have the problem
that device has to be re-attached, don't I? Or if the same device still
exists on the other server the VMs has that device still attached?

Thanks,
Jan


> I don't know if you are going to loose any fibre-channel advantages, but
> I figure you also reduce administrative complexity to dom0's only.
>
> - Joris
>
>
>   


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>