From: "Daniel P. Berrange" <berrange@redhat.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: James Harper <james.harper@bendigoit.com.au>,
xen-devel@lists.xensource.com, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Christian Limpach <Christian.Limpach@xensource.com>,
Masaki Kanno <kanno.masaki@jp.fujitsu.com>
Subject: Re: feature request - prevent user stupidity (eg mine)
Date: Fri, 29 Jun 2007 02:17:32 +0100 [thread overview]
Message-ID: <20070629011732.GA13857@redhat.com> (raw)
In-Reply-To: <200706290105.19180.mark.williamson@cl.cam.ac.uk>
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 -=|
next prev parent reply other threads:[~2007-06-29 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 14:10 feature request - prevent user stupidity (eg mine) James Harper
2007-06-28 2:52 ` Ian Pratt
2007-06-28 4:04 ` Masaki Kanno
2007-06-29 0:05 ` Mark Williamson
2007-06-29 1:17 ` Daniel P. Berrange [this message]
2007-06-29 1:36 ` Mark Williamson
2007-06-29 2:38 ` Masaki Kanno
2007-06-29 2:47 ` Mark Williamson
2007-06-29 8:25 ` Masaki Kanno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070629011732.GA13857@redhat.com \
--to=berrange@redhat.com \
--cc=Christian.Limpach@xensource.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=james.harper@bendigoit.com.au \
--cc=kanno.masaki@jp.fujitsu.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.