From: Anthony Liguori <aliguori@us.ibm.com>
To: John Byrne <john.l.byrne@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Error checking on migration?
Date: Mon, 05 Jun 2006 21:50:06 -0500 [thread overview]
Message-ID: <4484ED5E.6070503@us.ibm.com> (raw)
In-Reply-To: <4484DFF7.5050601@hp.com>
John Byrne wrote:
>
> I've noticed that migration doesn't fail if the VM cannot access the
> disk image on the new host. (xen-unstable 10273) The VM ends up on
> the new host and hangs when it does a disk access. This is a somewhat
> evil behavior.
You could add some basic sanity checking in XendRestore.py:restore()
before xd.restore_() is invoked. A consequence of doing device setup
through scripts is that the only proper way to know if a device creation
will succeed is by actually creating it. It's further complicated by
the race condition that results by doing the checking before actually
grabbing the devices (what if another migration is in progress that
happens to use the same devices).
At any rate, having some sort of error checking is probably better than
having none at all.
Regards,
Anthony Liguori
>
> Does anyone have a fix for this in-hand, somewhere? If not, any advice
> where to look to fix the problem?
>
> Thanks,
>
> John Byrne
>
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-06 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 1:52 Error checking on migration? John Byrne
2006-06-06 2:50 ` Anthony Liguori [this message]
2006-06-06 11:02 ` Ewan Mellor
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=4484ED5E.6070503@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=john.l.byrne@hp.com \
--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.