From: Wei Liu <wei.liu2@citrix.com>
To: Pavlo Suikov <pavlo.suikov@globallogic.com>
Cc: wei.liu2@citrix.com,
Iurii Mykhalskyi <iurii.mykhalskyi@globallogic.com>,
Andrii Anisov <andrii.anisov@globallogic.com>,
xen-devel@lists.xen.org
Subject: Re: Hotplugged devices in Xen 4.5 and domain reboot
Date: Tue, 1 Dec 2015 14:02:08 +0000 [thread overview]
Message-ID: <20151201140208.GA25722@citrix.com> (raw)
In-Reply-To: <CAE4oM6w8kh8JCRrduPFcB9bhABpQ9aT7acu5jyP-hQnCUzaOWA@mail.gmail.com>
On Tue, Dec 01, 2015 at 03:24:13PM +0200, Pavlo Suikov wrote:
> Hi,
>
> got a question regarding hotplugged devices in Xen 4.5. What we currently
> have is Xen 4.5, Linux in Dom0 and DomD and Android in DomU. All the
> devices are configured via domain config, so they are initialized on domain
> startup: libxl reads config, sets up xenstore branches and fills them for
> driver back ends and front ends; front ends monitor these branches and fill
> in their specific data once connection is established. On DomU reboot,
> config is being re-read and all the devices are started again in the same
> manner.
>
> Problem is we don't really know what to do with hotplugged devices. When
> such a device appears in DomU during runtime, we set up all the xenstore
> insformation on the fly, but it doesn't go to persistent domain
> configuration; so when DomU reboot comes, they are not set up again as they
> should. All the solutions we are considering look like dirty hacks (e.g.
> making separate branch in xenstore for hotplugged devices, reading it on
> domain start in the same way domain config is parsed, and copying data to
> corresponding xenstore domain branches). Are there any existing ways to
> handle these?
>
Do you have the exact runes you use to do the hotplug? How do you reboot
your DomU? What does /var/lib/xen/userdata-d.$DOMID-$UUID.libxl-json
look like before and after hotplug?
Wei.
> Suikov Pavlo
> GlobalLogic
> P +x.xxx.xxx.xxxx M +38.066.667.1296 S psujkov
> www.globallogic.com
> <http://www.globallogic.com/>
> http://www.globallogic.com/email_disclaimer.txt
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-01 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 13:24 Hotplugged devices in Xen 4.5 and domain reboot Pavlo Suikov
2015-12-01 14:02 ` Wei Liu [this message]
2015-12-01 14:58 ` Iurii Mykhalskyi
2015-12-01 15:29 ` Wei Liu
2015-12-01 15:41 ` Ian Campbell
2015-12-01 16:48 ` Iurii Mykhalskyi
2015-12-01 17:05 ` Ian Campbell
2015-12-01 21:03 ` Doug Goldstein
2015-12-02 9:31 ` Ian Campbell
2015-12-01 17:21 ` Wei Liu
2015-12-02 9:28 ` Ian Campbell
2015-12-01 17:52 ` Roger Pau Monné
2015-12-02 9:30 ` Ian Campbell
2015-12-01 15:56 ` Roger Pau Monné
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=20151201140208.GA25722@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=iurii.mykhalskyi@globallogic.com \
--cc=pavlo.suikov@globallogic.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.