xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>, xen devel <xen-devel@lists.xen.org>
Subject: Re: what will happen for a floated vcpu?
Date: Thu, 31 Mar 2016 18:00:44 +0200	[thread overview]
Message-ID: <1459440044.5082.178.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB130852457DCB9308C516D54D8D870@HE1PR05MB1308.eurprd05.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]

On Tue, 2016-03-29 at 20:06 +0000, tutu sky wrote:
> Hi,
> I need to know what happens while a cpu which is running a vcpu,
> suddenly crash or down? I mean have xen any plane for such a
> situation?
>
I don't understand the question: what does it mean for a cpu to
"suddenly crash"?

It's typically software that crashes. Hardware failures are possible,
of course, but whether they are recoverable or not, and whether there
are plans/code to do that, would depend on what failure we're actually
talking about.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-03-31 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 20:06 what will happen for a floated vcpu? tutu sky
2016-03-31 16:00 ` Dario Faggioli [this message]
2016-03-31 16:27   ` tutu sky
2016-04-01 14:18     ` Dario Faggioli

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=1459440044.5082.178.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ooohooo_u@hotmail.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).