From: Avi Kivity <avi@redhat.com>
To: "Xu, Jiajun" <jiajun.xu@intel.com>,
Anthony Liguori <anthony@codemonkey.ws>
Cc: "'kvm-devel'" <kvm@vger.kernel.org>
Subject: Re: Biweekly KVM Test report, kernel 0b972... qemu f2593...
Date: Sun, 09 Aug 2009 14:46:32 +0300 [thread overview]
Message-ID: <4A7EB718.5090506@redhat.com> (raw)
In-Reply-To: <4A7EB3BC.70400@redhat.com>
On 08/09/2009 02:32 PM, Avi Kivity wrote:
>
> I see that the guest is in stopped state after migration, issuing the
> cont command in the monitor unhalts it.
>
> Anthony, was this a planned change, or is it a regression?
>
Okay, looks like a regression. I fixed this in qemu-kvm.git and send a
patch for upstream.
This did show up in my own regression tests but I ignored it for some
reason...
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-09 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 2:23 Biweekly KVM Test report, kernel 0b972... qemu f2593 Xu, Jiajun
2009-08-05 13:14 ` Avi Kivity
2009-08-07 6:11 ` Xu, Jiajun
2009-08-09 11:32 ` Avi Kivity
2009-08-09 11:46 ` Avi Kivity [this message]
2009-08-10 8:00 ` Xu, Jiajun
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=4A7EB718.5090506@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jiajun.xu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox