From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: Handling CPU unplug failure
Date: Thu, 4 Feb 2016 11:59:54 -0500 [thread overview]
Message-ID: <56B3838A.5060203@oracle.com> (raw)
While playing with CPU hotplug I noticed that if a guest fails to unplug
a VCPU the toolstack will mark VCPU's availability in xenstore as
"offline" even though that VCPU is still running in the guest.
It's easy to see this by doing 'xl vcpu-set <domid> 0', which is
presumably not a realistic scenario but we can get into the same
situation if, for example, the guest is configured without hotplug
support or some operations during unplug fail.
Should we at least document this behavior (that 'availability' entry in
xenstore is unreliable) somewhere?
-boris
reply other threads:[~2016-02-04 16:59 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=56B3838A.5060203@oracle.com \
--to=boris.ostrovsky@oracle.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 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).