From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Ren, Yongjie" <yongjie.ren@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Biweekly KVM Test report, kernel a3e2cba1... qemu 2c9bb5d4...
Date: Mon, 04 Apr 2011 09:19:48 -0600 [thread overview]
Message-ID: <1301930388.19639.43.camel@x201> (raw)
In-Reply-To: <4D98332A.7040801@redhat.com>
On Sun, 2011-04-03 at 11:43 +0300, Avi Kivity wrote:
> On 04/02/2011 01:14 PM, Ren, Yongjie wrote:
> > Hi All,
> > This is KVM test result against kvm.git a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f based on kernel 2.6.38+, and qemu-kvm.git 2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a.
> >
> > We found 1 bug about "guest cannot boot with 8 VFs or more".
> > The VT-d bug 730441 (qemu bugzilla) concerning "nomsi NIC" is still exist for near a month.
Fix for this has been posted for a while -
http://www.spinics.net/lists/kvm/msg51735.html
> > 2 bugs about “Save/Restore” and "Live Migration" are fixed.
> >
> > New issue:
> > 1.guest cannot boot with 8 VFs or more
> > https://bugs.launchpad.net/qemu/+bug/744195
> >
>
> Alex?
Yep, we only support a fixed number of memory slots and device
assignment is a consumer. The core kvm code isn't very graceful about
exceeding that limit. We could add a temporary limit of assigned
devices, but it's not guaranteed to hit before we run out of slots since
it depends on the device. The real fix is to make kvm support an
arbitrary number of slots, but I don't know how to cache mmio fault
misses and it's since dropped below the cut line on my todo list.
Thanks,
Alex
next prev parent reply other threads:[~2011-04-04 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 10:14 Biweekly KVM Test report, kernel a3e2cba1... qemu 2c9bb5d4 Ren, Yongjie
2011-04-03 8:43 ` Avi Kivity
2011-04-04 15:19 ` Alex Williamson [this message]
2011-04-05 9:01 ` 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=1301930388.19639.43.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox