From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Is PVH a blocker?
Date: Mon, 16 Dec 2013 10:10:41 -0500 [thread overview]
Message-ID: <20131216151041.GA14186@phenom.dumpdata.com> (raw)
In-Reply-To: <1387191257.20076.70.camel@kazak.uk.xensource.com>
On Mon, Dec 16, 2013 at 10:54:17AM +0000, Ian Campbell wrote:
> On Fri, 2013-12-13 at 14:43 -0500, Konrad Rzeszutek Wilk wrote:
> > > == Open ==
> > >
> > Also, xl as opposed to xend, allows me to share a disk without
> > any fanfare.
> >
> > Meaning I can do this:
> >
> > xl block-attach phy:/dev/sda latest1 xvda w
> > xl block-attach phy:/dev/sda latest2 xvda w
> >
> > while if I had used 'xend' I had to also append the '!' parameter
> > to denote it as 'shared'.
>
> Do you find that restriction to be valuable in practice?
It protects me from doing silly mistakes.
>
> Was it ever reliable? How did it cope with /dev/mapper/FOO-BAR
> vs /dev/FOO/BAR and other similar aliases (/dev/cdrom etc)?
I am not sure - but it did work across device mapper.
>
> We could certainly cause xl to swallow the '!' for compatibility but is
> the feature itself necessary?
Not for Xen 4.4.
>
> I have a feeling this is mostly implemented by checks in the block
> scripts rather than the toolstack itself, perhaps libxl drives them a
> bit differently.
I can do some investigation for this. After New Year though.
>
> Ian.
>
next prev parent reply other threads:[~2013-12-16 15:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 19:21 Xen 4.4 development update: Is PVH a blocker? George Dunlap
2013-12-13 19:39 ` Konrad Rzeszutek Wilk
2013-12-13 20:55 ` Sander Eikelenboom
2013-12-16 15:09 ` Konrad Rzeszutek Wilk
2013-12-16 17:24 ` Sander Eikelenboom
2013-12-16 17:46 ` Konrad Rzeszutek Wilk
2013-12-16 17:59 ` Sander Eikelenboom
2013-12-16 19:34 ` Konrad Rzeszutek Wilk
2013-12-16 19:46 ` Sander Eikelenboom
2013-12-17 14:35 ` Konrad Rzeszutek Wilk
2013-12-17 15:03 ` Sander Eikelenboom
2013-12-17 21:35 ` Konrad Rzeszutek Wilk
2013-12-17 21:52 ` Sander Eikelenboom
2013-12-17 15:04 ` Anthony Liguori
2013-12-17 15:18 ` Konrad Rzeszutek Wilk
2013-12-16 10:51 ` Ian Campbell
2013-12-16 15:12 ` Konrad Rzeszutek Wilk
2013-12-16 15:24 ` Konrad Rzeszutek Wilk
2013-12-16 15:43 ` Ian Campbell
2013-12-13 19:43 ` Konrad Rzeszutek Wilk
2013-12-16 10:50 ` George Dunlap
2013-12-16 10:54 ` Ian Campbell
2013-12-16 15:10 ` Konrad Rzeszutek Wilk [this message]
2013-12-19 14:06 ` Ian Campbell
2013-12-19 14:15 ` Processed: " xen
2013-12-16 8:47 ` Jan Beulich
2013-12-16 23:45 ` Mukesh Rathor
2013-12-17 8:25 ` Jan Beulich
2013-12-17 11:58 ` Tim Deegan
2013-12-17 14:13 ` George Dunlap
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=20131216151041.GA14186@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.