From: Paolo Bonzini <pbonzini@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
Date: Wed, 29 May 2013 23:26:50 +0200 [thread overview]
Message-ID: <51A6729A.6020705@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A1001AE4BC0@SHSMSX102.ccr.corp.intel.com>
Il 29/05/2013 10:12, Ren, Yongjie ha scritto:
> Hi All,
>
> This is KVM upstream test result against kvm.git next branch and qemu-kvm.git uq/master branch.
> kvm.git next branch: e47a5f5fb715b90b40747e9e235de557c6abd56c based on kernel 3.10.0-rc1
> qemu-kvm.git uq/master branch: b5803aa3583e82e5133f7621121bc15ee694f4a1
>
> We found 5 new bugs and verified 1 fixed bug this month.
> We also closed a bug as invalid because it's a known issue that some Windows version is not supported for I350 NIC.
>
> New issues (5):
> 1. guest cannot boot up when Intel 82572 NIC assigned
> https://bugs.launchpad.net/qemu/+bug/1182716
> -- this may already been fixed in qemu.git tree but it still exists in qemu-kvm.git uq/master branch.
>
> 2. with 'monitor pty', it needs to flush pts device after sending command to it
> https://bugs.launchpad.net/qemu/+bug/1185228
>
> 3. [nested virt] L2 Windows guest can't boot up ('-cpu host' to start L1)
> https://bugzilla.kernel.org/show_bug.cgi?id=58921
>
> 4. SMP x64 Windows 2003 guest can't boot up
> https://bugzilla.kernel.org/show_bug.cgi?id=58931
Can you reproduce this with "modprobe kvm_intel
emulate_invalid_guest_state=0"?
Thanks,
Paolo
> 5. [nested virt] L2 has NMI error when creating L1 with "-cpu host" parameter
> https://bugzilla.kernel.org/show_bug.cgi?id=58941
> -- this may have some relationship with the above bug #58921.
next prev parent reply other threads:[~2013-05-29 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 8:12 KVM Test report, kernel e47a5f5f... qemu b5803aa3 Ren, Yongjie
2013-05-29 21:26 ` Paolo Bonzini [this message]
2013-05-30 5:53 ` Ren, Yongjie
2013-05-31 8:46 ` Ren, Yongjie
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=51A6729A.6020705@redhat.com \
--to=pbonzini@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 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.