From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: Biweekly KVM Test report, kernel a72e315c... qemu b73357ec...
Date: Mon, 21 Mar 2011 18:51:22 +0200 [thread overview]
Message-ID: <4D87820A.7020703@redhat.com> (raw)
In-Reply-To: <4D877C31.1060105@redhat.com>
On 03/21/2011 06:26 PM, Avi Kivity wrote:
> On 03/21/2011 02:35 PM, Avi Kivity wrote:
> > On 03/21/2011 04:47 AM, Ren, Yongjie wrote:
> > > Hi all,
> > > This is KVM test result against kvm.git a72e315c509376bbd1e121219c3ad9f23973923f based on kernel 2.6.38-rc6+, and qemu-kvm.git b73357ecd2b14c057134cb71d29447b5b988c516.
> > >
> > > The VT-d bug 730441 concerning "nomsi NIC" is exist for two weeks.
> > > We found another two issues: one about "Save/Restore" , the other about "Live Migration".
> > >
> > > New issues:
> > > 1. [KVM-User] I/O errors after "Save/Restore"
> > > https://bugs.launchpad.net/qemu/+bug/739088.
> >
> > Probably the same as the next issue.
> >
> > > 2. [KVM-User] guest hangs when using network after live migration
> > > https://bugs.launchpad.net/qemu/+bug/739092
> >
> > Confirmed, autotest Fedora.32.migrate.tmp also fails. Looks like the
> > recent qemu.git merge. I am bisecting to find out more.
> >
>
> 82fa39b75181b730d6d4d09f443bd26bcfcd045c is the first bad commit
> commit 82fa39b75181b730d6d4d09f443bd26bcfcd045c
> Author: Juan Quintela <quintela@redhat.com>
> Date: Thu Mar 10 12:33:49 2011 +0100
>
> vmstate: Fix varrays with uint8 indexes
With this reverted, qemu-kvm.git master appears to work.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-21 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 2:47 Biweekly KVM Test report, kernel a72e315c... qemu b73357ec Ren, Yongjie
2011-03-21 12:35 ` Avi Kivity
2011-03-21 16:26 ` Avi Kivity
2011-03-21 16:51 ` Avi Kivity [this message]
2011-03-22 9:32 ` Avi Kivity
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=4D87820A.7020703@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=quintela@redhat.com \
--cc=yongjie.ren@intel.com \
/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.