From: Avi Kivity <avi@redhat.com>
To: "Xu, Jiajun" <jiajun.xu@intel.com>
Cc: "'kvm-devel'" <kvm@vger.kernel.org>
Subject: Re: Biweekly KVM Test report, kernel 0b972... qemu f2593...
Date: Wed, 05 Aug 2009 16:14:33 +0300 [thread overview]
Message-ID: <4A7985B9.5090101@redhat.com> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E0897E01F2D@pdsmsx502.ccr.corp.intel.com>
On 08/05/2009 05:23 AM, Xu, Jiajun wrote:
> Hi All,
>
> There has been a long time we did not send out KVM testing resport. We will restart our biweekly report sending from this week. This Weekly KVM Testing Report against lastest kvm.git
>
Thanks, that's helpful.
> 0b972aaabb95808397c61483bd061f4e9ed10e11 and qemu-kvm.git
> f2593a0bf33ed609d87ad029ff003f1d50afb65e. There are two new bugs in lastest commit, one is for migration and another is vt-d issue after migration.
>
> Two New Issues:
> ================================================
> 1. Guest will be no response after migration
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2832401&group_id=180599
>
What kind of guest is this?
> Seven Old Issues:
> ================================================
> 1. ltp diotest running time is 2.54 times than before
> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
>
>
Most likely due to qcow2 switching to write through (from write back).
Write back is faster but is unsafe.
> 4. failure to migrate guests with more than 4GB of RAM
> https://sourceforge.net/tracker/index.php?func=detail&aid=1971512&group_id=180599&atid=893831
>
>
Can you retest this? I was able to migrate a 6GB smp guest without
problems.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-05 13:09 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 [this message]
2009-08-07 6:11 ` Xu, Jiajun
2009-08-09 11:32 ` Avi Kivity
2009-08-09 11:46 ` Avi Kivity
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=4A7985B9.5090101@redhat.com \
--to=avi@redhat.com \
--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