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-devel

[Xen-devel] xen test results on Unisys ES7000 using changeset 13898

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] xen test results on Unisys ES7000 using changeset 13898
From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
Date: Mon, 12 Feb 2007 20:20:28 -0500
Delivery-date: Mon, 12 Feb 2007 17:22:33 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D3035046F1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EF8D308BE33AF54D8934DF26520252D3035046F1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdJ4UYHnZd8QwLHTMSjo0sqxNkrmgE+CxDg
Thread-topic: xen test results on Unisys ES7000 using changeset 13898

Host:  Unisys ES7000/one, x86_64, 16 physical processors, 64 GB RAM

 

xen-unstable changeset 13898 booted with dom0_mem=512M

 

Issue:  When attempt to start a domain for which there is not enough memory, get “Error: an integer is required” instead of a message indicating there is not enough memory. See xend.log output attached.

 

Booted, logged into, and ran SLES top command or Windows task manager in the following domUs and domVTs (#s 2 through 7 ran simultaneously):

 

  1. 32-processor 64-bit SLES10 DomU with 62GB memory
  2. 4-processor 64-bit SLES10 DomU with 16GB memory
  3. 4-procesor 32-bit SLES10 DomVT with 2GB memory
  4. 4-processor 32-bit PAE SLES10 DomVT with 16GB memory
  5. 4-processor 64-bit SLES10 DomVT with 16GB memory
  6. 1-processor Windows XP DomVT with 4GB memory
  7. 1-processor Windows 2003 Server DomVT with 4GB memory

 

Ran xm-test (non-HVM) on dom0 with the following results:

 

Xm-test timing summary:

  Run Started : Mon, 12 Feb 2007 09:50:01 -0500

  Run Stoped  : Mon, 12 Feb 2007 10:36:11 -0500

Xm-test execution summary:

  PASS:  109

  FAIL:  3

  XPASS: 2

  XFAIL: 1

 

 

Details:

 

 FAIL: 04_memset_smallmem_pos

         Bug #145 Ballooning DomU too low caused run-away

 

XFAIL: 02_network_local_ping_pos

         ping loopback failed for size 65507. ping eth0 failed for size 65507.

 

 FAIL: 01_vcpu-pin_basic_pos

         failed to switch VCPU 0 to CPU 1

 

 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

Attachment: xendlog.txt
Description: xendlog.txt

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