public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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, kvm.git 66b0ae... qemu-kvm.git 6e57bb...
Date: Sun, 10 May 2009 18:21:43 +0300	[thread overview]
Message-ID: <4A06F107.6000801@redhat.com> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E15B82DCB@pdsmsx502.ccr.corp.intel.com>

Xu, Jiajun wrote:
> Hi All,
>
> This is our Weekly KVM Testing Report against lastest kvm.git
> 66b0aed4a9e15a2ea3a00763f362b6ee0b28d538 and qemu-kvm.git
> 6e57bb9a636cefdaba7decbd5ac10f1508ff64c0. There is a Live Migration bug found in this two weeks.
>
> One New Issue:
> ================================================
> 1. Destination guest will reboot when Migration
> https://sourceforge.net/tracker/?func=detail&aid=2789729&group_id=180599&atid=893831
>
>   

There's a patch pending for this, should be applied in a day or too.

> Old Issue List:
> ================================================
> 1. ltp diotest running time is 2.54 times than before
> https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
>   

This test is not very meaningful on qcow2.  It should be run on an LVM 
parition, with cache=none:

   -drive file=/dev/volgroup/image,cache=none



-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-05-10 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 15:15 Biweekly KVM Test report, kvm.git 66b0ae... qemu-kvm.git 6e57bb Xu, Jiajun
2009-05-10 15:21 ` Avi Kivity [this message]

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=4A06F107.6000801@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