I just rebuilt with changeset 13319 and
the domVT shutdown problem is fixed.
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
From: Krysan, Susan
Sent: Monday, January 08, 2007
2:32 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Carb, Brian A;
Puthiyaparambil, Aravindh; Subrahmanian, Raj; Szymanski, Lukasz K; Vessey,
Bruce A
Subject: xen test results on
Unisys ES7000 - domVT shutdown is broken- results in dom0 panic
January 8, 2007
Unisys ES7000/one
x86_64
16 physical processors
32 GB RAM
xen-unstable changeset 13282 booted with dom0_mem=512M
Ran xm-test on dom0 (see results below).
Booted, logged into, and ran top(SLES) or task manager(Windows)
in the following domUs and domVTs (#s 2 through 6 ran simultaneously):
- 32-processor 64-bit SLES10 DomU
with 31GB memory
- 4-processor 64-bit SLES10 DomU
with 8GB memory
- 4-procesor 32-bit SLES10 DomVT
with 2GB memory
- 4-processor 64-bit SLES10 DomVT
with 8GB memory
- uni-processor Windows XP DomVT
with 2GB memory
- uni-processor Windows 2003
Server DomVT with 2GB memory
Issues: Dom0 panic (BUG at common.c:823) results when the 4
domVTs (#s 3-6 above) are powered off(SLES)/shutdown(Windows). Serial
console output attached. I was able to successfully shutdown hvms with
changeset 13205
Xm-test timing summary:
Run Started : Mon, 08 Jan 2007 04:58:23 -0500
Run Stoped : Mon, 08 Jan 2007 05:42:56 -0500
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
