All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Xen Developers <xen-devel@lists.xensource.com>
Subject: Daily Xen-HVM Builds: cs9920
Date: Wed, 03 May 2006 20:21:10 -0500	[thread overview]
Message-ID: <44595706.3070905@us.ibm.com> (raw)

changeset:   9920:915d5af5dc18
tag:         tip
user:        kaf24@firebug.cl.cam.ac.uk
date:        Wed May  3 07:33:01 2006 +0100
summary:     Fix mismerge of vmx vm86 patch: 
9915:e1409c2ace46afd67b54de1f5c0b2b6d3721ca3b


Hardware:  x460

******************** x86_32(no PAE): ***************************

* dom0: SLES9 SP2
* dom0 boots fine
* xend starts without problem

--- Linux HVM domain status: ---

* Xm-test completes.
* Able to boot multiple HVM domains

ISSUES:

* 5 fails on xm-test.

SUMMARY:

Xm-test execution summary:
   PASS:  71
   FAIL:  5
   XPASS: 2
   XFAIL: 1


Details:

  FAIL: 11_create_concurrent_pos
          [2] Failed to create domain

  FAIL: 12_create_concurrent_stress_pos
          Failed to start 12_create_concurrent_stress_pos-1146671800

  FAIL: 16_create_smallmem_neg
          Starting a console with 16 MB passed, expected test to fail

  FAIL: 01_enforce_dom0_cpus_basic_pos
          /proc/cpuinfo says xend didn't enforce dom0_cpus (13 != 1)

XFAIL: 02_network_local_ping_pos
          ping loopback failed for size 65507. ping eth0 failed for size 
65507.



--- Windows HVM domain status: ---

* I'll get to testing the other Windowns OS when I automate the test cases.

+------------------------------------+
|    Test    |            OS         |
| Category   |-----------------------|
|            | Win2k| Win2k3 | WinXP |
+------------------------------------+
| Networking |      |        | pass  |
| Graphics   |      |        | pass  |
| Disk I/O   |      |        | pass  |
| Xen        |      |        | N/A   |
+------------------------------------+

ISSUES:

None

********************** x86_64: *********************************

* dom0: SLES9 SP2
* dom0 boots fine
* xend starts without problems

--- Linux HVM domain status: ---

* Xm-test completes
* Able to boot multiple HVM domains

ISSUES:

* 3 xm-tests failing

SUMMERY:
Xm-test execution summary:
   PASS:  73
   FAIL:  3
   XPASS: 2
   XFAIL: 1


Details:

  FAIL: 16_create_smallmem_neg
          Starting a console with 16 MB passed, expected test to fail

  FAIL: 01_enforce_dom0_cpus_basic_pos
          /proc/cpuinfo says xend didn't enforce dom0_cpus (16 != 1)

XFAIL: 02_network_local_ping_pos
          ping loopback failed for size 65507. ping eth0 failed for size 
65507.



--- Windows HVM domain status: ---


+------------------------------------+
|    Test    |            OS         |
| Category   |-----------------------|
|            | Win2k| Win2k3 | WinXP |
+------------------------------------+
| Networking |      |        | pass  |
| Graphics   |      |        | pass  |
| Disk I/O   |      |        | pass  |
| Xen        |      |        | N/A   |
+------------------------------------+


ISSUES:

none


NOTE: Contact me if you would like to see all the output files.



regards,



------------------------
Rick Gonzalez
Linux Technology Center
IBM Corporation
Phone#: 512-838-0623

                 reply	other threads:[~2006-05-04  1:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44595706.3070905@us.ibm.com \
    --to=rcgneo@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.