RE: [Xen-devel] Now available: xm-test-0.4.0

["Yu, Ping Y" <ping.y.yu@xxxxxxxxx>]

Smith,

  I have tried your latest xm-test-0.4. To enable VMX, I have done the following
(1) modify RD_PATH="a specific directory" in configuration 
(2) put VMX initrd.img in RD_PATH
(3) run ./configure
(4) then run a specific test suite by "make check" in this directory

I notice that /tmp/xm-test.conf has been generated as the following content.

disk = ['file:/var/vmmtest/ia32/initrd.img,hdd1,w'] 

When running test case in "create", I found the following domain has been 
created.

[root@localhost xm-test-0.4.0]# xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       251    -      2  r-----     89.5
14_create_blockroot  14        64    0      1  r-----     53.3

It seems that block device has been working!

But the test result is failure in "xm create", and reason is "REASON: Failed to 
read from console (fd=3)"

I suppose that there some reason for that for your reference.
(1) To create a VMX, we should use the following disk item as 
/etc/xen/xmexample.vmx stated
disk = [ 'file:/var/images/min-el3-i386.img,ioemu:hda,w' ]
keyword "ioemu" is necessary.

(2)"xm console" does not support VMX now. We could not get console information.

(3)maybe we should let user configure the image name, for sometimes, we need to 
test multiple VMX.

Any comment is welcome. :-)



-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dan Smith
Sent: 2005年11月1日 0:13
To: Xen Developers
Subject: [Xen-devel] Now available: xm-test-0.4.0

I have just posted version 0.4.0 of xm-test here:

  http://sourceforge.net/project/showfiles.php?group_id=3382&package_id=167975

Online reports can be viewed here:

  http://xmtest.dague.org/

Major changes in this version:

 - More machine information in submitted reports
 - Fixes to some tests
 - VMX compatibility mode, which uses a block device instead of a 
   ramdisk

We are starting to get some really good data on the reporting site.
However, we need more people to submit tests, and from varying
platforms.  If you can run Xen on it, please run xm-test on it at
least occasionally.  

* For those who are not familiar with xm-test:

Several of us here at IBM have been working on a framework for testing
the xen tools, specifically xm.  Our goal is to provide a way for
developers to _easily_ write tests for new and existing xm commands.
We believe that such a test suite will help reduce breakages in the
user-facing tools when developers modify xm and/or xend.

We would like some feedback from the community on the usefulness of
our framework, in hopes that it might be hosted by xensource so that
everyone can contribute tests to help harden xm and xend.

* Details:

The framework tests (as well as the support libraries) are written in
python, which are executed by the standard automake "make check"
facilities.  We build a standardized ramdisk that can be used for
portable test writing, therefore reducing dependencies on the test
host machine.

The framework library provides several abstractions to make common and
complex tasks easier for the test writer.  For example, we provide a
domain and console abstraction that allows a test writer to start a
domU and execute arbitrary commands, retrieving the status and output
of each.  This allows a decent amount of automation for verifying that
(for example) "xm sysrq mydomain s" actually sent the sysrq.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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

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