From: "François Delawarde" <fdelawarde-SUMRa3zBIYkZJcOFZJ5hdAC/G2K4zDHf@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM Test result, kernel ff3784. .. , userspace 3a3429...
Date: Fri, 30 Nov 2007 14:12:20 +0100 [thread overview]
Message-ID: <47500C34.6050006@wirelessmundi.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A0271EB64-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hello,
I have a few different Intel and AMD architectures where I could run
automated tests like these.
Is there any possibility of downloading a shared test-suite (disk images
+ automated scripts) for people like me (newbies wanting to contribute,
at least with our spare CPU cycles) to be able to send equivalent
reports on other architectures on the mailing list?
I think it could be a great contribution for people having different
architecture/hardware to be able to send at least partial test-suite
results on every release, thus permitting developers to know the exact
setup and OS version (same test-suite). It might help identify
architecture specific, kernel specific or general issues on every kvm
version (and keep the "supported guests/hosts" wiki page up-to-date with
the last working version for a specific OS).
If there are licenses issues with Windows images, we could have a small
script (or a howto) for setting up a similar test suite with our own
licenses and Windows CDs!
Thanks,
François.
Zhao, Yunfeng wrote:
> -----Original Message-----
> From: Zhao, Yunfeng
> Sent: 2007年11月23日 16:46
> To: kvm-devel
> Subject: KVM Test result, kernel 51727a1.. , userspace 6a385c9..
>
> Hi, all,
>
> This is today's KVM test result against kvm.git ff378422888a8b3ff296e30297fcabf1c831ff83 and kvm-userspace.git 3a342937ce00c27b3eefd55032f261403b7ab5ab.
>
> One new issue:
> 1. Crashme causes RHEL5 guest kernel panic
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1840711&group_id=180599
>
> Old issues:
> 2. Timer of guest is inaccurate
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1826080&group_id=180599
> 3. Cannot install 64bit vista guests.
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1836905&group_id=180599
> 4. Fails to save/restore guests
> https://sourceforge.net/tracker/index.php?func=detail&aid=1824525&group_id=180599&atid=893831
> 5. xp and win2k3 guest crashes
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1819768&group_id=180599
> 6. xpsp2 with 2vpus may fail to boot
> https://sourceforge.net/tracker/index.php?func=detail&aid=1805017&group_id=180599&atid=893831
> 7. Cannot boot 32bit smp RHEL5.1 guest on 64bit host
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1812043&group_id=180599
>
>
> Test environment
> ================================================
>
> Platform woodcrest
> CPU 4
> Memory size 8G'
>
>
>
> Details
>
> ================================================
>
> PAE:
>
> 1. boot guest with 256M memory PASS
> 2. boot two windows xp guest PASS
> 3. boot 4 same guest in parallel PASS
> 4. boot linux and windows guest in parallel PASS
> 5. boot 4G linux guest PASS
> 6. boot guest with 1500M memory PASS
> 7. boot windows 2003 with ACPI enabled PASS
> 8. boot Windows xp with ACPI enabled PASS
> 9. boot Windows 2000 without ACPI PASS
> 10. kernel build on SMP linux guest PASS
> 11. LTP on SMP linux guest PASS
> 12. boot base kernel linux PASS
> 13. save/restore 32-bit HVM guests FAIL
> 14. live migration 32-bit HVM guests FAIL
> 15. boot SMP Windows xp with ACPI enabled FAIL
> 16. boot SMP windows 2003 with ACPI enabled FAIL
> 17. boot SMP Windows 2000 with ACPI enabled FAIL
>
>
> ================================================
>
> IA32e:
>
> 1. boot four 32-bit guest in parallel PASS
> 2. boot four 64-bit guest in parallel PASS
> 3. boot 4G 64-bit guest PASS
> 4. boot 4G pae guest PASS
> 5. boot 32-bit linux and 32 bit windows guest in parallel PASS
> 6. boot 32-bit guest with 1500M memory PASS
> 7. boot 64-bit guest with 1500M memory PASS
> 8. boot 32-bit guest with 256M memory PASS
> 9. boot 64-bit guest with 256M memory PASS
> 10. boot two 32-bit windows xp in parallel PASS
> 11. boot four 32-bit different guest in para PASS
> 12. save/restore 64-bit linux guests FAIL
> 13. save/restore 32-bit linux guests FAIL
> 14. boot 32-bit SMP windows 2003 with ACPI enabled PASS
> 15. boot 32bit SMP Windows 2000 with ACPI enabled FAIL
> 16. boot 32-bit SMP Windows xp with ACPI enabled FAIL
> 17. boot 32-bit Windows 2000 without ACPI PASS
> 18. boot 64-bit Windows xp with ACPI enabled PASS
> 19. boot 32-bit Windows xp without ACPI PASS
> 20. boot 64-bit vista PASS
> 21. kernel build in 32-bit linux guest OS PASS
> 22. kernel build in 64-bit linux guest OS PASS
> 23. LTP on SMP 32-bit linux guest OS PASS
> 24. LTP on SMP 64-bit linux guest OS PASS
> 25. boot 64-bit guests with ACPI enabled PASS
> 26. boot 32-bit x-server PASS
> 27. boot 64-bit SMP windows XP with ACPI enabled FAIL
> 28. boot 64-bit SMP windows 2003 with ACPI enabled PASS
>
>
>
> Report Summary on IA32-pae
>
> Summary Test Report of Last Session
> =====================================================================
> Total Pass Fail NoResult Crash
> =====================================================================
> control_panel 8 5 3 0 0
> Restart 2 2 0 0 0
> gtest 13 10 3 0 0
> =====================================================================
> control_panel 8 5 3 0 0
> :KVM_LM_PAE_gPAE 1 0 1 0 0
> :KVM_four_sguest_PAE_gPA 1 1 0 0 0
> :KVM_256M_guest_PAE_gPAE 1 1 0 0 0
> :KVM_linux_win_PAE_gPAE 1 1 0 0 0
> :KVM_1500M_guest_PAE_gPA 1 1 0 0 0
> :KVM_SR_PAE_gPAE 1 0 1 0 0
> :KVM_two_winxp_PAE_gPAE 1 1 0 0 0
> :KVM_4G_guest_PAE_gPAE 1 0 1 0 0
> Restart 2 2 0 0 0
> :GuestPAE_PAE_g64 1 1 0 0 0
> :BootTo32pae_PAE_g64 1 1 0 0 0
> gtest 13 10 3 0 0
> :ltp_nightly_PAE_gPAE 1 1 0 0 0
> :boot_up_acpi_PAE_gPAE 1 1 0 0 0
> :boot_up_vista_PAE_gPAE 1 1 0 0 0
> :boot_up_acpi_xp_PAE_gPA 1 1 0 0 0
> :boot_up_acpi_win2k3_PAE 1 1 0 0 0
> :boot_base_kernel_PAE_gP 1 1 0 0 0
> :boot_smp_acpi_win2k3_PA 1 0 1 0 0
> :boot_smp_acpi_win2k_PAE 1 0 1 0 0
> :boot_up_acpi_win2k_PAE_ 1 1 0 0 0
> :boot_smp_acpi_xp_PAE_gP 1 0 1 0 0
> :boot_up_noacpi_win2k_PA 1 1 0 0 0
> :bootx_PAE_gPAE 1 1 0 0 0
> :kb_nightly_PAE_gPAE 1 1 0 0 0
> =====================================================================
> Total 23 17 6 0 0
>
> Report Summary on IA32e
>
> Summary Test Report of Last Session
> =====================================================================
> Total Pass Fail NoResult Crash
> =====================================================================
> control_panel 15 11 4 0 0
> Restart 3 3 0 0 0
> gtest 22 16 6 0 0
> =====================================================================
> control_panel 15 11 4 0 0
> :KVM_LM_64_g64 1 0 1 0 0
> :KVM_four_sguest_64_gPAE 1 1 0 0 0
> :KVM_4G_guest_64_g64 1 1 0 0 0
> :KVM_four_sguest_64_g64 1 1 0 0 0
> :KVM_linux_win_64_gPAE 1 1 0 0 0
> :KVM_1500M_guest_64_gPAE 1 1 0 0 0
> :KVM_SR_64_g64 1 0 1 0 0
> :KVM_LM_64_gPAE 1 0 1 0 0
> :KVM_256M_guest_64_g64 1 1 0 0 0
> :KVM_1500M_guest_64_g64 1 1 0 0 0
> :KVM_4G_guest_64_gPAE 1 1 0 0 0
> :KVM_SR_64_gPAE 1 0 1 0 0
> :KVM_256M_guest_64_gPAE 1 1 0 0 0
> :KVM_two_winxp_64_gPAE 1 1 0 0 0
> :KVM_four_dguest_64_gPAE 1 1 0 0 0
> Restart 3 3 0 0 0
> :GuestPAE_64_gPAE 1 1 0 0 0
> :BootTo64_64_gPAE 1 1 0 0 0
> :Guest64_64_gPAE 1 1 0 0 0
> gtest 22 16 6 0 0
> :boot_up_acpi_64_gPAE 1 1 0 0 0
> :boot_up_noacpi_xp_64_gP 1 1 0 0 0
> :boot_smp_acpi_xp_64_g64 1 0 1 0 0
> :boot_base_kernel_64_gPA 1 1 0 0 0
> :boot_smp_acpi_win2k3_64 1 1 0 0 0
> :boot_smp_acpi_win2k_64_ 1 0 1 0 0
> :boot_base_kernel_64_g64 1 1 0 0 0
> :bootx_64_gPAE 1 1 0 0 0
> :kb_nightly_64_gPAE 1 1 0 0 0
> :ltp_nightly_64_g64 1 1 0 0 0
> :boot_up_acpi_64_g64 1 0 1 0 0
> :boot_up_noacpi_win2k_64 1 1 0 0 0
> :boot_smp_acpi_xp_64_gPA 1 0 1 0 0
> :boot_up_acpi_win2k3_64_ 1 1 0 0 0
> :bootx_64_g64 1 1 0 0 0
> :boot_up_vista_64_g64 1 0 1 0 0
> :boot_up_vista_64_gPAE 1 1 0 0 0
> :ltp_nightly_64_gPAE 1 1 0 0 0
> :boot_up_acpi_xp_64_g64 1 1 0 0 0
> :boot_smp_acpi_win2k3_64 1 0 1 0 0
> :boot_up_noacpi_win2k3_6 1 1 0 0 0
> :kb_nightly_64_g64 1 1 0 0 0
> =====================================================================
> Total 40 30 10 0 0
>
> Thanks
> Yunfeng
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
prev parent reply other threads:[~2007-11-30 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 7:15 KVM Test result, kernel ff3784. .. , userspace 3a3429 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A0271EB64-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-30 13:12 ` François Delawarde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47500C34.6050006@wirelessmundi.com \
--to=fdelawarde-sumra3zbiykzjcofzj5hdac/g2k4zdhf@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox