* KVM Test report, kernel e47a5f5f... qemu b5803aa3...
@ 2013-05-29 8:12 Ren, Yongjie
2013-05-29 21:26 ` Paolo Bonzini
2013-05-31 8:46 ` Ren, Yongjie
0 siblings, 2 replies; 4+ messages in thread
From: Ren, Yongjie @ 2013-05-29 8:12 UTC (permalink / raw)
To: kvm@vger.kernel.org
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
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.
Fixed issue (1):
1. [nested virt] L1 CPU Stuck when booting a L2 guest
https://bugzilla.kernel.org/show_bug.cgi?id=56971
Closed issue with invalid(1):
1. [SR-IOV] Intel I350 NIC VF cannot work in a Windows 2008 guest.
https://bugzilla.kernel.org/show_bug.cgi?id=56981
-- Intel driver team said I350 is supported in Win2k8 R2 version (not supported Win2k8).
Old issues (6):
----------------------------------------------------------------------------------------------------------
1. guest panic with parameter "-cpu host" in qemu command line (about vPMU issue).
https://bugs.launchpad.net/qemu/+bug/994378
2. Can't install or boot up 32bit win8 guest.
https://bugs.launchpad.net/qemu/+bug/1007269
3. vCPU hot-add makes the guest abort.
https://bugs.launchpad.net/qemu/+bug/1019179
4. Nested Virt: VMX can't be initialized in L1 Xen ("Xen on KVM")
https://bugzilla.kernel.org/show_bug.cgi?id=45931
5. Guest has no "xsave" feature with parameter "-cpu qemu64,+xsave" in qemu command line.
https://bugs.launchpad.net/qemu/+bug/1042561
6. Guest hang when doing kernel build and writing data in guest.
https://bugs.launchpad.net/qemu/+bug/1096814
Test environment:
==================================================================
Platform IvyBridge-EP Sandybridge-EP
CPU Cores 32 32
Memory size 64GB 32GB
Regards
Yongjie Ren (Jay)
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
2013-05-29 8:12 KVM Test report, kernel e47a5f5f... qemu b5803aa3 Ren, Yongjie
@ 2013-05-29 21:26 ` Paolo Bonzini
2013-05-30 5:53 ` Ren, Yongjie
2013-05-31 8:46 ` Ren, Yongjie
1 sibling, 1 reply; 4+ messages in thread
From: Paolo Bonzini @ 2013-05-29 21:26 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: kvm@vger.kernel.org
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.
^ permalink raw reply [flat|nested] 4+ messages in thread* RE: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
2013-05-29 21:26 ` Paolo Bonzini
@ 2013-05-30 5:53 ` Ren, Yongjie
0 siblings, 0 replies; 4+ messages in thread
From: Ren, Yongjie @ 2013-05-30 5:53 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: kvm@vger.kernel.org
> -----Original Message-----
> From: Paolo Bonzini [mailto:paolo.bonzini@gmail.com] On Behalf Of Paolo
> Bonzini
> Sent: Thursday, May 30, 2013 5:27 AM
> To: Ren, Yongjie
> Cc: kvm@vger.kernel.org
> Subject: Re: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
>
> 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"?
>
Yes. This bug still exists with "modprobe kvm_intel emulate_invalid_guest_state=0".
The VNC console of a SMP x64 Window 2003 guest is always blank (nothing is displayed).
But UP (1 vCPU) Windows 2003 guest can work fine.
Best regards,
Jay
> 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
2013-05-29 8:12 KVM Test report, kernel e47a5f5f... qemu b5803aa3 Ren, Yongjie
2013-05-29 21:26 ` Paolo Bonzini
@ 2013-05-31 8:46 ` Ren, Yongjie
1 sibling, 0 replies; 4+ messages in thread
From: Ren, Yongjie @ 2013-05-31 8:46 UTC (permalink / raw)
To: jan.kiszka@siemens.com, kvm@vger.kernel.org; +Cc: Liu, RongrongX, Liu, Dan D
> 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.
>
I think someone also reported this issue in the mailing list weeks ago.
Jan, Can you reproduce this issue? or any idea to fix it?
I found your following commit is the first bad commit for this bug.
commit 3b656cf764cbc43d3efb9bf5f45c618d4cf0989f
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date: Sun Apr 14 12:12:45 2013 +0200
KVM: nVMX: Fix injection of PENDING_INTERRUPT and NMI_WINDOW exits to L1
Check if the interrupt or NMI window exit is for L1 by testing if it has
the corresponding controls enabled. This is required when we allow
direct injection from L0 to L2
Best Regards,
Yongjie (Jay)
> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
> On Behalf Of Ren, Yongjie
> Sent: Wednesday, May 29, 2013 4:13 PM
> To: kvm@vger.kernel.org
> Subject: KVM Test report, kernel e47a5f5f... qemu b5803aa3...
>
> 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
>
> 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.
>
> Fixed issue (1):
> 1. [nested virt] L1 CPU Stuck when booting a L2 guest
> https://bugzilla.kernel.org/show_bug.cgi?id=56971
>
> Closed issue with invalid(1):
> 1. [SR-IOV] Intel I350 NIC VF cannot work in a Windows 2008 guest.
> https://bugzilla.kernel.org/show_bug.cgi?id=56981
> -- Intel driver team said I350 is supported in Win2k8 R2 version (not
> supported Win2k8).
>
> Old issues (6):
> ----------------------------------------------------------------------------------------------------------
> 1. guest panic with parameter "-cpu host" in qemu command line (about
> vPMU issue).
> https://bugs.launchpad.net/qemu/+bug/994378
> 2. Can't install or boot up 32bit win8 guest.
> https://bugs.launchpad.net/qemu/+bug/1007269
> 3. vCPU hot-add makes the guest abort.
> https://bugs.launchpad.net/qemu/+bug/1019179
> 4. Nested Virt: VMX can't be initialized in L1 Xen ("Xen on KVM")
> https://bugzilla.kernel.org/show_bug.cgi?id=45931
> 5. Guest has no "xsave" feature with parameter "-cpu qemu64,+xsave" in
> qemu command line.
> https://bugs.launchpad.net/qemu/+bug/1042561
> 6. Guest hang when doing kernel build and writing data in guest.
> https://bugs.launchpad.net/qemu/+bug/1096814
>
>
> Test environment:
> ============================================================
> ======
> Platform IvyBridge-EP Sandybridge-EP
> CPU Cores 32 32
> Memory size 64GB 32GB
>
>
> Regards
> Yongjie Ren (Jay)
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-05-31 8:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-29 8:12 KVM Test report, kernel e47a5f5f... qemu b5803aa3 Ren, Yongjie
2013-05-29 21:26 ` Paolo Bonzini
2013-05-30 5:53 ` Ren, Yongjie
2013-05-31 8:46 ` Ren, Yongjie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox