Li, Haicheng
2008-May-23 06:12 UTC
[Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- no new issue
Hi all,
This is today''s nightly testing report; no new issue found, bug #1259
got fixed.
Some vt-d cases failed in first round testing, but can get pass in
retesting.
Fixed issue:
=============================================1. booting windows guest causes Xen
HV crash
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259
Old issues:
=============================================1. linux guest kernel panic when
booting up with 4G memory.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255
2. On PAE host, Linux guest with vtd assignment becomes too slow to boot
up.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1225
3. xm console can not work after doing Save-Restore or Live-migration
one guest.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1256
4. Hvm windows guest shows abnormal color.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1180
5. dom0 hangs with io errors printed while booting hvm guest.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1243
Testing Environments:
=============================================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: 17702:2e6a51378451
Date: Fri May 23 11:00:48 CST 2008
1. 2 PAE SMP VMX domains and 2 xenU domains coexist PASS
2. Live and migration PASS
3. Save and Restore PASS
4. one PAE SMP Linux VMX domain with memory 256M PASS
5. one PAE SMP Linux VMX domain with memory 1500M PASS
6. one PAE SMP Linux VMX domain with memory 4G FAIL
7. boot 4 VMX per processor at the same time PASS
8. boot up 1 winXP VMX and 1 linux PAE VMX PASS
9. Single domain with single vcpu bind a CPU PASS
10. boot up two winXP per processor at the same time PASS
11. boot up one linux VMX with 4 vcpus PASS
12. boot up four linux VMX one by one PASS
13. boot up VMX with acpi=1, vcpu=1 PASS
14. subset LTP test in RHEL4U2 PAE SMP VMX domain PASS
15. Boot Linux 2.6.23 base kernel in RHEL4U1 PAE SMP Linux VMX domain
PASS
16. one IA32 UP ACPI Windows 2K VMX domain PASS
17. one IA32 UP ACPI Windows 2K3 VMX domain PASS
18. one IA32 UP ACPI Windows XP VMX domain PASS
19. one IA32 UP ACPI Vista VMX domain
PASS
20. one IA32 SMP ACPI Windows 2K VMX domain PASS
21. one IA32 SMP ACPI Windows 2K3 VMX domain PASS
22. one IA32 SMP ACPI Windows XP VMX domain PASS
23. one IA32 SMP ACPI Vista VMX domain
PASS
24. one IA32 UP NOACPI Windows 2K VMX domain PASS
25. one IA32 UP NOACPI Windows 2K3 VMX domain PASS
26. one IA32 UP NOACPI Windows XP VMX domain PASS
27. kernel build in one linux VMX PASS
28. startx in dom0 PASS
29. boot up one IA32 RHEL5u1 VMX domain. PASS
30. boot up one IA32 Fedora 7 VMX domain PASS
31. boot up one IA32 Fedora 8 VMX domain PASS
32. reboot Windows xp after it boot up. PASS
33. reboot Fedora core 6 after it boot up. PASS
34. VBD and VNIF works on UP VMX domain PASS
35. VBD and VNIF works on SMP VMX domain PASS
36. assign one pcie nic to one UP Linux guest with vtd. PASS
37. assign one pcie nic to one SMP Linux guest with vtd. PASS
38. assign one pcie nic to one UP WinXP guest with vtd. PASS
39. assign one pci nic to one SMP Linux guest with vtd. FAIL
40. assign one pci nic to one UP WinXP guest with vtd. PASS
41. assign one pci nic to one UP Linux guest with vtd PASS
42. assign one pcie nic to one SMP WinXP guest with vtd.
PASS
43. assign one pci nic to one SMP WinXP guest with vtd.
PASS
44. scp a big file in Linux guest via the pci nic assigned with vt-d.
PASS
45. scp a big file in Linux guest via the pcie nic assigned with vt-d.
PASS
46. hotplug one pcie nic to one UP Linux guest with vtd. PASS
47. hotplug one pcie nic to one SMP Linux guest with vtd. PASS
48. hotplug one pcie nic to one UP WinXP guest with vtd. PASS
49. hotplug one pci nic to one SMP Linux guest with vtd. PASS
50. hotplug one pci nic to one UP WinXP guest with vtd. PASS
51. hotplug one pci nic to one UP Linux guest with vtd PASS
52. hotplug one pcie nic to one SMP WinXP guest with vtd.
PASS
53. hotplug one pci nic to one SMP WinXP guest with vtd.
PASS
54. live-migrate one UP Linux guest with one vtd pcie nic assigned.
PASS
55. live-migrate one SMP Linux guest with one vtd pcie nic assigned.
PASS
56. live-migrate one UP WinXP guest with one vtd pcie nic assigned.
PASS
57. live-migrate one SMP Linux guest with one vtd pci nic assigned.
PASS
58. live-migrate one UP WinXP guest with one vtd pci nic assigned.
PASS
59. live-migrate one UP Linux guest with one vtd pci nic assigned.
PASS
60. live-migrate one SMP WinXP guest with one vtd pcie nic assigned.
PASS
61. live-migrate one SMP WinXP guest with one vtd pci nic assigned.
PASS
62. boot up one IA32 Solaris PV domain for XenU FAIL
63. boot up one IA32 Solaris VMX domain PASS
64. one IA32 UP ACPI Windows 2K8 VMX domain PASS
65. one IA32 SMP ACPI Windows 2K8 VMX domain PASS
66. Save and Restore one SMP linux domain PASS
67. Live and migrate one SMP linux domain PASS
68. Dom0 does S3 for one time PASS
Platform : PAE
Service OS : Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Hardware : Clovertown
Xen package: 17702:2e6a51378451
Date: Fri May 23 11:00:48 CST 2008
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
26 17 9 0 0
device_model 2 2 0 0 0
control_panel 15 13 2 0 0
acpi 1 1 0 0 0
Restart 2 2 0 0 0
gtest 24 24 0 0 0
====================================================================vtd
26 17 9 0 0
:one_pci_smp_xp_PAE_gPAE 1 0 1 0 0
:hp_pcie_up_PAE_gPAE 1 0 1 0 0
:hp_pcie_up_xp_PAE_gPAE 1 0 1 0 0
:one_pci_smp_PAE_gPAE 1 0 1 0 0
:one_pcie_smp_PAE_gPAE 1 0 1 0 0
:hp_pci_up_xp_PAE_gPAE 1 1 0 0 0
:hp_pci_smp_xp_PAE_gPAE 1 1 0 0 0
:lm_pcie_smp_xp_PAE_gPAE 1 1 0 0 0
:one_pcie_up_PAE_gPAE 1 1 0 0 0
:one_pci_up_PAE_gPAE 1 1 0 0 0
:lm_pcie_up_PAE_gPAE 1 1 0 0 0
:one_pcie_scp_PAE_gPAE 1 1 0 0 0
:one_pcie_up_xp_PAE_gPAE 1 1 0 0 0
:hp_pcie_smp_xp_PAE_gPAE 1 1 0 0 0
:hp_pcie_smp_PAE_gPAE 1 0 1 0 0
:lm_pci_smp_PAE_gPAE 1 0 1 0 0
:one_pci_up_xp_PAE_gPAE 1 1 0 0 0
:one_pcie_smp_xp_PAE_gPA 1 1 0 0 0
:one_pci_scp_PAE_gPAE 1 1 0 0 0
:lm_pcie_smp_PAE_gPAE 1 1 0 0 0
:lm_pcie_up_xp_PAE_gPAE 1 1 0 0 0
:hp_pci_up_PAE_gPAE 1 1 0 0 0
:lm_pci_up_xp_PAE_gPAE 1 1 0 0 0
:hp_pci_smp_PAE_gPAE 1 1 0 0 0
:lm_pci_up_PAE_gPAE 1 0 1 0 0
:lm_pci_smp_xp_PAE_gPAE 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 13 2 0 0
:XEN_4G_guest_PAE_gPAE 1 0 1 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 1 0 0 0
:XEN_Nevada_xenu_PAE_gPA 1 0 1 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_two_winxp_PAE_gPAE 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_vmx_2vcpu_PAE_gPAE 1 1 0 0 0
:XEN_four_sguest_seq_PAE 1 1 0 0 0
acpi 1 1 0 0 0
:Dom0_S3_PAE_gPAE 1 1 0 0 0
Restart 2 2 0 0 0
:GuestPAE_PAE_gPAE 1 1 0 0 0
:SolarisPAE_PAE_gPAE 1 1 0 0 0
gtest 24 24 0 0 0
:boot_fc7_PAE_gPAE 1 1 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_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_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
:boot_fc8_PAE_gPAE 1 1 0 0 0
:kb_nightly_PAE_gPAE 1 1 0 0 0
====================================================================Total
70 59 11 0 0
Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
Xen package: 17702:2e6a51378451
Date: Fri May 23 10:24:01 CST 2008
1. boot up four PAE linux VMX one by one
PASS
2. one PAE xenU domain with memory 256M PASS
3. one PAE SMP Linux VMX domain with memory 1500M PASS
4. one PAE SMP Linux VMX domain with memory 4G FAIL
5. one PAE SMP Linux VMX domain with memory 256M PASS
6. 2 ia32E SMP VMX domains and 2 xenU domains coexist PASS
7. Live and migration PASS
8. Save and Restore PASS
9. one ia32E SMP Linux VMX domain with memory 1500M PASS
10. one ia32E SMP Linux VMX domain with memory 4G
FAIL
11. one ia32E SMP Linux VMX domain with memory 256M PASS
12. boot 4 VMX per processor at the same time PASS
13. boot up 1 winXP VMX and 1 linux VMX PASS
14. Single domain with single vcpu bind a CPU PASS
15. boot up two winXP per processor at the same time PASS
16. boot up one linux VMX with 4 vcpus PASS
17. boot up four linux VMX one by one PASS
18. Boot up VMX with acpi=1, vcpu=1 PASS
19. subset LTP test in RHEL4U2 ia32E SMP VMX domain PASS
20. one IA32E UP ACPI Windows 2K3 VMX domain PASS
21. one IA32E UP ACPI Windows 2K VMX domain PASS
22. one IA32E UP ACPI Windows XP VMX domain PASS
23. one IA32E UP ACPI Vista VMX domain
PASS
24. one IA32E SMP ACPI Windows 2K3 VMX domain PASS
25. one IA32E SMP ACPI Windows 2K VMX domain PASS
26. one IA32E SMP ACPI Windows XP VMX domain PASS
27. one IA32E SMP ACPI Vista VMX domain
PASS
28. one IA32E UP NOACPI Windows 2K VMX domain PASS
29. boot Linux 2.6.23 base kernel in ia32E SMP Linux VMX domain PASS
30. kernel build in one ia32E linux VMX PASS
31. startx in dom0 PASS
32. boot up one IA32E RHEL5u1 VMX domain. PASS
33. boot up one IA32E Fedora 7 VMX domain PASS
34. boot up one IA32E Fedora 8 VMX domain PASS
35. reboot Windows xp after it boot up. PASS
36. reboot Fedora core 6 after it boot up. PASS
37. VBD and VNIF works on UP VMX domain PASS
38. VBD and VNIF works on SMP VMX domain PASS
39. boot up one IA32E Solaris PV domain for XenU PASS
40. boot up one IA32E Solaris VMX domain PASS
41. assign one pcie nic to one UP Linux guest with vtd. PASS
42. assign one pcie nic to one SMP Linux guest with vtd. FAIL
43. assign one pcie nic to one UP WinXP guest with vtd. PASS
44. assign one pci nic to one SMP Linux guest with vtd. FAIL
45. assign one pci nic to one UP WinXP guest with vtd. PASS
46. assign one pci nic to one UP Linux guest with vtd PASS
47. assign one pcie nic to one SMP WinXP guest with vtd.
PASS
48. assign one pci nic to one SMP WinXP guest with vtd.
FAIL
49. scp a big file in Linux guest via the pci nic assigned with vt-d.
PASS
50. scp a big file in Linux guest via the pcie nic assigned with vt-d.
PASS
51. hotplug one pcie nic to one UP Linux guest with vtd. FAIL
52. hotplug one pcie nic to one SMP Linux guest with vtd. PASS
53. hotplug one pcie nic to one UP WinXP guest with vtd. FAIL
54. hotplug one pci nic to one SMP Linux guest with vtd. FAIL
55. hotplug one pci nic to one UP WinXP guest with vtd. PASS
56. hotplug one pci nic to one UP Linux guest with vtd PASS
57. hotplug one pcie nic to one SMP WinXP guest with vtd.
PASS
58. hotplug one pci nic to one SMP WinXP guest with vtd.
PASS
59. live-migrate one UP Linux guest with one vtd pcie nic assigned.
PASS
60. live-migrate one SMP Linux guest with one vtd pcie nic assigned.
PASS
61. live-migrate one UP WinXP guest with one vtd pcie nic assigned.
PASS
62. live-migrate one SMP Linux guest with one vtd pci nic assigned.
FAIL
63. live-migrate one UP WinXP guest with one vtd pci nic assigned.
PASS
64. live-migrate one UP Linux guest with one vtd pci nic assigned.
FAIL
65. live-migrate one SMP WinXP guest with one vtd pcie nic assigned.
FAIL
66. live-migrate one SMP WinXP guest with one vtd pci nic assigned.
PASS
67. one IA32E UP ACPI Windows 2K8 VMX domain PASS
68. one IA32E SMP ACPI Windows 2K8 VMX domain PASS
69. Save and Restore one SMP linux domain PASS
70. Live and migrate one SMP linux domain PASS
71. Dom0 does S3 for one time PASS
Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
Xen package: 17702:2e6a51378451
Date: Fri May 23 10:24:01 CST 2008
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
26 19 7 0 0
device_model 2 2 0 0 0
control_panel 20 18 2 0 0
acpi 1 1 0 0 0
Restart 3 3 0 0 0
gtest 22 22 0 0 0
====================================================================vtd
26 19 7 0 0
:one_pci_up_64_g32e 1 1 0 0 0
:one_pcie_up_xp_64_g32e 1 0 1 0 0
:hp_pcie_smp_xp_64_g32e 1 1 0 0 0
:lm_pcie_up_64_g32e 1 1 0 0 0
:lm_pci_smp_xp_64_g32e 1 1 0 0 0
:hp_pci_smp_64_g32e 1 0 1 0 0
:one_pcie_smp_xp_64_g32e 1 0 1 0 0
:lm_pcie_up_xp_64_g32e 1 1 0 0 0
:hp_pcie_smp_64_g32e 1 1 0 0 0
:lm_pci_up_64_g32e 1 1 0 0 0
:one_pci_smp_xp_64_g32e 1 1 0 0 0
:lm_pci_up_xp_64_g32e 1 0 1 0 0
:one_pci_scp_64_g32e 1 1 0 0 0
:lm_pcie_smp_xp_64_g32e 1 1 0 0 0
:one_pcie_up_64_g32e 1 1 0 0 0
:lm_pcie_smp_64_g32e 1 1 0 0 0
:hp_pcie_up_xp_64_g32e 1 1 0 0 0
:one_pci_smp_64_g32e 1 1 0 0 0
:hp_pci_up_64_g32e 1 1 0 0 0
:lm_pci_smp_64_g32e 1 0 1 0 0
:one_pcie_scp_64_g32e 1 1 0 0 0
:hp_pci_up_xp_64_g32e 1 0 1 0 0
:hp_pci_smp_xp_64_g32e 1 0 1 0 0
:one_pci_up_xp_64_g32e 1 1 0 0 0
:one_pcie_smp_64_g32e 1 1 0 0 0
:hp_pcie_up_64_g32e 1 1 0 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 18 2 0 0
:XEN_1500M_guest_64_g32e 1 1 0 0 0
:XEN_4G_guest_64_g32e 1 0 1 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_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 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
acpi 1 1 0 0 0
:Dom0_S3_64_g32e 1 1 0 0 0
Restart 3 3 0 0 0
:GuestPAE_64_gPAE 1 1 0 0 0
:Solaris64_64_g32e 1 1 0 0 0
:Guest64_64_gPAE 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
:boot_fc7_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_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_smp_win2008_64_g32 1 1 0 0 0
:boot_fc8_64_g32e 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
74 65 9 0 0
-- haicheng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2008-May-23 07:53 UTC
Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- no new issue
On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com> wrote:> Old issues: > =============================================> 1. linux guest kernel panic when booting up with 4G memory. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255Can you provide more info on this one? Linux version, configuration, etc? And/or send me the vmlinux/bzImage files privately to try to repro. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Xu, Dongxiao
2008-May-23 08:06 UTC
RE: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue
Hi, Keir,
This issue is caused by the 2MB superpage patch in Xen C/S 17645. It seems
that any linux guest (hap=0, using shadow) with more than 4G memory will fail to
boot (4095M memory can boot successful). I haven''t tried EPT guest.
-- Dongxiao
-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
Sent: 2008年5月23日 15:54
To: Li, Haicheng; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 --
nonew issue
On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com> wrote:
> Old issues:
> =============================================> 1. linux guest kernel
panic when booting up with 4G memory.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255
Can you provide more info on this one? Linux version, configuration, etc?
And/or send me the vmlinux/bzImage files privately to try to repro.
-- Keir
_______________________________________________
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-May-23 08:25 UTC
Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue
That means I broke memory allocation when I cleaned up the tools side of that patch. I will look into it and fix it. -- Keir On 23/5/08 09:06, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote:> Hi, Keir, > This issue is caused by the 2MB superpage patch in Xen C/S 17645. It seems > that any linux guest (hap=0, using shadow) with more than 4G memory will fail > to boot (4095M memory can boot successful). I haven''t tried EPT guest. > > -- Dongxiao > > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: 2008年5月23日 15:54 > To: Li, Haicheng; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew > issue > > On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com> wrote: > >> Old issues: >> =============================================>> 1. linux guest kernel panic when booting up with 4G memory. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255 > > Can you provide more info on this one? Linux version, configuration, etc? > And/or send me the vmlinux/bzImage files privately to try to repro. > > -- Keir > > > > _______________________________________________ > 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
Xu, Dongxiao
2008-May-23 08:37 UTC
RE: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue
Hi, Keir,
I think the problem may be not in the tools side, but in the shadow side. I
ever removed the shadow 2MB superpage support code in p2m.c, and the Linux guest
(hap=0, using shadow) can boot successful with more than 4G memory.
Thanks!
-- Dongxiao
-----Original Message-----
From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
Sent: 2008年5月23日 16:26
To: Xu, Dongxiao; Li, Haicheng; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 --
nonew issue
That means I broke memory allocation when I cleaned up the tools side of
that patch. I will look into it and fix it.
-- Keir
On 23/5/08 09:06, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote:
> Hi, Keir,
> This issue is caused by the 2MB superpage patch in Xen C/S 17645. It
seems
> that any linux guest (hap=0, using shadow) with more than 4G memory will
fail
> to boot (4095M memory can boot successful). I haven''t tried EPT
guest.
>
> -- Dongxiao
>
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
> Sent: 2008年5月23日 15:54
> To: Li, Haicheng; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 --
nonew
> issue
>
> On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com>
wrote:
>
>> Old issues:
>> =============================================>> 1. linux guest
kernel panic when booting up with 4G memory.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255
>
> Can you provide more info on this one? Linux version, configuration, etc?
> And/or send me the vmlinux/bzImage files privately to try to repro.
>
> -- Keir
>
>
>
> _______________________________________________
> 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-May-23 08:45 UTC
Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue
Okay, I have failed to repro this issue, but my test machine does not have 4G of memory, so I created a low-memory/high-memory split by placing the start of the MMIO ''hole'' at 256MB rather than the usual 3.75GB. Doing this, for a 512MB Linux guest, did not cause the guest to crash. So I guess either you really do need to give the guest >4GB of RAM (i.e., it''s not a split-across-the-MMIO-hole bug) and/or it''s related to usage of EPT? At least it looks like this one is not *my* bug. :-) -- Keir On 23/5/08 09:37, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote:> Hi, Keir, > I think the problem may be not in the tools side, but in the shadow side. > I ever removed the shadow 2MB superpage support code in p2m.c, and the Linux > guest (hap=0, using shadow) can boot successful with more than 4G memory. > > Thanks! > -- Dongxiao > > -----Original Message----- > From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] > Sent: 2008年5月23日 16:26 > To: Xu, Dongxiao; Li, Haicheng; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew > issue > > That means I broke memory allocation when I cleaned up the tools side of > that patch. I will look into it and fix it. > > -- Keir > > On 23/5/08 09:06, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote: > >> Hi, Keir, >> This issue is caused by the 2MB superpage patch in Xen C/S 17645. It >> seems >> that any linux guest (hap=0, using shadow) with more than 4G memory will fail >> to boot (4095M memory can boot successful). I haven''t tried EPT guest. >> >> -- Dongxiao >> >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser >> Sent: 2008年5月23日 15:54 >> To: Li, Haicheng; xen-devel@lists.xensource.com >> Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew >> issue >> >> On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com> wrote: >> >>> Old issues: >>> =============================================>>> 1. linux guest kernel panic when booting up with 4G memory. >>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255 >> >> Can you provide more info on this one? Linux version, configuration, etc? >> And/or send me the vmlinux/bzImage files privately to try to repro. >> >> -- Keir >> >> >> >> _______________________________________________ >> 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-May-23 08:51 UTC
Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew issue
One thought: in c/s 17690 Xin Xiaohui fixed superpage shattering in EPT tables. Could there be a similar bug relating to superpage shattering in the ordinary (non-EPT) p2m logic? -- Keir On 23/5/08 09:45, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:> Okay, I have failed to repro this issue, but my test machine does not have > 4G of memory, so I created a low-memory/high-memory split by placing the > start of the MMIO ''hole'' at 256MB rather than the usual 3.75GB. Doing this, > for a 512MB Linux guest, did not cause the guest to crash. So I guess either > you really do need to give the guest >4GB of RAM (i.e., it''s not a > split-across-the-MMIO-hole bug) and/or it''s related to usage of EPT? > > At least it looks like this one is not *my* bug. :-) > > -- Keir > > On 23/5/08 09:37, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote: > >> Hi, Keir, >> I think the problem may be not in the tools side, but in the shadow side. >> I ever removed the shadow 2MB superpage support code in p2m.c, and the Linux >> guest (hap=0, using shadow) can boot successful with more than 4G memory. >> >> Thanks! >> -- Dongxiao >> >> -----Original Message----- >> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] >> Sent: 2008年5月23日 16:26 >> To: Xu, Dongxiao; Li, Haicheng; xen-devel@lists.xensource.com >> Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- nonew >> issue >> >> That means I broke memory allocation when I cleaned up the tools side of >> that patch. I will look into it and fix it. >> >> -- Keir >> >> On 23/5/08 09:06, "Xu, Dongxiao" <dongxiao.xu@intel.com> wrote: >> >>> Hi, Keir, >>> This issue is caused by the 2MB superpage patch in Xen C/S 17645. It >>> seems >>> that any linux guest (hap=0, using shadow) with more than 4G memory will >>> fail >>> to boot (4095M memory can boot successful). I haven''t tried EPT guest. >>> >>> -- Dongxiao >>> >>> -----Original Message----- >>> From: xen-devel-bounces@lists.xensource.com >>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser >>> Sent: 2008年5月23日 15:54 >>> To: Li, Haicheng; xen-devel@lists.xensource.com >>> Subject: Re: [Xen-devel] VMX status report. Xen: #17702 & Xen0: #559 -- >>> nonew >>> issue >>> >>> On 23/5/08 07:12, "Li, Haicheng" <haicheng.li@intel.com> wrote: >>> >>>> Old issues: >>>> =============================================>>>> 1. linux guest kernel panic when booting up with 4G memory. >>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1255 >>> >>> Can you provide more info on this one? Linux version, configuration, etc? >>> And/or send me the vmlinux/bzImage files privately to try to repro. >>> >>> -- Keir >>> >>> >>> >>> _______________________________________________ >>> 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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Apparently Analagous Threads
- VMX status report. Xen: #17270 & Xen0: #488 -- no new issue
- VMX status report. Xen: #17917 & Xen0: #583 -- no new issue
- VMX status report. Xen: #17714 & Xen0: #559 -- one new issue
- Weekly VMX status report. Xen: #18132 & Xen0: #616
- VMX status report. Xen: #17062 & Xen0: #425 -- no new issue