From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: xl create should refuse to share block devices RW between domains
Date: Mon, 26 Jul 2010 17:36:22 -0700 [thread overview]
Message-ID: <4C4E2A06.9070604@goop.org> (raw)
When creating a domain, "xl create" should fail if a block device is
shared RW between domains, like xm create does.
I'm not sure how this would be implemented. Search xenstore for
references to the device when setting up a domain?
J
next reply other threads:[~2010-07-27 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 0:36 Jeremy Fitzhardinge [this message]
2010-07-27 8:18 ` xl create should refuse to share block devices RW between domains Ian Campbell
2010-07-27 10:40 ` Stefano Stabellini
2010-07-27 10:55 ` Ian Campbell
2010-07-27 15:18 ` Jeremy Fitzhardinge
2010-07-27 15:47 ` Ian Campbell
2010-07-27 18:17 ` Daniel Stodden
2010-07-27 15:17 ` Ian Jackson
2010-07-27 15:23 ` Jeremy Fitzhardinge
2010-07-27 15:33 ` Ian Jackson
2010-07-27 15:50 ` Ian Campbell
2010-07-27 16:01 ` Jeremy Fitzhardinge
2010-07-27 16:07 ` Stefano Stabellini
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=4C4E2A06.9070604@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=stefano.stabellini@eu.citrix.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.