From: Gerrit Slomma <roadrunner_gs@web.de>
To: kvm@vger.kernel.org
Subject: Re: problems with live migration using kvm-84
Date: Sat, 28 Mar 2009 19:33:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20090328T193051-959@post.gmane.org> (raw)
In-Reply-To: 49CE1149.2030506@wpkg.org
Tomasz Chmielewski <mangoo <at> wpkg.org> writes:
>
> Gerrit Slomma schrieb:
> > Hello and good day.
> >
> > I have filed a bug report via bugzilla.redhat.com with the id
>
> With what ID?
>
> Could you give the full URL?
>
Sorry, my fault.
Full URL is:
https://bugzilla.redhat.com/show_bug.cgi?id=492688
Problem is described there but for the lazy i copy-paste it here:
Virtual machine gets stuck after migration. One CPU is 100% load, other one
idles. The virtual machine could be pinged, ssh-login is not always possible.
If stopped on migration target and continued on migration-source the virtual
machine recovers after some time without load.
Version-Release number of selected component (if applicable):
kvm-84-1.el5.x86_64.rpm
kvm-kmod-84-1.el5.x86_64.rpm
qemu-0.9.1-11.el5.x86_64.rpm
qemu-img-0.9.1-11.el5.x86_64.rpm
kvm and kvm-kmod compiled from sourceforge sources and installed from built
rpm, qemu and qemu-img are from EPEL-repository
How reproducible:
Start a kvm-virtual-machine on host A, start a kvm-virtual-machine with the
same parameters on host B in incoming-Mode. Migrate the virtual-machine from
host A to host B. Watch the kvm-process go to 100% after migration finishs.
Maybe you have to wait up to 5 seconds or apply a ls or such in the virtual
machine. After stopping virtual machine on host B and continuing virtual
machine on host A the virtual machine recovers
next prev parent reply other threads:[~2009-03-28 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 11:12 problems with live migration using kvm-84 Gerrit Slomma
2009-03-28 12:00 ` Tomasz Chmielewski
2009-03-28 19:33 ` Gerrit Slomma [this message]
2009-03-31 20:26 ` Gerrit Slomma
2009-03-31 20:49 ` Gerrit Slomma
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=loom.20090328T193051-959@post.gmane.org \
--to=roadrunner_gs@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox