June 6, 2006
Configuration:
Unisys ES7000/one
x86_64
32 processors (16 procs with hyperthreading turned on)
16 GB RAM
SLES 10 RC1 with xen-unstable changeset 10269
Ran xm-test (see results below) and successfully booted the following SLES10
domUs:
a. A uni-processor DomU with 1GB of memory
b. A 4-processor DomU with 1GB of memory
c. A uniprocessory DomU with 8GB of memory
d. A 4-processor DomU with 8GB of memory
e. A 32-processor DomU with 15GB memory
xm-test results
Issue: 01_enforce_dom0_cpus_basic_pos seems to only release 7 processors (drops
from 32 to 25). When we boot as 16 procs with hyperthreading off, this test
still only releases 7 processors (drops from 16 to 9). Also changed the script
to wait longer for the processors to release, but still get the same results.
Xm-test execution summary:
PASS: 110
FAIL: 5
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_enforce_dom0_cpus_basic_pos
/proc/cpuinfo says xend didn''t enforce dom0_cpus (25 != 1)
FAIL: 03_memset_random_pos
Timed out waiting for console
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
June 14, 2006
Configuration:
Unisys ES7000/one
x86_64
16 processors
16 GB RAM
SLES10 RC2.5 with xen-unstable changeset 10333
Ran xm-test (see results below) and successfully booted and ran LTP in the
following SLES10 domUs:
a. A uni-processor DomU with 1GB of memory
b. A 4-processor DomU with 1GB of memory
c. A uni-processor DomU with 8GB of memory
d. A 4-processor DomU with 8GB of memory
e. A 32-processor DomU with 15GB memory
xm-test results:
Issue: 01_enforce_dom0_cpus_basic_pos seems to only release 7 processors (drops
from 16 to 7). Also changed the script to wait longer for the processors to
release, but still get the same results.
Xm-test execution summary:
PASS: 112
FAIL: 5
XPASS: 0
XFAIL: 3
Details:
FAIL: 01_enforce_dom0_cpus_basic_pos
/proc/cpuinfo says xend didn''t enforce dom0_cpus (9 != 1)
FAIL: 03_memset_random_pos
Timed out waiting for console
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 65507.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
June 20,2006
Configuration:
Unisys ES7000/one
x86_64
32 processors (16 procs with hyperthreading turned on)
16 GB RAM
SLES10 RC2.5 with xen-unstable changeset 10449 plus patch to xm-test Console.py
(for bug #674)
Ran xm-test (see results below) and successfully booted and ran LTP in the
following SLES10 domUs:
a. A uni-processor DomU with 1GB of memory
b. A 4-processor DomU with 1GB of memory
c. A uni-processor DomU with 8GB of memory
d. A 4-processor DomU with 8GB of memory
e. A 32-processor DomU with 15GB memory
Issues: Applied patch to xm-test Console.py (fix for bug #674)
Bug #683 - Cannot start 1GB and 2GB domUs when dom0 has most of the
host''s 16GB memory (get error - privileged domain did not balloon)
Xm-test execution summary:
PASS: 111
FAIL: 6
XPASS: 0
XFAIL: 3
Details:
FAIL: 03_memset_random_pos
Timed out waiting for console prompt
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 16384 24567 32767 65495.
FAIL: 13_network_domU_udp_pos
UDP hping2 failed for size 32767 65495.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
June 27, 2006
Configuration:
Unisys ES7000/one
x86_64
32 processors (16 procs with hyperthreading turned on)
16 GB RAM
SLES10 RC2.5 with xen-unstable changeset 10482
Ran xm-test (see results below) and successfully booted and ran LTP in the
following SLES10 domUs:
a. A uni-processor DomU with 1GB of memory
b. A 4-processor DomU with 1GB of memory
c. A uni-processor DomU with 8GB of memory
d. A 4-processor DomU with 8GB of memory
e. A 32-processor DomU with 15GB memory
Issues: None
Xm-test execution summary:
PASS: 107
FAIL: 5
XPASS: 0
XFAIL: 3
Details:
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 16384 24567 32767 65495.
FAIL: 13_network_domU_udp_pos
UDP hping2 failed for size 32767 65495.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
July 06, 2006
Configuration:
Unisys ES7000/one
x86_64
32 physical processors
32 GB RAM
SLES10 RC3 with xen-unstable changeset 10641
Ran xm-test (see results below) and successfully booted and ran LTP in the
following x86_64 SLES10 domUs:
a. A uni-processor DomU with 1GB of memory
b. A 4-processor DomU with 1GB of memory
c. A uni-processor DomU with 8GB of memory
d. A 4-processor DomU with 8GB of memory
e. A 32-processor DomU with 31GB memory
Issues: None
Xm-test execution summary:
PASS: 107
FAIL: 5
XPASS: 0
XFAIL: 3
Details:
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 05_network_dom0_ping_pos
Ping to dom0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 16384 24567 32767 65495.
FAIL: 13_network_domU_udp_pos
UDP hping2 failed for size 32767 65495.
> Thanks,
> Sue Krysan
> Linux Systems Group
> Unisys Corporation
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel