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-devel

Re: [Xen-devel] feature request - prevent user stupidity (eg mine)

To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] feature request - prevent user stupidity (eg mine)
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Fri, 29 Jun 2007 02:17:32 +0100
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxxx>, Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Delivery-date: Thu, 28 Jun 2007 18:15:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200706290105.19180.mark.williamson@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01166BB2@trantor> <8A87A9A84C201449A0C56B728ACF491E25FC8B@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <200706290105.19180.mark.williamson@xxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Fri, Jun 29, 2007 at 01:05:18AM +0100, Mark Williamson wrote:
> > > Given that there is almost no way you would ever want to publish the
> > > same block device to the same virtual domain more than once, would
> >
> > there
> >
> > > be any value in flagging that as an error when you try and start the
> > > domain?
> >
> > I'm surprised that the existing block device safety checks don't pick up
> > on this, but I guess they're run before the guest is started rather than
> > before each virtual disk is attached.
> 
> Looks like the hotplug scripts do contain the checking logic, and it does 
> check each device at a time, but it explicitly ignores if the same VM already 
> has access to a device.  Maybe checking for duplicate exports here would be 
> too racey, since I guess the hotplug scripts are not run in any particular 
> order...

Well duplicate devices in the same VM could be fairly easily checked by XenD
itself before it gets anywhere near creating the VM or doing device hotplug.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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