Mailing List Archive

Hi Qiaowei,

It sounds a xen/dom0 kernel problem rather than a problem specifically
with buildroot.

On CentOS, buildroot currently uses a fork of the Xen4CentOS bits and
pieces to get Xen and a suitable kernel. We have a plan to get back to
using the standard repository, but it's a bit fiddly. For now, could you
please verify whether using the current Xen4CentOS instructions [1] gets
you a usable dom0?

Cheers,

Jon

[1] http://wiki.centos.org/HowTos/Xen/Xen4QuickStart

On 31/05/14 02:47, Ren, Qiaowei wrote:
>
> Hi Everyone,
>
>
>
> I tried latest buildroot (https://github.com/xenserver/buildroot) and
> it could be built and installed smoothly. But unfortunately, after
> "xenserver-install-wizard" with all default answers, the system could
> not booted successfully into xen and always autoreset during booting
> and print some call trace information due to panic:
>
>
>
> Xen call trace:
>
> [<ffff82c4802721e8>] setup_boot_APIC_clock+0x178/0x340
>
> [<ffff82c4802728ad>] APIC_init_uniprocessor+0xad/0x120
>
> [<ffff82c48027cf68>] smp_prepare_cpus+0x1d8/0x240
>
> [<ffff82c48027c6a1>] __start_xen+0x3451/0x38c0
>
> [<ffff82c4801000b5>] __high_start+0xa1/0xa3
>
>
>
> **************************************
>
> Panic on CPU 0:
>
> FATAL TRAP: vector = 0 (divide error)
>
> [Error_code=0000]
>
> **************************************
>
>
>
> Reboot in five seconds...
>
>
>
> My environment is virtualbox + CentOS 6.5(no separate /boot partition)
> + bridged network, and proxy must be set in our side.
>
>
>
> In addition, the issue
> https://github.com/xenserver/buildroot/issues/205
> <https://github.com/xenserver/buildroot/issues/205> still exists:
>
> /etc/init.d/message-switch: line 61: status_of_proc: command not found
>
> /etc/init.d/forkexecd: line 59: status_of_proc: command not found
>
> /etc/init.d/xcp-networkd: line 59: status_of_proc: command not found
>
> /etc/init.d/ffs: line 59: status_of_proc: command not found
>
> /etc/init.d/xapi: line 79: status_of_proc: command not found
>
>
>
> Thanks,
>
> Qiaowei
>
>
>
>
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Hi Jon,

I just tried the building and installation according to the guide https://github.com/xenserver/buildroot.

./configure.sh
make
make install
xenserver-install-wizard
reboot

And I didn't install xen and centos-release-xen through 'yum install', as http://wiki.centos.org/HowTos/Xen/Xen4QuickStart mentioned.

Thanks,
Qiaowei



On 2014-06-02, Jan Beulich wrote:
It sounds a xen/dom0 kernel problem rather than a problem specifically with buildroot.

On CentOS, buildroot currently uses a fork of the Xen4CentOS bits and pieces to get Xen and a suitable kernel. We have a plan to get back to using the standard repository, but it's a bit fiddly. For now, could you please verify whether using the current Xen4CentOS instructions [1] gets you a usable dom0?

Cheers,

Jon

[1] http://wiki.centos.org/HowTos/Xen/Xen4QuickStart

On 31/05/14 02:47, Ren, Qiaowei wrote:
Hi Everyone,

I tried latest buildroot (https://github.com/xenserver/buildroot) and it could be built and installed smoothly. But unfortunately, after "xenserver-install-wizard" with all default answers, the system could not booted successfully into xen and always autoreset during booting and print some call trace information due to panic:

Xen call trace:
[<ffff82c4802721e8>] setup_boot_APIC_clock+0x178/0x340
[<ffff82c4802728ad>] APIC_init_uniprocessor+0xad/0x120
[<ffff82c48027cf68>] smp_prepare_cpus+0x1d8/0x240
[<ffff82c48027c6a1>] __start_xen+0x3451/0x38c0
[<ffff82c4801000b5>] __high_start+0xa1/0xa3

**************************************
Panic on CPU 0:
FATAL TRAP: vector = 0 (divide error)
[Error_code=0000]
**************************************

Reboot in five seconds...


My environment is virtualbox + CentOS 6.5(no separate /boot partition) + bridged network, and proxy must be set in our side.

In addition, the issue https://github.com/xenserver/buildroot/issues/205 still exists:

/etc/init.d/message-switch: line 61: status_of_proc: command not found

/etc/init.d/forkexecd: line 59: status_of_proc: command not found

/etc/init.d/xcp-networkd: line 59: status_of_proc: command not found

/etc/init.d/ffs: line 59: status_of_proc: command not found

/etc/init.d/xapi: line 79: status_of_proc: command not found

Thanks,
Qiaowei





_______________________________________________

Xen-api mailing list

Xen-api@lists.xen.org<mailto:Xen-api@lists.xen.org>

http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Hi Qiaowei,

On 02/06/14 12:59, Ren, Qiaowei wrote:
>
> Hi Jon,
>
>
>
> I just tried the building and installation according to the guide
> https://github.com/xenserver/buildroot.
>
>
>
> ./configure.sh
>
> make
>
> make install
>
> xenserver-install-wizard
>
> reboot
>

This has the side effect of installing xen and a dom0 kernel, but these
both come from a non-standard location.

>
>
> And I didn't install xen and centos-release-xen through 'yum install',
> as http://wiki.centos.org/HowTos/Xen/Xen4QuickStart mentioned.
>
>
>
> Thanks,
>
> Qiaowei
>
>
>
That Xen quickstart is the 'standard' location for getting xen up and
running on CentOS. Could you please try that and see if that works for
you - if so, it indicates a problem with one of those two things in our
non-standard location. If that is the case, the solution is to use the
normal Xen4CentOS repositories, which requires a bit of work in
buildroot, which we're going to work on soon.

I note you're using Virtualbox - I have had this working, but I have
also noticed many crashes while using it. I'd certainly recommend using
a physical machine for this, as it'll be much more reliable.

Cheers,

Jon

Hi Jon,

You mean I should first install Xen according to "Xen4QuickStart" wiki and then install xenserver, right?

Thanks,
Qiaowei

From: Jon Ludlam [mailto:jonathan.ludlam@eu.citrix.com]
Sent: Monday, June 02, 2014 8:14 PM
To: Ren, Qiaowei; xen-api@lists.xen.org
Subject: Re: [Xen-API] the system panic with latest buildroot

Hi Qiaowei,

On 02/06/14 12:59, Ren, Qiaowei wrote:
Hi Jon,

I just tried the building and installation according to the guide https://github.com/xenserver/buildroot.

./configure.sh
make
make install
xenserver-install-wizard
reboot

This has the side effect of installing xen and a dom0 kernel, but these both come from a non-standard location.



And I didn't install xen and centos-release-xen through 'yum install', as http://wiki.centos.org/HowTos/Xen/Xen4QuickStart mentioned.

Thanks,
Qiaowei

That Xen quickstart is the 'standard' location for getting xen up and running on CentOS. Could you please try that and see if that works for you - if so, it indicates a problem with one of those two things in our non-standard location. If that is the case, the solution is to use the normal Xen4CentOS repositories, which requires a bit of work in buildroot, which we're going to work on soon.

I note you're using Virtualbox - I have had this working, but I have also noticed many crashes while using it. I'd certainly recommend using a physical machine for this, as it'll be much more reliable.

Cheers,

Jon

On 03/06/14 03:02, Ren, Qiaowei wrote:
>
> Hi Jon,
>
>
>
> You mean I should first install Xen according to “Xen4QuickStart” wiki
> and then install xenserver, right?
>
Just follow the instructions from Xen4QuickStart - you won't get the
xenserver bits, but at least we can tell whether xen works at all on
your virtualbox.

Jon

>
>
> Thanks,
>
> Qiaowei
>
>

I tried, but unfortunately this problem was still met. So it should be Xen and Dom0 issue. Maybe I should also find one real server to try it, instead of virtualbox. Or I can try Fedora or other distros.

Thanks,
Qiaowei

From: Jon Ludlam [mailto:jjl25@cam.ac.uk]
Sent: Tuesday, June 03, 2014 4:01 PM
To: Ren, Qiaowei; xen-api@lists.xen.org
Subject: Re: [Xen-API] the system panic with latest buildroot

On 03/06/14 03:02, Ren, Qiaowei wrote:
Hi Jon,

You mean I should first install Xen according to “Xen4QuickStart” wiki and then install xenserver, right?
Just follow the instructions from Xen4QuickStart - you won't get the xenserver bits, but at least we can tell whether xen works at all on your virtualbox.

Jon



Thanks,
Qiaowei