Li, Haicheng
2009-Feb-14 13:28 UTC
[Xen-devel] Bi-weekly VMX status report. Xen: #19198 & Xen0: #793
Hi all,
This is our bi-weekly test report for Xen-unstable tree. 2 new bugs were found
in the past 2 weeks. VT-d testing was blocked by bug #1417.
New Bugs:
====================================================================1. cpu
offline causes Xen panic.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1416
2. [VT-d] Xen hypervisor will crash at booting if vt-d is enabled.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1417
Old Bugs:
====================================================================1. cpu idle
time / cpufreq residency becomes extremely large.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1394
2. with AHCI disk drive, dom0 S3 resume is failed.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1374
3. stubdom based guest hangs when assigning hdc to it.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1373
4. [stubdom]The xm save command hangs while saving <Domain-dm>.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1377
5. [stubdom] cannot restore stubdom based domain.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1378
6. [VT-d] failed to reassign some PCI-e NICs.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1379
7. stubdom based guest hangs at starting when using qcow image.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1372
8. Qemu exit(1) if guest tries setup msi for VT-d device.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1408
9. VT-d fault causes disk corrupted or Dom0 kernel panic.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1409
Xen Info:
===========================================================================xen-changeset:
19198:32b154137492
dom0-changeset: 793:3aa9b8a7876b
ioemu git:
commit 200a4ece52fa37d6b884b52c47e3d56b9c1c7563
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Mon Feb 9 10:40:12 2009 +0000
Test Environment:
===============================================================Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Hardware : Nehalem
Xen package: 19198:32b154137492
Platform : PAE
Service OS : Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Hardware : Nehalem
Xen package: 19198:32b154137492
Details:
====================================================================X86_64:
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd_ept_vpid
16 0 16 0 0
ras_ept_vpid 1 0 0 0 1
control_panel_ept_vpid 18 17 1 0 0
stubdom_ept_vpid 1 1 0 0 0
gtest_ept_vpid 22 20 2 0 0
acpi_ept_vpid 2 0 2 0 0
device_model_ept_vpid 2 2 0 0 0
====================================================================vtd_ept_vpid
16 0 16 0 0
:two_dev_up_xp_nomsi_64_ 1 0 1 0 0
:two_dev_smp_nomsi_64_g3 1 0 1 0 0
:two_dev_scp_64_g32e 1 0 1 0 0
:lm_pcie_smp_64_g32e 1 0 1 0 0
:lm_pcie_up_64_g32e 1 0 1 0 0
:two_dev_up_64_g32e 1 0 1 0 0
:lm_pcie_up_xp_nomsi_64_ 1 0 1 0 0
:two_dev_up_nomsi_64_g32 1 0 1 0 0
:two_dev_smp_64_g32e 1 0 1 0 0
:lm_pci_up_xp_nomsi_64_g 1 0 1 0 0
:lm_pci_up_nomsi_64_g32e 1 0 1 0 0
:two_dev_smp_xp_nomsi_64 1 0 1 0 0
:two_dev_scp_nomsi_64_g3 1 0 1 0 0
:lm_pcie_smp_xp_nomsi_64 1 0 1 0 0
:lm_pci_smp_nomsi_64_g32 1 0 1 0 0
:lm_pci_smp_xp_nomsi_64_ 1 0 1 0 0
ras_ept_vpid 1 0 0 0 1
:cpu_online_offline_64_g 1 0 0 0 1
control_panel_ept_vpid 18 17 1 0 0
:XEN_1500M_guest_64_g32e 1 1 0 0 0
:XEN_LM_Continuity_64_g3 1 1 0 0 0
:XEN_256M_xenu_64_gPAE 1 1 0 0 0
:XEN_four_vmx_xenu_seq_6 1 1 0 0 0
:XEN_vmx_vcpu_pin_64_g32 1 1 0 0 0
:XEN_SR_Continuity_64_g3 1 1 0 0 0
:XEN_linux_win_64_g32e 1 1 0 0 0
:XEN_vmx_2vcpu_64_g32e 1 1 0 0 0
:XEN_1500M_guest_64_gPAE 1 1 0 0 0
:XEN_four_dguest_co_64_g 1 1 0 0 0
:XEN_two_winxp_64_g32e 1 0 1 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_256M_guest_64_gPAE 1 1 0 0 0
:XEN_LM_SMP_64_g32e 1 1 0 0 0
:XEN_Nevada_xenu_64_g32e 1 1 0 0 0
:XEN_256M_guest_64_g32e 1 1 0 0 0
:XEN_SR_SMP_64_g32e 1 1 0 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
stubdom_ept_vpid 1 1 0 0 0
:boot_stubdom_no_qcow_64 1 1 0 0 0
gtest_ept_vpid 22 20 2 0 0
:boot_up_acpi_win2k_64_g 1 1 0 0 0
:boot_up_noacpi_win2k_64 1 1 0 0 0
:reboot_xp_64_g32e 1 1 0 0 0
:boot_solaris10u5_64_g32 1 1 0 0 0
:boot_up_vista_64_g32e 1 0 1 0 0
:boot_indiana_64_g32e 1 1 0 0 0
:boot_up_acpi_xp_64_g32e 1 1 0 0 0
:boot_smp_acpi_xp_64_g32 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
: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_nevada_64_g32e 1 1 0 0 0
:boot_smp_vista_64_g32e 1 0 1 0 0
:ltp_nightly_64_g32e 1 1 0 0 0
:boot_fc9_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_rhel5u1_64_g32e 1 1 0 0 0
:reboot_fc6_64_g32e 1 1 0 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
acpi_ept_vpid 2 0 2 0 0
:hvm_s3_sr_64_g32e 1 0 1 0 0
:hvm_s3_smp_64_g32e 1 0 1 0 0
device_model_ept_vpid 2 2 0 0 0
:pv_on_up_64_g32e 1 1 0 0 0
:pv_on_smp_64_g32e 1 1 0 0 0
====================================================================Total
62 40 21 0 1
32PAE:
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================control_panel_ept_vpid
14 14 0 0 0
stubdom_ept_vpid 2 1 1 0 0
gtest_ept_vpid 24 24 0 0 0
acpi_ept_vpid 2 0 2 0 0
device_model_ept_vpid 2 2 0 0 0
====================================================================control_panel_ept_vpid
14 14 0 0 0
:XEN_four_vmx_xenu_seq_P 1 1 0 0 0
:XEN_four_dguest_co_PAE_ 1 1 0 0 0
:XEN_SR_SMP_PAE_gPAE 1 1 0 0 0
:XEN_linux_win_PAE_gPAE 1 1 0 0 0
:XEN_Nevada_xenu_PAE_gPA 1 1 0 0 0
:XEN_LM_SMP_PAE_gPAE 1 1 0 0 0
:XEN_SR_Continuity_PAE_g 1 1 0 0 0
:XEN_vmx_vcpu_pin_PAE_gP 1 1 0 0 0
:XEN_LM_Continuity_PAE_g 1 1 0 0 0
:XEN_256M_guest_PAE_gPAE 1 1 0 0 0
:XEN_1500M_guest_PAE_gPA 1 1 0 0 0
:XEN_two_winxp_PAE_gPAE 1 1 0 0 0
:XEN_four_sguest_seq_PAE 1 1 0 0 0
:XEN_vmx_2vcpu_PAE_gPAE 1 1 0 0 0
stubdom_ept_vpid 2 1 1 0 0
:boot_stubdom_no_qcow_PA 1 1 0 0 0
:boot_stubdom_qcow_PAE_g 1 0 1 0 0
gtest_ept_vpid 24 24 0 0 0
:boot_up_acpi_PAE_gPAE 1 1 0 0 0
:ltp_nightly_PAE_gPAE 1 1 0 0 0
:reboot_xp_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_win2k3_PAE 1 1 0 0 0
:boot_smp_acpi_win2k3_PA 1 1 0 0 0
:boot_smp_acpi_win2k_PAE 1 1 0 0 0
:boot_up_acpi_win2k_PAE_ 1 1 0 0 0
:boot_smp_acpi_xp_PAE_gP 1 1 0 0 0
:boot_up_noacpi_win2k_PA 1 1 0 0 0
:boot_smp_vista_PAE_gPAE 1 1 0 0 0
:boot_up_noacpi_win2k3_P 1 1 0 0 0
:boot_nevada_PAE_gPAE 1 1 0 0 0
:boot_solaris10u5_PAE_gP 1 1 0 0 0
:boot_indiana_PAE_gPAE 1 1 0 0 0
:boot_rhel5u1_PAE_gPAE 1 1 0 0 0
:boot_base_kernel_PAE_gP 1 1 0 0 0
:boot_up_win2008_PAE_gPA 1 1 0 0 0
:boot_up_noacpi_xp_PAE_g 1 1 0 0 0
:boot_smp_win2008_PAE_gP 1 1 0 0 0
:reboot_fc6_PAE_gPAE 1 1 0 0 0
:boot_fc10_PAE_gPAE 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
acpi_ept_vpid 2 0 2 0 0
:hvm_s3_sr_PAE_gPAE 1 0 1 0 0
:hvm_s3_smp_PAE_gPAE 1 0 1 0 0
device_model_ept_vpid 2 2 0 0 0
:pv_on_up_PAE_gPAE 1 1 0 0 0
:pv_on_smp_PAE_gPAE 1 1 0 0 0
====================================================================Total
44 41 3 0 0
-haicheng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2009-Feb-14 13:43 UTC
Re: [Xen-devel] Bi-weekly VMX status report. Xen: #19198 & Xen0: #793
On 14/02/2009 13:28, "Li, Haicheng" <haicheng.li@intel.com> wrote:> Hi all, > > This is our bi-weekly test report for Xen-unstable tree. 2 new bugs were found > in the past 2 weeks. VT-d testing was blocked by bug #1417.Bug 1417 is probably fixed by c/s 19207. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Li, Haicheng
2009-Feb-14 13:49 UTC
RE: [Xen-devel] Bi-weekly VMX status report. Xen: #19198 & Xen0: #793
Keir Fraser wrote:> On 14/02/2009 13:28, "Li, Haicheng" <haicheng.li@intel.com> wrote: > >> Hi all, >> >> This is our bi-weekly test report for Xen-unstable tree. 2 new bugs >> were found in the past 2 weeks. VT-d testing was blocked by bug >> #1417. > > Bug 1417 is probably fixed by c/s 19207. > > -- KeirThanks, we will check it next Monday. -haicheng _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Li, Haicheng
2009-Feb-16 07:56 UTC
RE: [Xen-devel] Bi-weekly VMX status report. Xen: #19198 & Xen0: #793
Keir Fraser wrote:> On 14/02/2009 13:28, "Li, Haicheng" <haicheng.li@intel.com> wrote: > >> Hi all, >> >> This is our bi-weekly test report for Xen-unstable tree. 2 new bugs >> were found in the past 2 weeks. VT-d testing was blocked by bug >> #1417. > > Bug 1417 is probably fixed by c/s 19207. > > -- Keir2. [VT-d] Xen hypervisor will crash at booting if vt-d is enabled. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1417 For c/s 19210, with VT-d enabled, Xen doesn''t crash, but still hangs at booting on some HW platforms. Detailed serial log can be found via above BZ. -haicheng _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel