From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Mihir Nanavati <mihirn@cs.ubc.ca>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: libxl: Allow specification of backend domains for vifs
Date: Tue, 10 Aug 2010 22:28:14 +0100 [thread overview]
Message-ID: <4C61C46E.4080503@eu.citrix.com> (raw)
In-Reply-To: <AANLkTimyZb67qcRWcvEacufHPc6DsH2J0fQF_xaXpF_a@mail.gmail.com>
On 10/08/10 22:13, Mihir Nanavati wrote:
> It works fine with stub domains. I haven't really played around with
> it on regular HVM guests, but I suspect it might cause some issues.
> Will give it a spin tomorrow.
There's nothing different in this case. exposing the backend domid for
hvm guest is a perfectly valid thing to do.
--
Vincent
prev parent reply other threads:[~2010-08-10 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 14:28 libxl: Allow specification of backend domains for vifs Mihir Nanavati
2010-08-09 16:42 ` Stefano Stabellini
2010-08-10 16:44 ` Ian Jackson
2010-08-10 21:13 ` Mihir Nanavati
2010-08-10 21:28 ` Vincent Hanquez [this message]
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=4C61C46E.4080503@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=mihirn@cs.ubc.ca \
--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 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).