Hi Johnny, Thanks a lot. I'll upgrade kernel to the cr repository, and give it a try now. --Guolin ________________________________ From: Johnny Hughes <johnny at centos.org> To: centos at centos.org Sent: Wednesday, November 23, 2011 9:55 AM Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote: > I tried several ways but still no help. The following are the output (stock Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located kernel and initial ramdisk. but kernel booting faied at the very beginning... > > Any suggestions are more than appreciated. > > > -------------------------------------------------- > > 2011-11-23T17:19:21+0000 > Xen Minimal OS! > start_info: 0x1890000(VA) > nr_pages: 0x1e0000 > shared_inf: 0xb2cea000(MA) > pt_base: 0x1893000(VA) > nr_pt_frames: 0x11 > mfn_list: 0x990000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: root=/dev/sda1 ro 4 > stack: 0x94f860-0x96f860 > MM: Init > _text: 0x0(VA) > _etext: 0x6000d(VA) > _erodata: 0x78000(VA) > _edata: 0x80b00(VA) > stack start: 0x94f860(VA) > _end: 0x98fe68(VA) > start_pfn: 18a7 > max_pfn: 1e0000 > Mapping memory range 0x1c00000 - 0x1e0000000 > setting 0x0-0x78000 readonly > skipped 0x1000 > MM: Initialise page allocator for 27a0000(27a0000)-1e0000000(1e0000000) > MM: done > Demand map pfns at 1e0001000-21e0001000. > Heap resides at 21e0002000-41e0002000. > Initialising timer interface > Initialising console ... done. > gnttab_table mapped at 0x1e0001000. > Initialising scheduler > Thread "Idle": pointer: 0x21e0002010, stack: 0x36f0000 > Initialising xenbus > Thread "xenstore": pointer: 0x21e00027c0, stack: 0x3700000 > Dummy main: start_info=0x96f960 > Thread "main": pointer: 0x21e0002f70, stack: 0x3710000 > "main" "root=/dev/sda1" "ro" "4" > vbd 2049 is hd0 > ******************* BLKFRONT for device/vbd/2049 ********** > > > backend at /local/domain/0/backend/vbd/162/2049 > Failed to read /local/domain/0/backend/vbd/162/2049/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache. > 20971520 sectors of 512 bytes > ************************** > vbd 2064 is hd1 > ******************* BLKFRONT for device/vbd/2064 ********** > > > backend at /local/domain/0/backend/vbd/162/2064 > Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache. > 880732160 sectors of 512 bytes > ************************** > vbd 2080 is hd2 > ******************* BLKFRONT for device/vbd/2080 ********** > > > backend at /local/domain/0/backend/vbd/162/2080 > Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier. > Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache. > 880732160 sectors of 512 bytes > ************************** > [H[J > GNU GRUB version 0.97 (7864320K lower / 0K upper memory) > > [m[4;2H+-------------------------------------------------------------------------+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-------------------------------------------------------------------------+[m > Use the ^ and v keys to select which entry is highlighted. > Press enter to boot the selected OS, 'e' to edit the > commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H CentOS (2.6.32-71.29.1.el6.x86_64) [5;75H[m[m[6;3H [6;75H[m[m[7;3H [7;75H[m[m[8;3H [8;75H[m[m[9;3H > [9;75H[m[m[10;3H [10;75H[m[m[11;3H [11;75H[m[m[12;3H [12;75H[m[m[13;3H [13;75H[m[m[14;3H > [14;75H[m[m[15;3H [15;75H[m[m[16;3H [16;75H[m[16;78H [5;75H[23;4H The highlighted entry will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 4 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 2 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 1 seconds. [5;75H[H[J Booting 'CentOS (2.6.32-71.29.1.el6.x86_64)' > > root (hd0) > Filesystem type is ext2fs, using whole disk > > kernel /boot/vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/sda1 rhgb quiet > initrd /boot/initramfs-2.6.32-71.29.1.el6.x86_64.img > > close blk: backend at /local/domain/0/backend/vbd/162/2049 > close blk: backend at /local/domain/0/backend/vbd/162/2064 > close blk: backend at /local/domain/0/backend/vbd/162/2080 > PCI: Warning: Cannot find a gap in the 32bit address range > PCI: Unassigned devices with 32bit resource registers may break! > PCI: Fatal: No config space access function found > > Boot has failed, sleeping forever. > > > > > > > ________________________________ > From: Robinson Tiemuqinke <hahaha_30k at yahoo.com> > To: CentOS mailing list <centos at centos.org> > Sent: Tuesday, November 22, 2011 3:35 PM > Subject: [CentOS] EC2 compatible kernel for centos 6? > > Hi all, > > I'm just scrambling to collect clues to build an Amazon AWS AMI based on Centos 6. the AWS PV-GRUB kernel loads my kernel but failed immediately. I'm using stock Centos 6 kernel 2.6.32-71.29.1.el6. and the kernel seems have xen? support? My questions are: > > 1, Are the centos 6 stock kernels, like kernel-2.6.32-71.29.1.el6.x86_64, EC2 compatible? > > 2, If the answer to the above #1 question is NO, the are the centos plus kernels, like kernel-2.6.32-71.29.1.el6.centos.plus.x86_64, EC2 compatible? > > 3, If the answers to both above are 'NO', then Are there any instructions to build a EC2 kernel based on kernel source RPMs? > > > Any help are greatly appreciated. > > --Tie I do not use amazon services, but does this help: https://forums.aws.amazon.com/thread.jspa?threadID=78007 _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos