Hi, all, This is KVM biweekly test result against kvm.git: f7ebf25e0c1e6cd8ff31f56a076908a169044090 and qemu-kvm.git: 02152f7275ebede652360c3840cf45fe240d34f0, based on kernel 2.6.35-rc2+. Two new issues found recently, one is kernel panic if start kvm sometimes. The other is qemu segmentation fault when use qemu-img create qcow image. New issues: 1. host panic on kernel 2.6.34 https://bugzilla.kernel.org/show_bug.cgi?id=16082 [Update]: kernel 2.6.34 and 2.6.35 has this issue. 2. qemu segmentation fault when create qcow2 image with qemu-img command https://bugs.launchpad.net/qemu/+bug/592056 [Update]: Kevin Wolf has a fix patch for it in qemu-devel mail list. Six Old Issues: ================================================ 1. 32PAE Windows guest is slow to boot with acpi on shadow https://sourceforge.net/tracker/?func=detail&aid=2976863&group_id=180599&atid=893831 2. Hot-added device is not visible in guest after migration https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2832416&group_id=180599 [Update]: Alex Williamson has a fix in qemu upstream tree. 3. ltp diotest running time is 2.54 times than before https://sourceforge.net/tracker/?func=detail&aid=2723366&group_id=180599&atid=893831 4. 32bits Rhel5/FC6 guest may fail to reboot after installation https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1991647&group_id=180599 5. perfctr wrmsr warning when booting 64bit RHEl5.3 https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831 6. [SR] qemu return form "migrate " command spend long time https://sourceforge.net/tracker/?func=detail&aid=2942079&group_id=180599&atid=893831 Test environment ================================================ Platform A Stoakley/Clovertown CPU 4 Memory size 8G Summary Test Report of Last Session ===================================================================== Total Pass Fail NoResult Crash ===================================================================== control_panel 17 15 2 0 0 gtest 23 20 3 0 0 ===================================================================== control_panel 17 15 2 0 0 :KVM_4G_guest_64_g32e 1 1 0 0 0 :KVM_four_sguest_64_gPAE 1 1 0 0 0 :KVM_LM_SMP_64_g32e 1 0 1 0 0 :KVM_linux_win_64_gPAE 1 1 0 0 0 :KVM_LM_SMP_64_gPAE 1 1 0 0 0 :KVM_SR_Continuity_64_gP 1 1 0 0 0 :KVM_four_sguest_64_g32e 1 1 0 0 0 :KVM_four_dguest_64_gPAE 1 1 0 0 0 :KVM_SR_SMP_64_gPAE 1 1 0 0 0 :KVM_LM_Continuity_64_g3 1 1 0 0 0 :KVM_1500M_guest_64_gPAE 1 1 0 0 0 :KVM_LM_Continuity_64_gP 1 0 1 0 0 :KVM_1500M_guest_64_g32e 1 1 0 0 0 :KVM_SR_Continuity_64_g3 1 1 0 0 0 :KVM_two_winxp_64_gPAE 1 1 0 0 0 :KVM_256M_guest_64_gPAE 1 1 0 0 0 :KVM_256M_guest_64_g32e 1 1 0 0 0 gtest 23 20 3 0 0 :boot_up_acpi_64_gPAE 1 1 0 0 0 :boot_up_noacpi_xp_64_gP 1 1 0 0 0 :boot_base_kernel_64_gPA 1 1 0 0 0 :boot_up_vista_64_g32e 1 1 0 0 0 :boot_smp_acpi_win2k3_64 1 0 1 0 0 :kb_nightly_64_gPAE 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_gPA 1 0 1 0 0 :boot_smp_acpi_xp_64_g32 1 1 0 0 0 :boot_smp_vista_64_gPAE 1 1 0 0 0 :boot_up_acpi_64_g32e 1 1 0 0 0 :boot_base_kernel_64_g32 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_win2008_64_gPAE 1 0 1 0 0 :ltp_nightly_64_g32e 1 1 0 0 0 :boot_smp_win2008_64_g32 1 1 0 0 0 :boot_up_vista_64_gPAE 1 1 0 0 0 :ltp_nightly_64_gPAE 1 1 0 0 0 :boot_smp_acpi_win2k3_64 1 1 0 0 0 :boot_up_noacpi_win2k3_6 1 1 0 0 0 :boot_smp_win7_ent_64_gP 1 1 0 0 0 ===================================================================== Total 40 35 5 0 0 Best Regards, Xudong Hao-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
