RE: [Xen-devel] test results on Unisys ES7000 32x 128gbusingxen-3.1-testing (c/s 15006) - no new issues

["Krysan, Susan" <KRYSANS@xxxxxxxxxx>]

Dexuan

I was able to successfully boot the ia32 and ia32pae SLES10 HVM guests with "hpet=disable" parameter.

Please let me know if you need any more information or if I can test any patches for you.

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

---

From: Cui, Dexuan [mailto:dexuan.cui@xxxxxxxxx]
Sent: Monday, May 07, 2007 12:37 PM
To: Krysan, Susan; Nakajima, Jun; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] test results on Unisys ES7000 32x 128gbusingxen-3.1-testing (c/s 15006) - no new issues

 

Then can you try to boot the in the grub command line? :)

I guess this can work.

 

-- Dexuan

 

---

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Krysan, Susan
Sent: 2007年5月5日 0:57
To: Nakajima, Jun; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] test results on Unisys ES7000 32x 128gbusingxen-3.1-testing (c/s 15006) - no new issues

 

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.

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

---

From: Nakajima, Jun [mailto:jun.nakajima@xxxxxxxxx]
Sent: Friday, May 04, 2007 11:02 AM
To: Krysan, Susan; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] test results on Unisys ES7000 32x 128gb usingxen-3.1-testing (c/s 15006) - no new issues

 

Can you try to boot the SLES10 with "nohpet" in the grub command line?

Jun
---
Intel Open Source Technology Center

 

---

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Krysan, Susan
Sent: Friday, May 04, 2007 7:30 AM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
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):

 

1.       32-processor 64-bit SLES10 DomU with 62GB memory – run kernbench optimal load

2.       32-processor 64-bit SLES10 DomVT with 62GB memory – run kernbench optimal load

3.       4-processor 64-bit SLES10 DomU with 16GB memory - run kernbench optimal load

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 optimal load

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

            9.   8-processor Windows 2003 Enterprise Edition DomVT with 8GB memory – run 100% cpu intensive program

 

Results:

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:

  PASS:  110

  FAIL:  2

  XPASS: 1

  XFAIL: 2

 

Details:

 

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 65507.

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel