RE: [Xen-devel] can't boot 32-bit SLES10 HVMs since c/s 14436 wasintroduced

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

Hi.  Dexuan.  Just a note to let you know that I also cannot boot 32-bit SLES10 hvms on Dell PowerEdge SC1430.  I can only boot if I add the hpet=disable parameter.  Also wanted to let you know that as I keep testing this issue, the failure to boot actually happens in a few different ways, on both the ES7000 and the Dell: sometimes with the kernel panic: Badness in smp_call_function at arch/i386/kernel/smp.c:595, sometimes the boot hangs in blue screen before login prompt appears, and sometimes it gets to the login prompt but the screen flashes off and on and when enter the userid, I keep getting a message that the login timed out after 60 seconds and I am unable to login.

 

I will be using the Dell box to keep decreasing the TSC_PER_HPET_TICK value as you suggest to see if I can find a value that will work.  Then I will try that value on the Unisys ES7000. 

 

Could you explain what exactly this value controls and why it is needed? (since I can boot successfully without it)

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

---

From: Cui, Dexuan [mailto:dexuan.cui@xxxxxxxxx]
Sent: Monday, May 14, 2007 9:57 PM
To: Krysan, Susan
Subject: RE: [Xen-devel] test results on Unisys ES7000 32x 128gb usingxen-3.1-testing (c/s 15040) - no new issues

 

Hi Susan,

Sorry to see the issue “32-bit SLES10 HVM guest can’t boot on Unisys ES7000” is still there. L

 

Can you try changing the macro in xen/arch/x86/hvm/hpet.c? i.e., change it to 16, 8, 4, 2, 1, and see if the guest can boot.

I think at least changing the macro to 1 can boot the guest definitely since this means disabling the patch actually.

 

-- Dexuan

 

---

From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Krysan, Susan
Sent: 2007年5月15日 5:15
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] test results on Unisys ES7000 32x 128gb usingxen-3.1-testing (c/s 15040) - no new issues

 

Host:  Unisys ES7000/one, x86_64, 32 physical processors, 128 GB RAM

 

Xen-3.1-testing changeset 15040 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 (DomU) on dom0 with the following results:

 

Xm-test timing summary:

  Run Started : Mon, 14 May 2007 14:04:02 -0400

  Run Stoped  : Mon, 14 May 2007 14:51:11 -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

 

 

 

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