From: Uri Lublin <uril@qumranet.com>
To: Chen_PeterK@emc.com
Cc: kvm@vger.kernel.org, Uri Lublin <uril@qumranet.com>
Subject: Re: Bug Report: Live Migration - could someone help me
Date: Sun, 06 Jul 2008 13:06:07 +0300 [thread overview]
Message-ID: <4870990F.7000400@qumranet.com> (raw)
In-Reply-To: <CFB9D4FF64E8FA48A3E9B113C4700D0E60AA4B@CORPUSMX70B.corp.emc.com>
From: kvm-owner@vger.kernel.org on behalf of Chen_PeterK@emc.com
>I am trying the live migration function, but meet some problem: The
>guest OS was blocked (or maybe dead) on target machine.
>
>The symptom is I can not interact with the migrated OS after operation.
>I believe it's dead, because the mouse can't response and I can't not
>ping it.
>
>Environment:
>1. The image was created in format raw or qcow2 (both have been tried)
>2. Migrated with TCP or SSH (both have been tried)
>3. Host OS: Fedora 9 (2.6.25) 64bit OS
>4. Host hardware: support Intel - VT (64bit CPU)
>5. Guest OS: Ubuntu 8.04 32bit, Windows XP, Windows 2003 (all have been tried)
>6. Shared story is NFS attached.
>
What is the command line you are using to start qemu/kvm on the source host and
destination host ?
What is the output of "info migration" monitor command sent to qemu/kvm running
on the source ?
>
>The strange is I can do successful live migration using my friend's
>image (WinXP raw format) and Tiny Linux (which don't need to install).
>I think may be I do something wrong.
Is there any significant difference between your XP guest and your friend's
guest (mainly different emulated devices) ?
What is the command line with your friend's image ?
Regards,
Uri.
next prev parent reply other threads:[~2008-07-06 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 1:27 Bug Report: Live Migration - could someone help me Chen_PeterK
2008-07-04 1:27 ` Chen_PeterK
2008-07-06 10:06 ` Uri Lublin [this message]
2008-07-07 1:35 ` Chen_PeterK
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=4870990F.7000400@qumranet.com \
--to=uril@qumranet.com \
--cc=Chen_PeterK@emc.com \
--cc=kvm@vger.kernel.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 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.