WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] Update xm-test

To: Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
Subject: Re: [XenPPC] Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] Update xm-test to support new architectures
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Sun, 1 Oct 2006 21:04:18 -0400
Cc: XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 01 Oct 2006 18:04:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061001063016.GX27551@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1159527414@xxxxxxxxxxxxxxxxxxxxxxxxx> <20061001063016.GX27551@xxxxxxxxxxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
/me shows utter sadness
mapled:~/work/xen/xenppc-unstable.hg/tools/xm-test # ./runtest.sh - d foobar
  (Skipping report submission)
  Running sanity checks...
  REASON: Failed to create domain
  Sanity checks failed
  mapled:~/work/xen/xenppc-unstable.hg/tools/xm-test #

can't get it off the ground, any pointers.
I think I f'ed up patches,, will try again.
-JX

On Oct 1, 2006, at 2:30 AM, Tony Breeds wrote:

On Fri, Sep 29, 2006 at 08:56:54PM +1100, Tony Breeds wrote:
Hi All,
        These patches update the xm-test code to be more easily portable
to new architecture. This focus od this endevour is PPC but I believe
that IA64 also benifits.

<snip>

By way of a quick status report.

With all thee patches applied to tip (7de08aceff6d) I ran:

I build xm-test:
cd xen.hg/tools/xm-test
./autogen
./configure
INITRD="http://ozlabs.au.ibm.com/~tony/xm-test/"; make existing

I created a grouptest/xenppc file which contains most[1] of the
potential tests and pushed the whole xm-test dir (yes it's wasteful but
it's also easy) to my JS20 blade.  Then:
        ./runtest.sh -d -e tony@xxxxxxxxxxxxxxxxxx -g xenppc xenppc

creates the following report.
---
Xm-test execution summary:
  PASS:  48
  FAIL:  17
  XPASS: 0
  XFAIL: 0


Details:

 FAIL: 01_block_attach_device_pos
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_attach_file_device_pos
         block-attach failed device did not switch to Connected state

 FAIL: 04_block_attach_device_repeatedly_pos
         Device is not actually attached to domU

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos
         block-attach failed device did not switch to Connected state

 FAIL: 09_block_attach_and_dettach_device_check_data_pos
         block-attach failed device did not switch to Connected state

 FAIL: 01_block-destroy_btblock_pos
         block device isn't attached; can't detach!

 FAIL: 02_block-destroy_rtblock_pos
         block-attach failed device did not switch to Connected state

 FAIL: 05_block-destroy_byname_pos
         block device isn't attached; can't detach!

 FAIL: 06_block-destroy_check_list_pos
         block-attach failed device did not switch to Connected state

 FAIL: 01_block_device_read_verify
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_device_write_verify
         block-attach failed device did not switch to Connected state

 FAIL: 01_block-list_pos
         Failed to verify that block dev is attached on DomainU

 FAIL: 02_block-list_attachbd_pos
         block-attach failed device did not switch to Connected state

 FAIL: 03_block-list_anotherbd_pos
         Failed to verify that block dev is attached on DomainU

 FAIL: 06_block-list_checkremove_pos
         block-attach failed device did not switch to Connected state

 FAIL: 01_memset_basic_pos
         Invalid domU meminfo line

 FAIL: 03_memset_random_pos
         Invalid domU meminfo line

---

You'd certainly expect the block-* tests to fail. I don't know why the
memset tests failed but I'll find out next week when I'm back at work.

[1] I omitted create/destroy, save/restore, network* and the scheduler
tests becuase I know some of them crash the machine, attached is the
    xenppc file I used.


Yours Tony

linux.conf.au http://linux.conf.au/ || http:// lca2007.linux.org.au/
   Jan 15-20 2007      The Australian Linux Technical Conference!

<xenppc>
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel


_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel