Host: Unisys ES7000/one, x86_64, 16 physical
processors, 64 GB RAM
xen-unstable changeset 14756 booted with dom0_mem=512M
ISSUES: boot of 32-bit SLES10 DomVTs hang. Serial
console, qemu log, and xend.log provide no indication why; the 32-bit SLES10
DomVTs boot when I back up to changeset 14201 (which I ran successfully 2 weeks
ago); the problem was introduced somewhere between changesets 14201 and 14462
(which I ran last week). Suspect changesets 14391 and 14392.
Testing includes running xm-test and also attempting to boot
and run programs in the following domUs and domVTs (running domains #s 3
through 8 simultaneously):
1. 32-processor
64-bit SLES10 DomU with 62GB memory – run cloops, bonnie, and kernbench
2. 32-processor
64-bit SLES10 DomVT with 62GB memory – run kernbench
3. 4-processor
64-bit SLES10 DomU with 16GB memory - run kernbench
4. 4-procesor
32-bit SLES10 DomVT with 2GB memory – doesn’t boot
5. 4-processor
32-bit PAE SLES10 DomVT with 16GB memory – doesn’t boot
6. 4-processor 64-bit
SLES10 DomVT with 16GB memory – run kernbench
7. 1-processor
Windows XP DomVT with 4GB memory – run 100% cpu intensive program
8. 1-processor
Windows 2003 Server DomVT with 4GB memory – run 100% cpu intensive
program
Results:
Domain #2 boots with only 8 processors instead of 32
Domains #4 and #5 (32-bit) do not boot. Bug # 940 still
applies to #4. #5 gets kernel panic – not syncing: attempted to
kill init
Domain #8 – cannot log in because cannot access qemu
console ctrl-alt-2 (or 1 or 3) to send ctrl-alt-delete key sequence
Rest of tests successful.
Ran xm-test (non-HVM) on dom0 with the following results:
Xm-test timing summary:
Run Started : Fri, 06 Apr 2007 15:12:33 -0400
Run Stoped : Fri, 06 Apr 2007 15:58:06 -0400
Xm-test execution summary:
PASS: 111
FAIL: 1
XPASS: 2
XFAIL: 1
Details:
XFAIL: 02_network_local_ping_pos
ping loopback
failed for size 65507. ping eth0 failed for size 65507.
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
