37 messages in com.xensource.lists.xen-devel[Xen-devel] xen test results on Unisy...
FromSent OnAttachments
Krysan, Susan06 Feb 2007 03:23 
Krysan, Susan12 Feb 2007 17:20.txt
Krysan, Susan20 Feb 2007 14:46 
Krysan, Susan27 Feb 2007 12:42 
Krysan, Susan06 Mar 2007 11:25 
Krysan, Susan22 Mar 2007 12:32 
Krysan, Susan27 Mar 2007 07:55 
Krysan, Susan09 Apr 2007 08:52 
Krysan, Susan26 Apr 2007 08:56 
Krysan, Susan04 May 2007 07:29 
Nakajima, Jun04 May 2007 08:01 
Krysan, Susan04 May 2007 09:57 
Cui, Dexuan07 May 2007 09:36 
Krysan, Susan09 May 2007 11:27 
Cui, Dexuan09 May 2007 19:37 
Krysan, Susan10 May 2007 11:15 
Krysan, Susan14 May 2007 14:14 
Krysan, Susan18 May 2007 08:31 
Krysan, Susan30 May 2007 15:20 
Krysan, Susan08 Jul 2007 12:18 
Ian Pratt08 Jul 2007 13:35 
Krysan, Susan09 Jul 2007 07:54 
Krysan, Susan09 Jul 2007 08:00 
Keir Fraser09 Jul 2007 09:21 
Krysan, Susan18 Jul 2007 06:15 
Krysan, Susan07 Aug 2007 14:12 
Krysan, Susan24 Aug 2007 15:27 
Krysan, Susan13 Sep 2007 08:52 
Krysan, Susan30 Sep 2007 08:34 
Keir Fraser30 Sep 2007 22:46 
Krysan, Susan09 Oct 2007 08:41 
Krysan, Susan25 Oct 2007 05:56 
Krysan, Susan01 Nov 2007 03:28 
Krysan, Susan01 Nov 2007 09:11 
Krysan, Susan26 Nov 2007 14:15 
Krysan, Susan28 Nov 2007 06:48 
Krysan, Susan09 Dec 2007 19:14 
Subject:[Xen-devel] xen test results on Unisys ES7000 using changeset 13898
From:Krysan, Susan (KRYS@unisys.com)
Date:02/12/2007 05:20:05 PM
List:com.xensource.lists.xen-devel
Attachments:

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