From: Michael Vrable <mvrable@cs.ucsd.edu>
To: xen-devel@lists.xensource.com
Subject: Xenstore Recovery?
Date: Thu, 3 Nov 2005 15:40:40 +0000 [thread overview]
Message-ID: <20051103154040.GA13320@vrable.net> (raw)
There has been talk of driver recovery within Xen domains if the backend
goes away unexpectedly. Has anyone given much thought to how to perform
recovery if a domain's connection to _xenstore_ goes away?
It seems a trickier problem. There's no existing way to signal a
domain that this has happened--we can't simply have the new xenstore
daemon write data out on the xenstore channels, since there are no clear
message boundaries. The xenbus code in Linux doesn't look like it's
designed to deal with failures in xenstore. Also, watches on the store
seem like hard state within xenstore, that domains can't be easily told
to rebuild.
It looks like the suspend/resume code in domains will handle
reconnecting to xenstore, but that only works if the domain is properly
notified ahead of time.
I'm mostly just curious whether this is in the xenstore/xenbus design at
all, a case that is explicitly not handled for complexity reasons, or
something else.
--Michael Vrable
reply other threads:[~2005-11-03 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051103154040.GA13320@vrable.net \
--to=mvrable@cs.ucsd.edu \
--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 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.