Thanks for your response.
I edited the kernel line to append “nohpet”
for both the SLES10 hvms (32-bit and 32-bit pae) and they both hang in the blue
SUSE linux screen.
Linux Systems Group
From: Nakajima, Jun
Sent: Friday, May 04, 2007 11:02
To: Krysan, Susan;
Subject: RE: [Xen-devel] test
results on Unisys ES7000 32x 128gb usingxen-3.1-testing (c/s 15006) - no new
Can you try to boot the SLES10 with
"nohpet" in the grub command line?
Intel Open Source
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Krysan, Susan
Sent: Friday, May 04, 2007 7:30 AM
Subject: [Xen-devel] test results
on Unisys ES7000 32x 128gb usingxen-3.1-testing (c/s 15006) - no new issues
Host: Unisys ES7000/one, x86_64, 32 physical
processors, 128 GB RAM
Xen-3.1-testing changeset 15006 booted with dom0_mem=512M
ISSUES: still cannot boot of 32-bit SLES10 DomVTs –
bug #940; narrowed down to c/s 14436
Testing includes running xm-test and also attempting to boot
and run programs in the following domUs and domVTs (running domains #s 3
through 9 simultaneously):
64-bit SLES10 DomU with 62GB memory – run kernbench optimal load
64-bit SLES10 DomVT with 62GB memory – run kernbench optimal load
64-bit SLES10 DomU with 16GB memory - run kernbench optimal load
32-bit SLES10 DomVT with 2GB memory – doesn’t boot
32-bit PAE SLES10 DomVT with 16GB memory – doesn’t boot
64-bit SLES10 DomVT with 16GB memory – run kernbench optimal load
Windows XP DomVT with 4GB memory – run 100% cpu intensive program
Windows 2003 Server DomVT with 4GB memory – run 100% cpu intensive
9. 8-processor Windows 2003 Enterprise
Edition DomVT with 8GB memory – run 100% cpu intensive program
Domains #4 and #5 (32-bit) do not boot. Bug # 940
Rest ran successfully.
Ran xm-test (PV) on dom0 with the following results:
Xm-test timing summary:
Run Started : Thu, 03 May 2007 09:23:44 -0400
Run Stoped : Thu, 03 May 2007 10:10:50 -0400
Xm-test execution summary:
loopback failed for size 65507. ping eth0 failed for size 65507.
Ping failed for size 65507.
Linux Systems Group