Host: Unisys ES7000/one, x86_64, 64 processors, 256gb
memory
unstable changeset 16549 compiled with max_phys_cpus=64 and
booted with dom0_mem=4096M, numa=on, and xenheap_megabytes=64
NEW ISSUE (fix on the way):
-xm-test 02_block_attach fails with device /dev/ram1 does
not exist
-xm-test 10_security-acm fails with KeyError ‘access_control’
(fix on the way – Stefan Berger)
OLD ISSUES:
-Bug #1037 - Shutdown of large domains takes a long time,
during which time xend is unresponsive (due to the synchronous tearing down of
the memory map); for example, shutdown of 180gb domu causes xend commands to hang
for 5 min 15 sec
-Bug #940 - Must specify hpet=disable kernel parameter to
get 32-bit SLES10 domVTs to boot; narrowed down to c/s 14436 but the patch
originator cannot recreate on his hardware
TESTS include running xm-test and also booting and running
programs in the following domUs and domVTs (running domains #s 1 through 8
simultaneously):
1) 8-processor 64-bit SLES10 domU with
32gb memory - run kernbench
2) 8-processor 64-bit SLES10 domVT with
32gb memory – run kernbench
3) 8-processor 32-bit SLES10 domU with 32gb
memory
4) 8-processor 32-bit PAE SLES10 domVT
with 32gb memory (booted with hpet=disable)
5) 8-processor 32-bit SLES10 domVT with
4gb memory (booted with hpet=disable) - run kernbench
6) 8-processor 32-bit Windows 2003
Enterprise Edition domVT with 32gb memory – run cpu intensive program
7) 8-processor 64-bit Windows Datacenter
with 32gb memory – run cpu intensive program
8) 2-processor 32-bit Windows XP domVT
with 4gb memory – run cpu intensive program
9) 32-processor 64-bit SLES10 domU with 240gb
memory
10) 32-processor 64-bit SLES10 domVT with 240gb memory
RESULTS:
All tests were successful, except for 2 old issues (see
above).
02_block_attach fails with:
[dom0] Running `xm block-attach
02_block_attach_file_device_pos-1196993485 file:/dev/ram1 xvda1 w'
Error: Device 51713 (vbd) could not be connected. /dev/ram1
does not exist.
Usage: xm block-attach <Domain> <BackDev>
<FrontDev> <Mode> [BackDomain]
10_security-acm fails with:
File "./10_security-acm_pol_update.test",
line 40, in ?
del
domain_ul.config.opts['access_control']
KeyError: 'access_control'
Xm-test timing summary:
Run Started : Thu, 06 Dec 2007 21:11:12 -0500
Run Stoped : Thu, 06 Dec 2007 22:01:10 -0500
Xm-test execution summary:
PASS: 109
FAIL: 4
XPASS: 1
XFAIL: 2
Details:
FAIL: 02_block_attach_file_device_pos
xm
block-attach returned invalid 256 != 0
XFAIL: 02_network_local_ping_pos
ping
loopback failed for size 65507. ping eth0 failed for size 65507.
XFAIL: 11_network_domU_ping_pos
Ping failed for size 1 48 64 512 1440 65507.
FAIL: 10_security-acm_pol_update
Unknown reason
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
