Hi All,
This is KVM test result against kvm.git
b796a09c5d808f4013f27ad45953db604dac18fd based on 3.1.0, and qemu.git
7879db7e9c09b92d9af1c143fbe2cc212ec89e4b.
We filed 3 new bugs during our test.
One of them is that kvm is not enabled by default when qemu starting a
guest. This bug has already been fixed.
The other two bugs are about vt-d NIC assignment in Windows guest and
SR-IOV VF hot-plug issue in guest.
We also found 2 vt-d device assignment bugs got fixed.
New issues(2):
1. guest aborts when detaching a SR-IOV VF
https://bugs.launchpad.net/qemu/+bug/875723
2. VT-D NIC doesn't work in windows guest
https://bugs.launchpad.net/qemu/+bug/877155
---this should be a kernel bug. For https://bugzilla.kernel.org is not
available yet, I filed this bug in qemu bugzilla just for tracking.
Fixed issues(3):
1. VF doesn't work in guest when not pinned with "addr="
https://bugs.launchpad.net/qemu/+bug/830558
2. NIC assignment order in command line make some NIC can't work
https://bugs.launchpad.net/qemu/+bug/799036
3. device assignment doesn't work: "error: requires KVM support"
https://bugs.launchpad.net/qemu/+bug/882358
Test environment:
==================================================================
Platform Westmere-EP
CPU Cores 24
Memory size 10G
Report summary of IA32E on Westmere-EP:
Summary Test Report of Last Session
=====================================================================
Total Pass Fail NoResult Crash
=====================================================================
control_panel_ept_vpid 12 12 0 0 0
control_panel_ept 4 4 0 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 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_SR_SMP_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 1 1 0 0 0
:KVM_linux_win_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_two_winxp_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 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_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 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 3 3 0 0 0
:KVM_1500M_guest_64_g32e 1 1 0 0 0
:KVM_LM_SMP_64_g32e 1 1 0 0 0
:KVM_1500M_guest_64_gPAE 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 0 1 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
:two_dev_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
:kb_nightly_64_g32e 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 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_smp_acpi_win2k3_64 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_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 0 1 0 0
:hp_vf_smp_64_g32e 1 0 1 0 0
:one_vf_smp_win2k8_64_g3 1 0 1 0 0
:one_vf_smp_64_g32e 1 1 0 0 0
:two_dev_smp_64_g32e 1 1 0 0 0
=====================================================================
Total 48 44 4 0 0
Best Regards,
Yongjie Ren (Jay)
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
