From: David Vrabel <david.vrabel@citrix.com>
To: David Scott <dave.scott@citrix.com>, xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v4] add support for libvirt-like channels
Date: Mon, 28 Jul 2014 15:22:02 +0100 [thread overview]
Message-ID: <53D65C8A.8040905@citrix.com> (raw)
In-Reply-To: <1406041520-561-1-git-send-email-dave.scott@citrix.com>
On 22/07/14 16:05, David Scott wrote:
>
> Note: I've seen a problem with some Linux console frontends which attempt
> to overwrite the read-only key 'type' (= xenconsoled|ioemu) in the frontend
> directory. [ this key is already present, it's not added by these patches ]
> Since 'type' refers to the toolstack's choice of implementation service
> (which is none of the guest's business) I think the read/only permissions
> are right. The location of the key is not ideal (it should be in the
> backend directory IMHO) but this is the case with several other keys located
> in the frontend such as 'limit' and 'tty'. I think this is a Linux frontend
> bug which should be fixed there. These patches work with Mirage VMs and
> with Linux if I workaround the permissions by giving the guest read/write
> to the 'type' key.
Which Linux frontends?
David
next prev parent reply other threads:[~2014-07-28 14:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 8:28 [PATCH v3] add support for libvirt-like channels David Scott
2014-06-23 8:28 ` [PATCH v3 1/3] docs: add a document describing the 'channels' mechanism David Scott
2014-06-23 14:38 ` Ian Jackson
2014-06-23 14:53 ` Ian Jackson
2014-06-23 17:45 ` Dave Scott
2014-06-24 10:43 ` Ian Jackson
2014-06-24 11:15 ` Dave Scott
2014-07-02 15:29 ` Ian Campbell
2014-06-23 8:29 ` [PATCH v3 2/3] libxl: add support for channels David Scott
2014-06-23 14:52 ` Ian Jackson
2014-06-23 17:43 ` Dave Scott
2014-06-24 10:41 ` Ian Jackson
2014-06-24 11:09 ` Dave Scott
2014-06-23 8:29 ` [PATCH v3 3/3] xl: " David Scott
2014-06-23 10:02 ` Wei Liu
2014-06-23 10:47 ` Dave Scott
2014-06-23 14:57 ` Ian Jackson
2014-07-02 15:33 ` Ian Campbell
2014-07-03 8:51 ` Dave Scott
2014-07-22 15:05 ` [PATCH v4] add support for libvirt-like channels David Scott
2014-07-22 15:05 ` [PATCH v4 1/3] libxl IDL: the name of a KeyedUnion descriminator need not be 'type' David Scott
2014-07-24 15:52 ` Ian Campbell
2014-07-22 15:05 ` [PATCH v4 2/3] libxl: add support for 'channels' David Scott
2014-09-10 14:41 ` Ian Campbell
2014-09-11 13:12 ` Dave Scott
2014-07-22 15:05 ` [PATCH v4 3/3] xl: " David Scott
2014-07-28 14:22 ` David Vrabel [this message]
2014-08-07 13:37 ` [PATCH v4] add support for libvirt-like channels Dave Scott
2014-08-07 14:12 ` David Vrabel
2014-08-07 14:26 ` Stefano Stabellini
2014-08-11 9:35 ` Dave Scott
2014-08-11 11:49 ` Stefano Stabellini
2014-09-10 13:07 ` Ian Campbell
2014-09-10 13:45 ` Dave Scott
2014-09-10 14:04 ` David Vrabel
2014-09-10 14:13 ` Ian Campbell
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=53D65C8A.8040905@citrix.com \
--to=david.vrabel@citrix.com \
--cc=dave.scott@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).