| |
|
 |
|
 |
|
|
|
| |
|
|
xen-api
[Xen-API] Re: [Xen-devel] Guest CentOS 5.4 64bit on-top XCP 0.5 issue /
Jonathan:
Reviewing my code, the error, I think, was in VM.set_memory_limits()
where the static_max was configured to all physical host memory. This
variable was changed and after this, the problem was solved.
Thanks,
On Fri, Feb 18, 2011 at 9:53 PM, Jonathan Ludlam
<Jonathan.Ludlam@xxxxxxxxxxxxx> wrote:
> Hi Marco,
>
> Does the problem occur on XCP 1.0?
>
> Jon
>
> On 18 Feb 2011, at 17:57, Marco Sinhoreli wrote:
>
>> Hello all:
>>
>> I've running on-top XCP 0.5 (Xen Hypervisor 3.4.2) a CentOS 5.4 64bit
>> Guest and it has some issue to finish the boot. In linux kernel boot,
>> it goes into a loop like this bellow:
>>
>> <code>
>> INFO: task swapper:1 blocked for more than 120 seconds.
>> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> swapper D ffff880004217d88 0 1 0 2
>> (L-TLB)
>> ffff880004217c90 0000000000000246 0000000000000000 ffff8800010f3460
>> 0000000000000008 ffff88000425c7a0 ffff88001fa51860 0000000000001678
>> ffff88000425c988 00000000000520a1
>> Call Trace:
>> [<ffffffff80287879>] __wake_up_common+0x3e/0x68
>> [<ffffffff80262fb3>] wait_for_completion+0x7d/0xaa
>> [<ffffffff8028906a>] default_wake_function+0x0/0xe
>> [<ffffffff80258b30>] pdflush+0x0/0x207
>> [<ffffffff8029c577>] kthread_create+0xc1/0x141
>> [<ffffffff8029c3f2>] keventd_create_kthread+0x0/0xc4
>> [<ffffffff80258b30>] pdflush+0x0/0x207
>> [<ffffffff802889dd>] enqueue_task+0x41/0x56
>> [<ffffffff80288a48>] __activate_task+0x56/0x6d
>> [<ffffffff802490c3>] try_to_wake_up+0x392/0x3a4
>> [<ffffffff80264931>] _spin_lock_irqsave+0x9/0x14
>> [<ffffffff802c1187>] start_one_pdflush_thread+0x1b/0x2e
>> [<ffffffff8065d20a>] pdflush_init+0xa/0x13
>> [<ffffffff8064c7eb>] init+0x1f9/0x2fe
>> [<ffffffff80260b2c>] child_rip+0xa/0x12
>> [<ffffffff8064c5f2>] init+0x0/0x2fe
>> [<ffffffff80260b22>] child_rip+0x0/0x12
>> </code>
>>
>> This problem occurs only on HP blades model HP ProLiant BL460c G6 [1].
>> Others servers running XenServer or XCP the problem does not occur.
>>
>>
>> [1]
>> http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/3709945-3709945-3328410-241641-3328419-3884098.html
>>
>> Cheers,
>>
>> --
>> Marco Sinhoreli
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
--
Marco Sinhoreli
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
|
|
| |
|
Home