* Biweekly KVM Test report, kernel 681fb677... qemu 05f17375...
@ 2011-06-18 4:43 Ren, Yongjie
2011-06-19 8:57 ` Avi Kivity
0 siblings, 1 reply; 2+ messages in thread
From: Ren, Yongjie @ 2011-06-18 4:43 UTC (permalink / raw)
To: kvm@vger.kernel.org
Hi All,
This is KVM test result against kvm.git 681fb677ace0754589792c92b8dbee9884d07158 based on kernel 3.0.0-rc2+, and qemu-kvm.git 05f1737582ab6c075476bde931c5eafbc62a9349.
We found a new vt-d bug about “NIC assignment order in command line makes some NIC can't work”.
A vt-d bug was fixed in kvm.git upstream.
New issue:
1. NIC assignment order in command line make some NIC can't work
https://bugs.launchpad.net/qemu/+bug/799036
Fixed issue:
1. [VT-d] NIC cannot work when it had been used before
https://bugs.launchpad.net/qemu/+bug/754591
Old Issues:
1. ltp diotest running time is 2.54 times than before
https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831
2. perfctr wrmsr warning when booting 64bit RHEl5.3
https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
Test environment:
==================================================================
Platform Westmere-EP SanyBridge-EP
CPU 24 32
Memory size 10G 32G
Report summary of IA32E on Westmere-EP:
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 12 11 1 0 0
control_panel_ept 4 3 1 0 0
control_panel_vpid 3 3 0 0 0
control_panel 3 3 0 0 0
gtest_vpid 1 1 0 0 0
gtest_ept 1 1 0 0 0
gtest 3 3 0 0 0
vtd_ept_vpid 3 2 1 0 0
gtest_ept_vpid 12 12 0 0 0
sriov_ept_vpid 6 6 0 0 0
=====================================================================
control_panel_ept_vpid 12 11 1 0 0
:KVM_LM_Continuity_64_g3 1 1 0 0 0
:KVM_four_dguest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_SR_SMP_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_two_winxp_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_SR_Continuity_64_g3 1 1 0 0 0
:KVM_256M_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
control_panel_ept 4 3 1 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 0 1 0 0
control_panel_vpid 3 3 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
control_panel 3 3 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
gtest_vpid 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest_ept 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest 3 3 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_smp_win7_ent_64_gP 1 1 0 0 0
:boot_smp_vista_64_g32e 1 1 0 0 0
vtd_ept_vpid 3 2 1 0 0
:one_pcie_smp_xp_64_g32e 1 1 0 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
:two_dev_smp_64_g32e 1 0 1 0 0
gtest_ept_vpid 12 12 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:boot_up_win2008_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
sriov_ept_vpid 6 6 0 0 0
:one_vf_up_64_g32e 1 1 0 0 0
:hp_vf_up_64_g32e 1 1 0 0 0
:hp_vf_smp_64_g32e 1 1 0 0 0
:one_vf_smp_win2k8_64_g3 1 1 0 0 0
:one_vf_smp_64_g32e 1 1 0 0 0
:two_dev_smp_64_g32e 1 1 0 0 0
=====================================================================
Total 48 45 3 0 0
Report summary of IA32E on Sandy Bridge - EP:
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 12 12 0 0 0
control_panel_vpid 3 3 0 0 0
control_panel_ept 4 4 0 0 0
control_panel 3 3 0 0 0
gtest_ept 1 1 0 0 0
gtest_vpid 1 1 0 0 0
gtest 3 3 0 0 0
vtd_ept_vpid 2 1 1 0 0
gtest_ept_vpid 12 12 0 0 0
sriov_ept_vpid 6 3 3 0 0
=====================================================================
control_panel_ept_vpid 12 12 0 0 0
:KVM_LM_Continuity_64_g3 1 1 0 0 0
:KVM_four_dguest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_SR_SMP_64_g32e 1 1 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_two_winxp_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_256M_guest_64_gPAE 1 1 0 0 0
:KVM_SR_Continuity_64_g3 1 1 0 0 0
:KVM_256M_guest_64_g32e 1 1 0 0 0
:KVM_four_sguest_64_g32e 1 1 0 0 0
control_panel_vpid 3 3 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
control_panel_ept 4 4 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
control_panel 3 3 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
gtest_ept 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest_vpid 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
gtest 3 3 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_smp_win7_ent_64_gP 1 1 0 0 0
:boot_smp_vista_64_g32e 1 1 0 0 0
vtd_ept_vpid 2 1 1 0 0
:one_pcie_smp_xp_64_g32e 1 0 1 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
gtest_ept_vpid 12 12 0 0 0
:boot_up_acpi_64_g32e 1 1 0 0 0
:boot_base_kernel_64_g32 1 1 0 0 0
:boot_up_win2008_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_smp_win2008_64_g32 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_smp_win7_ent_64_g3 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 1 1 0 0 0
sriov_ept_vpid 6 3 3 0 0
:one_vf_up_64_g32e 1 1 0 0 0
:hp_vf_up_64_g32e 1 1 0 0 0
:hp_vf_smp_64_g32e 1 0 1 0 0
:one_vf_smp_win2k8_64_g3 1 1 0 0 0
:one_vf_smp_64_g32e 1 0 1 0 0
:two_dev_smp_64_g32e 1 0 1 0 0
=====================================================================
Total 47 43 4 0 0
Best Regards,
Yongjie Ren (Jay)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Biweekly KVM Test report, kernel 681fb677... qemu 05f17375...
2011-06-18 4:43 Biweekly KVM Test report, kernel 681fb677... qemu 05f17375 Ren, Yongjie
@ 2011-06-19 8:57 ` Avi Kivity
0 siblings, 0 replies; 2+ messages in thread
From: Avi Kivity @ 2011-06-19 8:57 UTC (permalink / raw)
To: Ren, Yongjie; +Cc: kvm@vger.kernel.org, Alex Williamson
On 06/18/2011 07:43 AM, Ren, Yongjie wrote:
> Hi All,
> This is KVM test result against kvm.git 681fb677ace0754589792c92b8dbee9884d07158 based on kernel 3.0.0-rc2+, and qemu-kvm.git 05f1737582ab6c075476bde931c5eafbc62a9349.
>
> We found a new vt-d bug about “NIC assignment order in command line makes some NIC can't work”.
> A vt-d bug was fixed in kvm.git upstream.
>
> New issue:
> 1. NIC assignment order in command line make some NIC can't work
> https://bugs.launchpad.net/qemu/+bug/799036
>
> Fixed issue:
> 1. [VT-d] NIC cannot work when it had been used before
> https://bugs.launchpad.net/qemu/+bug/754591
cc += Alex
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-06-19 8:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-18 4:43 Biweekly KVM Test report, kernel 681fb677... qemu 05f17375 Ren, Yongjie
2011-06-19 8:57 ` Avi Kivity
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox