Krysan, Susan
2007-Apr-18 22:00 UTC
[Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on x86_64 Xen
I cannot boot 32-bit SLES10 HVMs since changeset 14201.
32-bit SLES10 hvm (4x 2gb) hangs in blue SUSE Linux screen
32-bit SLES10 PAE (4x 16gb) kernel panics as follows:
Kernel panic - not syncing: Fatal exception in interrupt
Badness in smp_call_function at arch/i386/kernel/smp.c:595
Neither serial port nor logs give any indication what is happening.
I saw changes in changeset 14392 to 32bit bios support module, so
rebuilt with changeset 14391and retried the 32-bit SLES10 non-PAE and it
boots fine.
Has anyone else had problems booting 32-bit SLES10 hvms on 64-bit
hypervisor?
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Krysan, Susan
2007-Apr-19 12:43 UTC
RE: [Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on x86_64Xen
Hi Yunfeng.
I am having problems with 32-bit SLES10 2.6 VMX on 64-bit SLES10 xen as
outlined below.
I see from your vmx status reports that you are able to:
Bootup unmodified FC5 IA32 nonPAE SMP 2.6 Linux VMX domain
Bootup unmodified FC5 PAE SMP 2.6 Linux VMX domain.
How many processors and how much memory do these two domains have?
Have you ever seen problems similar to mine?
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
________________________________
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Krysan,
Susan
Sent: Wednesday, April 18, 2007 6:01 PM
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on
x86_64Xen
I cannot boot 32-bit SLES10 HVMs since changeset 14201.
32-bit SLES10 hvm (4x 2gb) hangs in blue SUSE Linux screen
32-bit SLES10 PAE (4x 16gb) kernel panics as follows:
Kernel panic - not syncing: Fatal exception in interrupt
Badness in smp_call_function at arch/i386/kernel/smp.c:595
Neither serial port nor logs give any indication what is happening.
I saw changes in changeset 14392 to 32bit bios support module, so
rebuilt with changeset 14391and retried the 32-bit SLES10 non-PAE and it
boots fine.
Has anyone else had problems booting 32-bit SLES10 hvms on 64-bit
hypervisor?
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2007-Apr-19 13:25 UTC
Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on x86_64 Xen
On 18/4/07 23:00, "Krysan, Susan" <KRYSANS@unisys.com> wrote:> I saw changes in changeset 14392 to 32bit bios support module, so rebuilt with > changeset 14391and retried the 32-bit SLES10 non-PAE and it boots fine.Thanks for narrowing down to a specific changeset. I¹ll stare at that one and see if I can work out what¹s going on. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Apr-19 14:29 UTC
Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on x86_64 Xen
On 19/4/07 14:25, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:> On 18/4/07 23:00, "Krysan, Susan" <KRYSANS@unisys.com> wrote: > >> I saw changes in changeset 14392 to 32bit bios support module, so rebuilt >> with changeset 14391and retried the 32-bit SLES10 non-PAE and it boots fine. > > Thanks for narrowing down to a specific changeset. I¹ll stare at that one and > see if I can work out what¹s going on.That changeset looks like it actually fixes bugs rather than introducing them. Either way, rombios is not configured by default to use the TCG extensions, so the 32-bit highmem bios extension should not even be used. With current unstable repository, does the problem go away if you comment out the one-line body of function highbios_setup() in file tools/firmware/hvmloader/32bitbios_support.c? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Zhao, Yunfeng
2007-Apr-20 03:33 UTC
RE: [Xen-devel] can''t boot 32-bit SLES10 HVMs using c/s 14875 on x86_64Xen
Hi,Krysan I have no problem to boot 32 bit SLES10 SP1 RC2 HVM guest with 4 vpus on 64bit host against latest xen unstable. My test box is a bensley with 16GB mem. I specified 512M for the HVM guest. Thanks Yunfeng ________________________________________ From: Krysan, Susan [mailto:KRYSANS@unisys.com] Sent: 2007年4月19日 20:44 To: Zhao, Yunfeng Cc: xen-devel@lists.xensource.com Subject: RE: [Xen-devel] can't boot 32-bit SLES10 HVMs using c/s 14875 on x86_64Xen Hi Yunfeng. I am having problems with 32-bit SLES10 2.6 VMX on 64-bit SLES10 xen as outlined below. I see from your vmx status reports that you are able to: Bootup unmodified FC5 IA32 nonPAE SMP 2.6 Linux VMX domain Bootup unmodified FC5 PAE SMP 2.6 Linux VMX domain. How many processors and how much memory do these two domains have? Have you ever seen problems similar to mine? Thanks, Sue Krysan Linux Systems Group Unisys Corporation ________________________________________ From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Krysan, Susan Sent: Wednesday, April 18, 2007 6:01 PM To: xen-devel@lists.xensource.com Subject: [Xen-devel] can't boot 32-bit SLES10 HVMs using c/s 14875 on x86_64Xen I cannot boot 32-bit SLES10 HVMs since changeset 14201. 32-bit SLES10 hvm (4x 2gb) hangs in blue SUSE Linux screen 32-bit SLES10 PAE (4x 16gb) kernel panics as follows: Kernel panic - not syncing: Fatal exception in interrupt Badness in smp_call_function at arch/i386/kernel/smp.c:595 Neither serial port nor logs give any indication what is happening. I saw changes in changeset 14392 to 32bit bios support module, so rebuilt with changeset 14391and retried the 32-bit SLES10 non-PAE and it boots fine. Has anyone else had problems booting 32-bit SLES10 hvms on 64-bit hypervisor? Thanks, Sue Krysan Linux Systems Group Unisys Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Krysan, Susan
2007-May-01 17:49 UTC
[Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 was introduced
I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys ES7000/one with Intel processors. I initially tried with HVM memory sizes of 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot. I have run both with the ES7000 configured as 8x 32gb and 16x 64gb. The HVMs either hang in the graphical blue SUSE Linux screen or get this kernel panic: Badness in smp_call_function at arch/i386/kernel/smp.c:595. At Keir''s suggestion, I used a binary search method to narrow down changesets, and after building and testing multiple changesets I was able to determine that c/s 14436 introduces the problem. Thanks, Sue Krysan Linux Systems Group Unisys Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-May-01 20:47 UTC
Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 was introduced
On 1/5/07 18:49, "Krysan, Susan" <KRYSANS@unisys.com> wrote:> I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys > ES7000/one with Intel processors. I initially tried with HVM memory sizes of > 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot. I > have run both with the ES7000 configured as 8x 32gb and 16x 64gb. The HVMs > either hang in the graphical blue SUSE Linux screen or get this kernel panic: > Badness in smp_call_function at arch/i386/kernel/smp.c:595. > > At Keir¹s suggestion, I used a binary search method to narrow down changesets, > and after building and testing multiple changesets I was able to determine > that c/s 14436 introduces the problem.This is the changeset that reduced the virtual HPET frequency to 1/32 that of the virtual TSC. This was itself a bug fix (guests tend to assume that HPET frequency is somewhat less than TSC frequency). I can¹t immediately see how this changeset would cause issues like badness in smp_call_function¹. Any ideas, Dexuan? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-May-01 20:59 UTC
Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 was introduced
On 1/5/07 18:49, "Krysan, Susan" <KRYSANS@unisys.com> wrote:> I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys > ES7000/one with Intel processors. I initially tried with HVM memory sizes of > 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot. I > have run both with the ES7000 configured as 8x 32gb and 16x 64gb. The HVMs > either hang in the graphical blue SUSE Linux screen or get this kernel panic: > Badness in smp_call_function at arch/i386/kernel/smp.c:595. > > At Keir¹s suggestion, I used a binary search method to narrow down changesets, > and after building and testing multiple changesets I was able to determineWhen you get the Badness in smp_call_function¹ message, do you also get a backtrace and/or stack dump? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Krysan, Susan
2007-May-02 15:43 UTC
RE: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 wasintroduced
Yes, I saved this output from the 32-bit SMP (non-PAE) HVM when I ran with changeset 14756: <0>Kernel panic - not syncing: Fatal exception in interrupt Badness in smp_call_function at arch/i386/kernel/smp.c:595 [<c010dc2a>] smp_call_function+0x56/0x104 [<c011a7cf>] printk+0x14/0x18 [<c010dceb>] smp_send_stop+0x13/0x1c [<c0119ed8>] panic+0x4c/0xe4 [<c010421a>] die+0x1dd/0x1e7 [<c0104836>] do_invalid_op+0x0/0x9d [<c01048c7>] do_invalid_op+0x91/0x9d [<f886173d>] ide_timer_expiry+0x90/0x257 [ide_core] [<c02001e4>] vt_console_print+0x0/0x212 [<c0119fde>] __call_console_drivers+0x34/0x40 [<c011a263>] release_console_sem+0x15a/0x194 [<c011a797>] vprintk+0x23f/0x263 [<f8861351>] ide_intr+0x17f/0x18a [ide_core] [<c0135a92>] handle_IRQ_event+0x23/0x4c [<f8867694>] ide_dma_intr+0x0/0x8f [ide_core] [<c0103a2f>] error_code+0x4f/0x60 [<f8867694>] ide_dma_intr+0x0/0x8f [ide_core] [<f886007b>] ide_uevent+0xab/0xfe [ide_core] [<f886173d>] ide_timer_expiry+0x90/0x257 [ide_core] [<c012007b>] do_sysctl+0x1b1/0x21f [<c0121f90>] run_timer_softirq+0x128/0x18c [<f88616ad>] ide_timer_expiry+0x0/0x257 [ide_core] [<c011e544>] __do_softirq+0x58/0xc2 [<c011e5dc>] do_softirq+0x2e/0x32 [<c0104cb7>] do_IRQ+0x4b/0x53 [<c010387a>] common_interrupt+0x1a/0x20 [<c0141fe7>] __handle_mm_fault+0x3f8/0x7e8 [<c028524e>] do_page_fault+0x16e/0x525 [<c02850e0>] do_page_fault+0x0/0x525 [<c0103a2f>] error_code+0x4f/0x60 Thanks, Sue Krysan Linux Systems Group Unisys Corporation ________________________________ From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] Sent: Tuesday, May 01, 2007 4:59 PM To: Krysan, Susan; xen-devel@lists.xensource.com Subject: Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 wasintroduced On 1/5/07 18:49, "Krysan, Susan" <KRYSANS@unisys.com> wrote: I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys ES7000/one with Intel processors. I initially tried with HVM memory sizes of 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot. I have run both with the ES7000 configured as 8x 32gb and 16x 64gb. The HVMs either hang in the graphical blue SUSE Linux screen or get this kernel panic: Badness in smp_call_function at arch/i386/kernel/smp.c:595. At Keir''s suggestion, I used a binary search method to narrow down changesets, and after building and testing multiple changesets I was able to determine When you get the ''Badness in smp_call_function'' message, do you also get a backtrace and/or stack dump? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Cui, Dexuan
2007-May-07 16:30 UTC
RE: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436wasintroduced
Sorry, I just saw the mail (in our side, the past week was a long public holiday). It seems the issue hasn’t been fixed till now? I can’t see why the lower-the-freq-of-vHPET changeset should cause the issue… I remember booting 32bit SLES 10 SP1 RC2 HVM guest on 64bit Bensley host is ok, per some previous mail (pls see the attachment for it). Does this mean the issue only happens to Unisys ES7000, and doesn’t happen to Bensley? -- Dexuan ________________________________ From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Krysan, Susan Sent: 2007年5月2日 23:43 To: Keir Fraser; xen-devel@lists.xensource.com Subject: RE: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436wasintroduced Yes, I saved this output from the 32-bit SMP (non-PAE) HVM when I ran with changeset 14756: <0>Kernel panic – not syncing: Fatal exception in interrupt Badness in smp_call_function at arch/i386/kernel/smp.c:595 [<c010dc2a>] smp_call_function+0x56/0x104 [<c011a7cf>] printk+0x14/0x18 [<c010dceb>] smp_send_stop+0x13/0x1c [<c0119ed8>] panic+0x4c/0xe4 [<c010421a>] die+0x1dd/0x1e7 [<c0104836>] do_invalid_op+0x0/0x9d [<c01048c7>] do_invalid_op+0x91/0x9d [<f886173d>] ide_timer_expiry+0x90/0x257 [ide_core] [<c02001e4>] vt_console_print+0x0/0x212 [<c0119fde>] __call_console_drivers+0x34/0x40 [<c011a263>] release_console_sem+0x15a/0x194 [<c011a797>] vprintk+0x23f/0x263 [<f8861351>] ide_intr+0x17f/0x18a [ide_core] [<c0135a92>] handle_IRQ_event+0x23/0x4c [<f8867694>] ide_dma_intr+0x0/0x8f [ide_core] [<c0103a2f>] error_code+0x4f/0x60 [<f8867694>] ide_dma_intr+0x0/0x8f [ide_core] [<f886007b>] ide_uevent+0xab/0xfe [ide_core] [<f886173d>] ide_timer_expiry+0x90/0x257 [ide_core] [<c012007b>] do_sysctl+0x1b1/0x21f [<c0121f90>] run_timer_softirq+0x128/0x18c [<f88616ad>] ide_timer_expiry+0x0/0x257 [ide_core] [<c011e544>] __do_softirq+0x58/0xc2 [<c011e5dc>] do_softirq+0x2e/0x32 [<c0104cb7>] do_IRQ+0x4b/0x53 [<c010387a>] common_interrupt+0x1a/0x20 [<c0141fe7>] __handle_mm_fault+0x3f8/0x7e8 [<c028524e>] do_page_fault+0x16e/0x525 [<c02850e0>] do_page_fault+0x0/0x525 [<c0103a2f>] error_code+0x4f/0x60 Thanks, Sue Krysan Linux Systems Group Unisys Corporation ________________________________ From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] Sent: Tuesday, May 01, 2007 4:59 PM To: Krysan, Susan; xen-devel@lists.xensource.com Subject: Re: [Xen-devel] can''t boot 32-bit SLES10 HVMs since c/s 14436 wasintroduced On 1/5/07 18:49, "Krysan, Susan" <KRYSANS@unisys.com> wrote: I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys ES7000/one with Intel processors. I initially tried with HVM memory sizes of 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot. I have run both with the ES7000 configured as 8x 32gb and 16x 64gb. The HVMs either hang in the graphical blue SUSE Linux screen or get this kernel panic: Badness in smp_call_function at arch/i386/kernel/smp.c:595. At Keir’s suggestion, I used a binary search method to narrow down changesets, and after building and testing multiple changesets I was able to determine When you get the ‘Badness in smp_call_function’ message, do you also get a backtrace and/or stack dump? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel