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@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
