xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Olsowski <andreas.olsowski@leuphana.de>
To: xen-devel@lists.xensource.com
Subject: pv guests die after failed migration
Date: Tue, 20 Sep 2011 11:42:45 +0200	[thread overview]
Message-ID: <4E786015.80603@leuphana.de> (raw)


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

When xm failed to do a live migration the system was resumed on the 
sending host.
Xl does not do that it TRIES to, but just crashes the guest:
kernel BUG at drivers/xen/events.c:1466!
(In this example the target host didnt have the logical volume activated.)

Now that cant be right.
Imho xl should do some checking if the target is a viable migration 
target (are the disks and vifs there, is there enough memory available) 
and preserve a safe state on the sender until the guest has properly 
started on the receiver.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]

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

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

             reply	other threads:[~2011-09-20  9:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  9:42 Andreas Olsowski [this message]
2011-09-20 19:27 ` pv guests die after failed migration Ian Campbell
2011-09-23  7:39   ` Andreas Olsowski
2011-09-23  7:47     ` Ian Campbell
2011-09-23  9:15       ` Andreas Olsowski
2011-09-28 15:52         ` Ian Campbell
2011-10-15  1:18           ` Andreas Olsowski
2011-10-15  5:44             ` Ian Campbell
2011-10-15 10:35               ` Andreas Olsowski
2011-10-15 15:12                 ` Ian Campbell
2011-12-29 14:08                   ` Andreas Olsowski

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=4E786015.80603@leuphana.de \
    --to=andreas.olsowski@leuphana.de \
    --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).