Li, Haicheng
2008-Oct-07 08:00 UTC
[Xen-devel] Weekly VMX status report. Xen: #18560 & Xen0: #682
Hi all,
This is our weekly test report for Xen-unstable tree. No new issue found; P1 bug
#1339 still blocks our save/restore related cases.
Old Bugs:
====================================================================1. TSC not
accurate in Windows HVM.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1291
2. SMP 32e RHEL5.1 timer would be slow,if under working pressure.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1290
3. Guest will hang after Save/Restore.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339
Testing Environment:
====================================================================PAE
CPU : Xeon(r) processor 5300 series
Dom0 OS : RHEL5.1
Memory size : 8G
IA32E
CPU : Xeon(r) processor 5300 series
Dom0 OS : RHEL5
Memory size : 8G
Details:
====================================================================
Platform : PAE
Service OS : Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Hardware : Clovertown
Xen package: 18560:782599274bf9
Date: Wed Oct 1 09:10:10 CST 2008
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
16 9 7 0 0
device_model 2 2 0 0 0
control_panel 15 11 4 0 0
acpi 5 5 0 0 0
gtest 24 24 0 0 0
====================================================================vtd
16 9 7 0 0
:lm_pci_up_xp_nomsi_PAE_ 1 0 1 0 0
:two_dev_scp_nomsi_PAE_g 1 1 0 0 0
:lm_pcie_up_xp_nomsi_PAE 1 0 1 0 0
:two_dev_up_xp_nomsi_PAE 1 1 0 0 0
:two_dev_smp_xp_nomsi_PA 1 1 0 0 0
:two_dev_smp_PAE_gPAE 1 1 0 0 0
:two_dev_up_nomsi_PAE_gP 1 1 0 0 0
:two_dev_scp_PAE_gPAE 1 1 0 0 0
:lm_pcie_smp_xp_nomsi_PA 1 1 0 0 0
:lm_pci_up_nomsi_PAE_gPA 1 0 1 0 0
:lm_pci_smp_xp_nomsi_PAE 1 0 1 0 0
:two_dev_up_PAE_gPAE 1 1 0 0 0
:lm_pcie_smp_nomsi_PAE_g 1 0 1 0 0
:two_dev_smp_nomsi_PAE_g 1 1 0 0 0
:lm_pcie_up_nomsi_PAE_gP 1 0 1 0 0
:lm_pci_smp_nomsi_PAE_gP 1 0 1 0 0
device_model 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
control_panel 15 11 4 0 0
:XEN_4G_guest_PAE_gPAE 1 1 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_linux_win_PAE_gPAE 1 1 0 0 0
:XEN_SR_SMP_PAE_gPAE 1 0 1 0 0
:XEN_Nevada_xenu_PAE_gPA 1 1 0 0 0
:XEN_LM_SMP_PAE_gPAE 1 0 1 0 0
:XEN_SR_Continuity_PAE_g 1 0 1 0 0
:XEN_vmx_vcpu_pin_PAE_gP 1 1 0 0 0
:XEN_two_winxp_PAE_gPAE 1 1 0 0 0
:XEN_LM_Continuity_PAE_g 1 0 1 0 0
:XEN_256M_guest_PAE_gPAE 1 1 0 0 0
:XEN_1500M_guest_PAE_gPA 1 1 0 0 0
:XEN_vmx_2vcpu_PAE_gPAE 1 1 0 0 0
:XEN_four_sguest_seq_PAE 1 1 0 0 0
acpi 5 5 0 0 0
:check_p_residency_PAE_g 1 1 0 0 0
:Dom0_S3_PAE_gPAE 1 1 0 0 0
:check_c_trigger_PAE_gPA 1 1 0 0 0
:check_p_trigger_PAE_gPA 1 1 0 0 0
:check_c_residency_PAE_g 1 1 0 0 0
gtest 24 24 0 0 0
:boot_up_acpi_PAE_gPAE 1 1 0 0 0
:ltp_nightly_PAE_gPAE 1 1 0 0 0
:boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
:reboot_xp_PAE_gPAE 1 1 0 0 0
:boot_up_vista_PAE_gPAE 1 1 0 0 0
:boot_fc9_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_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
:bootx_PAE_gPAE 1 1 0 0 0
:reboot_fc6_PAE_gPAE 1 1 0 0 0
:boot_smp_win2008_PAE_gP 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
====================================================================Total
62 51 11 0 0
Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
Xen package: 18560:782599274bf9
Date: Wed Oct 1 09:33:16 CST 2008
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
16 5 11 0 0
device_model 2 2 0 0 0
control_panel 20 15 5 0 0
acpi 5 5 0 0 0
gtest 22 22 0 0 0
====================================================================vtd
16 5 11 0 0
:two_dev_up_xp_nomsi_64_ 1 0 1 0 0
:lm_pcie_smp_nomsi_64_g3 1 0 1 0 0
:two_dev_smp_nomsi_64_g3 1 0 1 0 0
:two_dev_scp_64_g32e 1 1 0 0 0
:two_dev_up_64_g32e 1 1 0 0 0
:lm_pcie_up_xp_nomsi_64_ 1 0 1 0 0
:two_dev_up_nomsi_64_g32 1 1 0 0 0
:two_dev_smp_64_g32e 1 1 0 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
:lm_pcie_up_nomsi_64_g32 1 0 1 0 0
:two_dev_scp_nomsi_64_g3 1 1 0 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
device_model 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
control_panel 20 15 5 0 0
:XEN_1500M_guest_64_g32e 1 1 0 0 0
:XEN_4G_guest_64_g32e 1 1 0 0 0
:XEN_LM_Continuity_64_g3 1 0 1 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 0 1 0 0
:XEN_linux_win_64_g32e 1 1 0 0 0
:XEN_vmx_2vcpu_64_g32e 1 1 0 0 0
:XEN_four_dguest_co_64_g 1 1 0 0 0
:XEN_1500M_guest_64_gPAE 1 1 0 0 0
:XEN_two_winxp_64_g32e 1 1 0 0 0
:XEN_4G_guest_64_gPAE 1 1 0 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 0 1 0 0
:XEN_Nevada_xenu_64_g32e 1 0 1 0 0
:XEN_256M_guest_64_g32e 1 1 0 0 0
:XEN_SR_SMP_64_g32e 1 0 1 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
acpi 5 5 0 0 0
:check_c_residency_64_g3 1 1 0 0 0
:check_p_residency_64_g3 1 1 0 0 0
:check_c_trigger_64_g32e 1 1 0 0 0
:Dom0_S3_64_g32e 1 1 0 0 0
:check_p_trigger_64_g32e 1 1 0 0 0
gtest 22 22 0 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
:bootx_64_g32e 1 1 0 0 0
:boot_up_vista_64_g32e 1 1 0 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 1 0 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
====================================================================Total
65 49 16 0 0
-- haicheng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Cui, Dexuan
2008-Oct-07 09:07 UTC
[Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682
> 3. Guest will hang after Save/Restore. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339Changeset 18383(hvm: Use main memory for video memory) should bread the save/restore. Could Samuel or somebody have a look at it? Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Cui, Dexuan
2008-Oct-07 09:13 UTC
[Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682
Sorry, my typo. I meant "C/S 18383 should break the save/restore" . Thanks, -- Dexuan -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Cui, Dexuan Sent: 2008年10月7日 17:08 To: 'Samuel Thibault'; 'xen-devel@lists.xensource.com' Cc: Li, Haicheng Subject: [Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682> 3. Guest will hang after Save/Restore. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339Changeset 18383(hvm: Use main memory for video memory) should bread the save/restore. Could Samuel or somebody have a look at it? Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2008-Oct-07 09:31 UTC
Re: [Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682
On 7/10/08 10:07, "Cui, Dexuan" <dexuan.cui@intel.com> wrote:>> 3. Guest will hang after Save/Restore. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339 > Changeset 18383(hvm: Use main memory for video memory) should bread the > save/restore. > Could Samuel or somebody have a look at it?Samuel''s email address has changed (cc''ed). He''s also not working full-time on Xen any more. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Stefano Stabellini
2008-Oct-07 11:09 UTC
Re: [Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682
Cui, Dexuan wrote:>> 3. Guest will hang after Save/Restore. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339 > Changeset 18383(hvm: Use main memory for video memory) should bread the save/restore. > Could Samuel or somebody have a look at it? >Could you please give us more details on your testcase? I have just tried using xen-unstable (CS 18540) and qemu-remote (CS 97f134a499a92818cdd891e6ba2cb6b067dfc9d2) and seems to work fine. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Li, Haicheng
2008-Oct-09 06:01 UTC
RE: [Xen-devel] RE: Weekly VMX status report. Xen: #18560 & Xen0: #682
Stefano Stabellini wrote:> Cui, Dexuan wrote: > >>> 3. Guest will hang after Save/Restore. >>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1339 >> Changeset 18383(hvm: Use main memory for video memory) should bread >> the save/restore. Could Samuel or somebody have a look at it? >> > > Could you please give us more details on your testcase? > I have just tried using xen-unstable (CS 18540) and qemu-remote (CS > 97f134a499a92818cdd891e6ba2cb6b067dfc9d2) and seems to work fine.Stefano, We can steadily reproduce this S/R issue with Xen #18560 & ioemu-remote(c/s 0f3d6384d1b3d96476f78950b14040f9c1c63375). Our test has no special operation, just "live-migrate a hvm guest on local host" or "save a hvm guest and then restore it". I attached a guest config with this email, which is using qcow image (using real image also can meet same failure). -- haicheng _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Possibly Parallel Threads
- VMX status report. Xen: #17917 & Xen0: #583 -- no new issue
- Weekly VMX status report. Xen: #18132 & Xen0: #616
- VMX status report. Xen: #17062 & Xen0: #425 -- no new issue
- VMX status report. Xen: #17702 & Xen0: #559 -- no new issue
- VMX status report. Xen: #17714 & Xen0: #559 -- one new issue