Xen-4.1-unstable hypervisor booting error

Xen-4.1-unstable hypervisor booting error

[Michal Novotny]

Hi,
I've installed latest PVops kernel 2.6.32.21 (upgraded from 2.6.32.15 
using the very same kernel build configuration - i.e. copied the 
config-2.6.32.15 file to the kernel source directory) and I can boot 
without hypervisor (using the standard kernel/initrd directives in grub) 
but not with the hypervisor since it fails.

Call trace is:
  [ <ffffffff8100faf2> ] ? check_events+0x12/0x20
  [ <ffffffff8108f94f> ] ? lock_acquire+0xe3/0xf2
  [ <ffffffff812cd2f3> ] ? balloon_process+0x0/0x555
  [ <ffffffff8107793f> ] worker_thread+0x1b2/0x2b1
  [ <ffffffff810778e6> ] ? worker_thread+0x159/0x2b1
  [ <ffffffff8107bf13> ] ? autoremove_wake_function+0x0/0x3d
  [ <ffffffff8107778d> ] ? worker_thread+0x0/0x2b1
  [ <ffffffff8107bcc1> ] kthread+0x6e/0x76
  [ <ffffffff81013eea> ] child_rip+0xa/0x20
  [ <ffffffff81013850> ] ? restore_args+0x0/0x30
  [ <ffffffff8107bdb6> ] ? kthreadd+x0ed/0x10f
  [ <ffffffff8100fadf> ] ? xen_restore_fl_direct_end+0x0/0x1
  [ <ffffffff81013ee0> ] ? child_rip+0x0/0x20

Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65 5a 00 
00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb 5a <0f> 0b 
eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c

RIP [ <ffffffff812cd49b> ] balloon_process+0x1a8/0x555
  RSP [ <ffff8801e9435d50> ]
--- [ end trace e93713a9d40cd06c ] ---
events/0 used greatest stack depth: 4664 bytes left

And the host is stuck and can't boot.

Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or any 
pointers what may be going on? The kernel/system is x86_64 system 
running on RHEL-5 with the PVops kernel now but as I said, it can't boot 
with the hypervisor but everything is fine (except Xen) when booting 
without the hypervisor.

Thanks,
Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

Re: Xen-4.1-unstable hypervisor booting error

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 2410 bytes --]

Could you try:-

/boot/xen.gz  dom0_mem=1024M
. . . . . . . . . . .

Boris.
P.S. I had the same issue.


--- On Mon, 9/27/10, Michal Novotny <minovotn@redhat.com> wrote:

From: Michal Novotny <minovotn@redhat.com>
Subject: [Xen-devel] Xen-4.1-unstable hypervisor booting error
To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Date: Monday, September 27, 2010, 3:47 AM

Hi,
I've installed latest PVops kernel 2.6.32.21 (upgraded from 2.6.32.15 using the very same kernel build configuration - i.e. copied the config-2.6.32.15 file to the kernel source directory) and I can boot without hypervisor (using the standard kernel/initrd directives in grub) but not with the hypervisor since it fails.

Call trace is:
 [ <ffffffff8100faf2> ] ? check_events+0x12/0x20
 [ <ffffffff8108f94f> ] ? lock_acquire+0xe3/0xf2
 [ <ffffffff812cd2f3> ] ? balloon_process+0x0/0x555
 [ <ffffffff8107793f> ] worker_thread+0x1b2/0x2b1
 [ <ffffffff810778e6> ] ? worker_thread+0x159/0x2b1
 [ <ffffffff8107bf13> ] ? autoremove_wake_function+0x0/0x3d
 [ <ffffffff8107778d> ] ? worker_thread+0x0/0x2b1
 [ <ffffffff8107bcc1> ] kthread+0x6e/0x76
 [ <ffffffff81013eea> ] child_rip+0xa/0x20
 [ <ffffffff81013850> ] ? restore_args+0x0/0x30
 [ <ffffffff8107bdb6> ] ? kthreadd+x0ed/0x10f
 [ <ffffffff8100fadf> ] ? xen_restore_fl_direct_end+0x0/0x1
 [ <ffffffff81013ee0> ] ? child_rip+0x0/0x20

Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65 5a 00 00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb 5a <0f> 0b eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c

RIP [ <ffffffff812cd49b> ] balloon_process+0x1a8/0x555
 RSP [ <ffff8801e9435d50> ]
--- [ end trace e93713a9d40cd06c ] ---
events/0 used greatest stack depth: 4664 bytes left

And the host is stuck and can't boot.

Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or any pointers what may be going on? The kernel/system is x86_64 system running on RHEL-5 with the PVops kernel now but as I said, it can't boot with the hypervisor but everything is fine (except Xen) when booting without the hypervisor.

Thanks,
Michal

-- Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat


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



      

[-- Attachment #1.2: Type: text/html, Size: 3181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen-4.1-unstable hypervisor booting error

[Michal Novotny]

Thanks a lot Boris, adding dom0_mem setting to 1G (1024M respectively) 
made it working fine so I guess there's a wrong default setting for 
dom0_mem, at least for x86_64 architecture.

Thanks again Boris!
Michal

On 09/27/2010 11:05 AM, Boris Derzhavets wrote:
> Could you try:-
>
> /boot/xen.gz  dom0_mem=1024M
> . . . . . . . . . . .
>
> Boris.
> P.S. I had the same issue.
>
>
> --- On *Mon, 9/27/10, Michal Novotny /<minovotn@redhat.com>/* wrote:
>
>
>     From: Michal Novotny <minovotn@redhat.com>
>     Subject: [Xen-devel] Xen-4.1-unstable hypervisor booting error
>     To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
>     Date: Monday, September 27, 2010, 3:47 AM
>
>     Hi,
>     I've installed latest PVops kernel 2.6.32.21 (upgraded from
>     2.6.32.15 using the very same kernel build configuration - i.e.
>     copied the config-2.6.32.15 file to the kernel source directory)
>     and I can boot without hypervisor (using the standard
>     kernel/initrd directives in grub) but not with the hypervisor
>     since it fails.
>
>     Call trace is:
>     [ <ffffffff8100faf2> ] ? check_events+0x12/0x20
>     [ <ffffffff8108f94f> ] ? lock_acquire+0xe3/0xf2
>     [ <ffffffff812cd2f3> ] ? balloon_process+0x0/0x555
>     [ <ffffffff8107793f> ] worker_thread+0x1b2/0x2b1
>     [ <ffffffff810778e6> ] ? worker_thread+0x159/0x2b1
>     [ <ffffffff8107bf13> ] ? autoremove_wake_function+0x0/0x3d
>     [ <ffffffff8107778d> ] ? worker_thread+0x0/0x2b1
>     [ <ffffffff8107bcc1> ] kthread+0x6e/0x76
>     [ <ffffffff81013eea> ] child_rip+0xa/0x20
>     [ <ffffffff81013850> ] ? restore_args+0x0/0x30
>     [ <ffffffff8107bdb6> ] ? kthreadd+x0ed/0x10f
>     [ <ffffffff8100fadf> ] ? xen_restore_fl_direct_end+0x0/0x1
>     [ <ffffffff81013ee0> ] ? child_rip+0x0/0x20
>
>     Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65
>     5a 00 00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb
>     5a <0f> 0b eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c
>
>     RIP [ <ffffffff812cd49b> ] balloon_process+0x1a8/0x555
>     RSP [ <ffff8801e9435d50> ]
>     --- [ end trace e93713a9d40cd06c ] ---
>     events/0 used greatest stack depth: 4664 bytes left
>
>     And the host is stuck and can't boot.
>
>     Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or
>     any pointers what may be going on? The kernel/system is x86_64
>     system running on RHEL-5 with the PVops kernel now but as I said,
>     it can't boot with the hypervisor but everything is fine (except
>     Xen) when booting without the hypervisor.
>
>     Thanks,
>     Michal
>
>     -- Michal Novotny<minovotn@redhat.com
>     </mc/compose?to=minovotn@redhat.com>>, RHCE
>     Virtualization Team (xen userspace), Red Hat
>
>
>     _______________________________________________
>     Xen-devel mailing list
>     Xen-devel@lists.xensource.com
>     </mc/compose?to=Xen-devel@lists.xensource.com>
>     http://lists.xensource.com/xen-devel
>
>


-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

Re: Xen-4.1-unstable hypervisor booting error

[Pasi Kärkkäinen]

On Mon, Sep 27, 2010 at 12:46:46PM +0200, Michal Novotny wrote:
> Thanks a lot Boris, adding dom0_mem setting to 1G (1024M respectively)  
> made it working fine so I guess there's a wrong default setting for  
> dom0_mem, at least for x86_64 architecture.
>

Hmm.. do I remember correctly this was an issue that's already fixed,
but the fix is not yet in xen/stable-2.6.32.x tree? 

Jeremy probably remembers..

-- Pasi

> Thanks again Boris!
> Michal
>
> On 09/27/2010 11:05 AM, Boris Derzhavets wrote:
>> Could you try:-
>>
>> /boot/xen.gz  dom0_mem=1024M
>> . . . . . . . . . . .
>>
>> Boris.
>> P.S. I had the same issue.
>>
>>
>> --- On *Mon, 9/27/10, Michal Novotny /<minovotn@redhat.com>/* wrote:
>>
>>
>>     From: Michal Novotny <minovotn@redhat.com>
>>     Subject: [Xen-devel] Xen-4.1-unstable hypervisor booting error
>>     To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
>>     Date: Monday, September 27, 2010, 3:47 AM
>>
>>     Hi,
>>     I've installed latest PVops kernel 2.6.32.21 (upgraded from
>>     2.6.32.15 using the very same kernel build configuration - i.e.
>>     copied the config-2.6.32.15 file to the kernel source directory)
>>     and I can boot without hypervisor (using the standard
>>     kernel/initrd directives in grub) but not with the hypervisor
>>     since it fails.
>>
>>     Call trace is:
>>     [ <ffffffff8100faf2> ] ? check_events+0x12/0x20
>>     [ <ffffffff8108f94f> ] ? lock_acquire+0xe3/0xf2
>>     [ <ffffffff812cd2f3> ] ? balloon_process+0x0/0x555
>>     [ <ffffffff8107793f> ] worker_thread+0x1b2/0x2b1
>>     [ <ffffffff810778e6> ] ? worker_thread+0x159/0x2b1
>>     [ <ffffffff8107bf13> ] ? autoremove_wake_function+0x0/0x3d
>>     [ <ffffffff8107778d> ] ? worker_thread+0x0/0x2b1
>>     [ <ffffffff8107bcc1> ] kthread+0x6e/0x76
>>     [ <ffffffff81013eea> ] child_rip+0xa/0x20
>>     [ <ffffffff81013850> ] ? restore_args+0x0/0x30
>>     [ <ffffffff8107bdb6> ] ? kthreadd+x0ed/0x10f
>>     [ <ffffffff8100fadf> ] ? xen_restore_fl_direct_end+0x0/0x1
>>     [ <ffffffff81013ee0> ] ? child_rip+0x0/0x20
>>
>>     Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65
>>     5a 00 00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb
>>     5a <0f> 0b eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c
>>
>>     RIP [ <ffffffff812cd49b> ] balloon_process+0x1a8/0x555
>>     RSP [ <ffff8801e9435d50> ]
>>     --- [ end trace e93713a9d40cd06c ] ---
>>     events/0 used greatest stack depth: 4664 bytes left
>>
>>     And the host is stuck and can't boot.
>>
>>     Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or
>>     any pointers what may be going on? The kernel/system is x86_64
>>     system running on RHEL-5 with the PVops kernel now but as I said,
>>     it can't boot with the hypervisor but everything is fine (except
>>     Xen) when booting without the hypervisor.
>>
>>     Thanks,
>>     Michal
>>
>>     -- Michal Novotny<minovotn@redhat.com
>>     </mc/compose?to=minovotn@redhat.com>>, RHCE
>>     Virtualization Team (xen userspace), Red Hat
>>
>>
>>     _______________________________________________
>>     Xen-devel mailing list
>>     Xen-devel@lists.xensource.com
>>     </mc/compose?to=Xen-devel@lists.xensource.com>
>>     http://lists.xensource.com/xen-devel
>>
>>
>
>
> -- 
> Michal Novotny<minovotn@redhat.com>, RHCE
> Virtualization Team (xen userspace), Red Hat
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Xen-4.1-unstable hypervisor booting error

[khris4]

I was also going to report this issue. I had to do a lot playing around to
find out  how to fix this issue. I'm waiting for someone to give me access
to xen wiki. 
-- 
View this message in context: http://xen.1045712.n5.nabble.com/Xen-4-1-unstable-hypervisor-booting-error-tp2854895p2855607.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: Xen-4.1-unstable hypervisor booting error

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 4430 bytes --]

> Hmm.. do I remember correctly this was an issue that's already fixed,
> but the fix is not yet in xen/stable-2.6.32.x tree? 

Yes , fix is not yet in xen/stable-2.6.32.x tree

Boris.


--- On Mon, 9/27/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] Xen-4.1-unstable hypervisor booting error
To: "Michal Novotny" <minovotn@redhat.com>
Cc: "Boris Derzhavets" <bderzhavets@yahoo.com>, "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>, "Jeremy Fitzhardinge" <jeremy@goop.org>
Date: Monday, September 27, 2010, 10:08 AM

On Mon, Sep 27, 2010 at 12:46:46PM +0200, Michal Novotny wrote:
> Thanks a lot Boris, adding dom0_mem setting to 1G (1024M respectively)  
> made it working fine so I guess there's a wrong default setting for  
> dom0_mem, at least for x86_64 architecture.
>

Hmm.. do I remember correctly this was an issue that's already fixed,
but the fix is not yet in xen/stable-2.6.32.x tree? 

Jeremy probably remembers..

-- Pasi

> Thanks again Boris!
> Michal
>
> On 09/27/2010 11:05 AM, Boris Derzhavets wrote:
>> Could you try:-
>>
>> /boot/xen.gz  dom0_mem=1024M
>> . . . . . . . . . . .
>>
>> Boris.
>> P.S. I had the same issue.
>>
>>
>> --- On *Mon, 9/27/10, Michal Novotny /<minovotn@redhat.com>/* wrote:
>>
>>
>>     From: Michal Novotny <minovotn@redhat.com>
>>     Subject: [Xen-devel] Xen-4.1-unstable hypervisor booting error
>>     To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
>>     Date: Monday, September 27, 2010, 3:47 AM
>>
>>     Hi,
>>     I've installed latest PVops kernel 2.6.32.21 (upgraded from
>>     2.6.32.15 using the very same kernel build configuration - i.e.
>>     copied the config-2.6.32.15 file to the kernel source directory)
>>     and I can boot without hypervisor (using the standard
>>     kernel/initrd directives in grub) but not with the hypervisor
>>     since it fails.
>>
>>     Call trace is:
>>     [ <ffffffff8100faf2> ] ? check_events+0x12/0x20
>>     [ <ffffffff8108f94f> ] ? lock_acquire+0xe3/0xf2
>>     [ <ffffffff812cd2f3> ] ? balloon_process+0x0/0x555
>>     [ <ffffffff8107793f> ] worker_thread+0x1b2/0x2b1
>>     [ <ffffffff810778e6> ] ? worker_thread+0x159/0x2b1
>>     [ <ffffffff8107bf13> ] ? autoremove_wake_function+0x0/0x3d
>>     [ <ffffffff8107778d> ] ? worker_thread+0x0/0x2b1
>>     [ <ffffffff8107bcc1> ] kthread+0x6e/0x76
>>     [ <ffffffff81013eea> ] child_rip+0xa/0x20
>>     [ <ffffffff81013850> ] ? restore_args+0x0/0x30
>>     [ <ffffffff8107bdb6> ] ? kthreadd+x0ed/0x10f
>>     [ <ffffffff8100fadf> ] ? xen_restore_fl_direct_end+0x0/0x1
>>     [ <ffffffff81013ee0> ] ? child_rip+0x0/0x20
>>
>>     Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65
>>     5a 00 00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb
>>     5a <0f> 0b eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c
>>
>>     RIP [ <ffffffff812cd49b> ] balloon_process+0x1a8/0x555
>>     RSP [ <ffff8801e9435d50> ]
>>     --- [ end trace e93713a9d40cd06c ] ---
>>     events/0 used greatest stack depth: 4664 bytes left
>>
>>     And the host is stuck and can't boot.
>>
>>     Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or
>>     any pointers what may be going on? The kernel/system is x86_64
>>     system running on RHEL-5 with the PVops kernel now but as I said,
>>     it can't boot with the hypervisor but everything is fine (except
>>     Xen) when booting without the hypervisor.
>>
>>     Thanks,
>>     Michal
>>
>>     -- Michal Novotny<minovotn@redhat.com
>>     </mc/compose?to=minovotn@redhat.com>>, RHCE
>>     Virtualization Team (xen userspace), Red Hat
>>
>>
>>     _______________________________________________
>>     Xen-devel mailing list
>>     Xen-devel@lists.xensource.com
>>     </mc/compose?to=Xen-devel@lists.xensource.com>
>>     http://lists.xensource.com/xen-devel
>>
>>
>
>
> -- 
> Michal Novotny<minovotn@redhat.com>, RHCE
> Virtualization Team (xen userspace), Red Hat
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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



      

[-- Attachment #1.2: Type: text/html, Size: 7868 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Xen-4.1-unstable hypervisor booting error

[Jeremy Fitzhardinge]

 On 09/27/2010 10:08 AM, Boris Derzhavets wrote:
> > Hmm.. do I remember correctly this was an issue that's already fixed,
> > but the fix is not yet in xen/stable-2.6.32.x tree?
>
> Yes , fix is not yet in xen/stable-2.6.32.x tree
>

xen/stable-2.6.32.x is now automatically updated as a result of having
gone through a successful test from IanJ's test stuff.  It appears that
hasn't passed a kernel in a while, so it has been stuck for a while.  It
isn't clear to me whether the failures are real or spurious (I believe
some have been spurious).

    J