From: Olaf Hering <olaf@aepfle.de>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 4/4] docs: Introduce xenstore paths for guest network address information
Date: Wed, 18 Nov 2015 13:00:15 +0100 [thread overview]
Message-ID: <20151118120015.GA12810@aepfle.de> (raw)
In-Reply-To: <1447759925-4441-5-git-send-email-paul.durrant@citrix.com>
On Tue, Nov 17, Paul Durrant wrote:
> This patch documents paths to allow a domain to advertise an interface
> name, MAC (unicast and multicast) and IP (version 4 and 6) address
> information.
How does the domU do that in practice?
With some variant of xenstore-write or with the PV vif driver?
Last time I tried to use xenstore* commands in domU it was unable to use
relative paths, which forced me to specify the domid value for the
paths. Might be a usage error on my side, or just a bug in the xenstore
commands.
Olaf
next prev parent reply other threads:[~2015-11-18 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 11:32 [PATCH v5 0/4] docs: Document xenstore paths Paul Durrant
2015-11-17 11:32 ` [PATCH v5 1/4] docs: Introduce xenstore paths for PV control features Paul Durrant
2015-11-17 11:32 ` [PATCH v5 2/4] docs: Introduce xenstore paths for PV driver information Paul Durrant
2015-11-23 11:31 ` Ian Jackson
2015-11-17 11:32 ` [PATCH v5 3/4] docs: Introduce xenstore paths for hotplug features Paul Durrant
2015-11-23 11:32 ` Ian Jackson
2015-11-17 11:32 ` [PATCH v5 4/4] docs: Introduce xenstore paths for guest network address information Paul Durrant
2015-11-18 12:00 ` Olaf Hering [this message]
2015-11-18 12:04 ` Paul Durrant
2015-11-18 12:05 ` Andrew Cooper
2015-11-23 11:32 ` Ian Jackson
2015-11-24 16:53 ` [PATCH v5 0/4] docs: Document xenstore paths 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=20151118120015.GA12810@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=paul.durrant@citrix.com \
--cc=tim@xen.org \
--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 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.