Li, Haicheng
2008-Apr-23 09:59 UTC
[Xen-devel] VMX status report. Xen: #17501 & Xen0: #524 -- two new issues
Hi all,
This is today''s nightly testing report; two new issue found and one old
issue got fixed.
Due to bug 1221 listed below, testing on PAE host is blocked.
New issues:
=============================================1. Fail to create any HVM guest on
IA32PAE host
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1221
2. Dom0 hangs at booting if loglvl and guest_loglvl are set as all.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1222
Fixed issue:
=============================================1. Xen HV hangs at booting on 32PAE
host if vtd is enabled.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1211
Old issues:
=============================================1. Hvm windows guest shows abnormal
color.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1180
2. XenU guest will hang if booted just after destorying a HVM guest.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1139
3. Hvm guest with generic kernel 2.6.18 cannot boot up.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1196..
Testing Environments:
=============================================PAE
CPU : Xeon(r) processor 5300 series
Dom0 OS : FC6
Memory size : 8G
IA32E
CPU : Xeon(r) processor 5300 series
Dom0 OS : RHEL5
Memory size : 8G
Details:
=============================================Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
Xen package: 17501:2ebb7f79e3bb
Date: Wed Apr 23 08:45:40 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 PASS
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 FAIL
8. Save and Restore FAIL
9. one ia32E SMP Linux VMX domain with memory 1500M PASS
10. one ia32E SMP Linux VMX domain with memory 4G
PASS
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. FAIL
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. assign one pcie nic to one UP Linux guest with vtd. PASS
40. assign one pcie nic to one SMP Linux guest with vtd. PASS
41. assign one pcie nic to one UP WinXP guest with vtd. PASS
42. assign one pci nic to one SMP Linux guest with vtd. PASS
43. assign one pci nic to one UP WinXP guest with vtd. PASS
44. assign one pci nic to one UP Linux guest with vtd PASS
45. scp a big file in Linux guest via the pci nic assigned with vt-d.
FAIL
46. assign one pcie nic to one SMP WinXP guest with vtd.
PASS
47. assign one pci nic to one SMP WinXP guest with vtd.
FAIL
48. scp a big file in Linux guest via the pcie nic assigned with vt-d.
PASS
49. hotplug one pcie nic to one UP Linux guest with vtd. PASS
50. hotplug one pcie nic to one SMP Linux guest with vtd. PASS
51. hotplug one pcie nic to one UP WinXP guest with vtd. PASS
52. hotplug one pci nic to one SMP Linux guest with vtd. PASS
53. hotplug one pci nic to one UP WinXP guest with vtd. PASS
54. hotplug one pci nic to one UP Linux guest with vtd PASS
55. hotplug one pcie nic to one SMP WinXP guest with vtd.
PASS
56. hotplug one pci nic to one SMP WinXP guest with vtd.
PASS
57. boot up one IA32E Solaris PV domain for XenU FAIL
58. boot up one IA32E Solaris VMX domain PASS
Platform : x86_64
Service OS : Red Hat Enterprise Linux Server release 5 (Tikanga)
Hardware : Clovertown
Xen package: 17501:2ebb7f79e3bb
Date: Wed Apr 23 08:45:40 CST 2008
Summary Test Report of Last Session
====================================================================
Total Pass Fail NoResult Crash
====================================================================vtd
18 16 2 0 0
device_model 2 2 0 0 0
control_panel 18 15 3 0 0
Restart 3 3 0 0 0
gtest 20 19 1 0 0
====================================================================vtd
18 16 2 0 0
:one_pcie_smp_xp_64_g64 1 1 0 0 0
:one_pcie_up_xp_64_g64 1 1 0 0 0
:one_pcie_scp_64_g64 1 1 0 0 0
:hp_pci_xp_up_64_g64 1 1 0 0 0
:one_pci_smp_64_g64 1 1 0 0 0
:hp_pci_xp_smp_64_g64 1 1 0 0 0
:hp_pci_up_64_g64 1 1 0 0 0
:hp_pcie_smp_64_g64 1 1 0 0 0
:one_pci_up_64_g64 1 1 0 0 0
:one_pci_smp_xp_64_g64 1 0 1 0 0
:one_pcie_up_64_g64 1 1 0 0 0
:hp_pci_smp_64_g64 1 1 0 0 0
:hp_pcie_xp_smp_64_g64 1 1 0 0 0
:one_pci_up_xp_64_g64 1 1 0 0 0
:one_pci_scp_64_g64 1 0 1 0 0
:hp_pcie_up_64_g64 1 1 0 0 0
:one_pcie_smp_64_g64 1 1 0 0 0
:hp_pcie_xp_up_64_g64 1 1 0 0 0
device_model 2 2 0 0 0
:pv_on_smp_64_g64 1 1 0 0 0
:pv_on_up_64_g64 1 1 0 0 0
control_panel 18 15 3 0 0
:XEN_1500M_guest_64_g64 1 1 0 0 0
:XEN_Nevada_xenu_64_g64 1 0 1 0 0
:XEN_256M_xenu_64_gPAE 1 1 0 0 0
:XEN_1500M_guest_64_gPAE 1 1 0 0 0
:XEN_4G_guest_64_gPAE 1 1 0 0 0
:XEN_256M_guest_64_g64 1 1 0 0 0
:XEN_SR_64_g64 1 0 1 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_vmx_2vcpu_64_g64 1 1 0 0 0
:XEN_vmx_vcpu_pin_64_g64 1 1 0 0 0
:XEN_linux_win_64_g64 1 1 0 0 0
:XEN_256M_guest_64_gPAE 1 1 0 0 0
:XEN_LM_64_g64 1 0 1 0 0
:XEN_two_winxp_64_g64 1 1 0 0 0
:XEN_four_vmx_xenu_seq_6 1 1 0 0 0
:XEN_four_sguest_seq_64_ 1 1 0 0 0
:XEN_4G_guest_64_g64 1 1 0 0 0
:XEN_four_dguest_co_64_g 1 1 0 0 0
Restart 3 3 0 0 0
:Guest64_64_gPAE 1 1 0 0 0
:Solaris64_64_g64 1 1 0 0 0
:GuestPAE_64_g64 1 1 0 0 0
gtest 20 19 1 0 0
:boot_smp_acpi_xp_64_g64 1 1 0 0 0
:boot_fc7_64_g64 1 1 0 0 0
:boot_base_kernel_64_g64 1 1 0 0 0
:ltp_nightly_64_g64 1 1 0 0 0
:boot_up_acpi_64_g64 1 1 0 0 0
:boot_up_acpi_win2k3_64_ 1 1 0 0 0
:boot_fc8_64_g64 1 1 0 0 0
:bootx_64_g64 1 1 0 0 0
:boot_nevada_64_g64 1 1 0 0 0
:reboot_xp_64_g64 1 0 1 0 0
:boot_smp_acpi_win2k_64_ 1 1 0 0 0
:boot_up_vista_64_g64 1 1 0 0 0
:boot_up_noacpi_win2k_64 1 1 0 0 0
:boot_smp_vista_64_g64 1 1 0 0 0
:boot_up_acpi_win2k_64_g 1 1 0 0 0
:reboot_fc6_64_g64 1 1 0 0 0
:boot_up_acpi_xp_64_g64 1 1 0 0 0
:boot_smp_acpi_win2k3_64 1 1 0 0 0
:boot_rhel5u1_64_g64 1 1 0 0 0
:kb_nightly_64_g64 1 1 0 0 0
====================================================================Total
61 55 6 0 0
-- haicheng
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2008-Apr-23 12:18 UTC
Re: [Xen-devel] VMX status report. Xen: #17501 & Xen0: #524 -- two new issues
On 23/4/08 10:59, "Li, Haicheng" <haicheng.li@intel.com> wrote:> 1. Fail to create any HVM guest on IA32PAE host > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1221Looks like it is due to Kevin Wolf''s changeset 17499. Your attempt to go back to older tools obviously didn''t work -- the backtrace in xend.log comes from a line introduced by c/s 17499.> 2. Dom0 hangs at booting if loglvl and guest_loglvl are set as all. > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1222Well, the obvious answer is to print less drivel in the VT-d code. There''s no reason at all to print so much useless text, even in a debug build. Actually a second point is that we should drop characters from the 16kB serial buffer rather than spin in the hypervisor waiting for the buffer to empty. I''ll implement that. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2008-Apr-23 13:27 UTC
Re: [Xen-devel] VMX status report. Xen: #17501 & Xen0: #524 -- two new issues
These issues are now all resolved: On 23/4/08 13:18, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:>> 1. Fail to create any HVM guest on IA32PAE host >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1221 > > Looks like it is due to Kevin Wolf''s changeset 17499. Your attempt to go > back to older tools obviously didn''t work -- the backtrace in xend.log comes > from a line introduced by c/s 17499.I reverted this changeset.>> 2. Dom0 hangs at booting if loglvl and guest_loglvl are set as all. >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1222 > > Well, the obvious answer is to print less drivel in the VT-d code. There''s > no reason at all to print so much useless text, even in a debug build.I greatly reduced printk() count in vtd code. If this stuff was useful for debugging (which for the most part it probably wasn''t) you might add it back via an ifdef''ed debug macro.> Actually a second point is that we should drop characters from the 16kB > serial buffer rather than spin in the hypervisor waiting for the buffer to > empty. I''ll implement that.This is now done. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Kevin Wolf
2008-Apr-23 13:41 UTC
[Xen-devel] [PATCH] xend: Create /var/run/tap during device model setup
Keir Fraser schrieb:> On 23/4/08 10:59, "Li, Haicheng" <haicheng.li@intel.com> wrote: > >> 1. Fail to create any HVM guest on IA32PAE host >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1221 > > Looks like it is due to Kevin Wolf''s changeset 17499. Your attempt to go > back to older tools obviously didn''t work -- the backtrace in xend.log comes > from a line introduced by c/s 17499.Create the directory /var/run/tap if it doesn''t exist yet. Try to continue even if the blktap communication pipes couldn''t be created. The VM might not need tap:ioemu and run just fine. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel