Fabian Lueghausen
2008-Mar-28  09:34 UTC
[Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Hello list,
I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this 
mission failed.. Hope you can help me by finding the reason for my problem.
I downloaded the xen sources from 
http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz 
and compiled them by running "make" and "./install.sh". This
seemed to
work.
After setting up grub like this,
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to
    this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/hda3 console=tty0
    console=ttyS0,9600
    #          initrd /initrd-version.img
    boot=/dev/hda1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    #
    title Scientific Linux (2.6.9-11.EL)
     root (hd0,0)
     kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0
    console=ttyS0,9600
     initrd /initrd-2.6.9-11.EL.img
    *#
    title Xen 3.1 / XenLinux 2.6
     root (hd0,0)
     kernel /xen-3.1.0.gz dom0_mem=256000 noreboot
     module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0
    console=ttyS0,9600**
     module /initrd-2.6.18-xen.img
    *
I shut down my machine and restarted it. But it won''t come up... as you
can see right here:
    (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot
        (...)
    System RAM: 511MB (523356KB)
    Xen heap: 10MB (10272KB)
    Domain heap initialised: DMA with 32 bits
    PAE enabled, limit: 16GB
    Processor #0 15:0 APIC version 20
    IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23
    Enabling APIC mode: Flat, Using 1 I/O APICs
    Using scheduler: SMP Credit Scheduler (credit)
    Detected 1694.889MHz processor
    CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a
    Mapping CPU0 to node 255
    Total of 1 processors activated.
    ENABLING IO-APIC IRQs
     -> Using new ACK method
    Platform timer is 1.193MHz PIT
    Brought up 1 CPUs
    *** LOADING DOMAIN 0 ***
     Xen kernel: 32-bit, PAE, lsb
     Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c
    PHYSICAL MEMORY ARRANGEMENT:
     Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to
    be allocated)
    VIRTUAL MEMORY ARRANGEMENT:
     Loaded kernel: c....... -> c.......
     Init. ramdisk: c....... -> c.......
     Phys-Mach mag: c....... -> c.......
     Start info:    c....... -> c.......
     Page tables:   c....... -> c.......
     Boot stack:    c....... -> c.......
     TOTAL:         c....... -> c.......
     ENTRY ADRESS:  c....... -> c.......
    Dom0 has maximum 1VCPUs
    Initrd len 0x112200, start at 0xc0460000
    Scrubbing Free RAM: .. done.
    Xen trace buffers: disabled
    Std Loglevel: Errors and warnings
    Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
    *Kernel Panic - not syncing: Attempted to kill init!*
Is there anyone who has an idea what I''m doing wrong?! Tried it by 
myself for a few hours, but I''m in the dark...
Thanks for every reply to this email!
Ciao,
Fabian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fabian Lueghausen
2008-Mar-28  09:51 UTC
[Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Hello list,
I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this 
mission failed.. Hope you can help me by finding the reason for my problem.
I downloaded the xen sources from 
http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz 
and compiled them by running "make" and "./install.sh". This
seemed to
work.
After setting up grub like this,
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to
    this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/hda3 console=tty0
    console=ttyS0,9600
    #          initrd /initrd-version.img
    boot=/dev/hda1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    #
    title Scientific Linux (2.6.9-11.EL)
     root (hd0,0)
     kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0
    console=ttyS0,9600
     initrd /initrd-2.6.9-11.EL.img
    *#
    title Xen 3.1 / XenLinux 2.6
     root (hd0,0)
     kernel /xen-3.1.0.gz dom0_mem=256000 noreboot
     module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0
    console=ttyS0,9600**
     module /initrd-2.6.18-xen.img
    *
I shut down my machine and restarted it. But it won''t come up... as you
can see right here:
    (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot
        (...)
    System RAM: 511MB (523356KB)
    Xen heap: 10MB (10272KB)
    Domain heap initialised: DMA with 32 bits
    PAE enabled, limit: 16GB
    Processor #0 15:0 APIC version 20
    IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23
    Enabling APIC mode: Flat, Using 1 I/O APICs
    Using scheduler: SMP Credit Scheduler (credit)
    Detected 1694.889MHz processor
    CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a
    Mapping CPU0 to node 255
    Total of 1 processors activated.
    ENABLING IO-APIC IRQs
     -> Using new ACK method
    Platform timer is 1.193MHz PIT
    Brought up 1 CPUs
    *** LOADING DOMAIN 0 ***
     Xen kernel: 32-bit, PAE, lsb
     Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c
    PHYSICAL MEMORY ARRANGEMENT:
     Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to
    be allocated)
    VIRTUAL MEMORY ARRANGEMENT:
     Loaded kernel: c....... -> c.......
     Init. ramdisk: c....... -> c.......
     Phys-Mach mag: c....... -> c.......
     Start info:    c....... -> c.......
     Page tables:   c....... -> c.......
     Boot stack:    c....... -> c.......
     TOTAL:         c....... -> c.......
     ENTRY ADRESS:  c....... -> c.......
    Dom0 has maximum 1VCPUs
    Initrd len 0x112200, start at 0xc0460000
    Scrubbing Free RAM: .. done.
    Xen trace buffers: disabled
    Std Loglevel: Errors and warnings
    Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
    *Kernel Panic - not syncing: Attempted to kill init!*
Is there anyone who has an idea what I''m doing wrong?! Tried it by 
myself for a few hours, but I''m in the dark...
Thanks for every reply to this email!
Ciao,
Fabian
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2008-Mar-28  09:59 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Fabian Lueghausen wrote:> Hello list, > > I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this > mission failed.. Hope you can help me by finding the reason for my > problem.Is there a particular need for Scientific/RHEL4? You might find it easier to simply use Centos/RHEL5.1 (which comes with Xen 3.1) as dom0, and use RHEL4 as domU. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2008-Mar-28  09:59 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Fabian Lueghausen wrote:> Hello list, > > I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this > mission failed.. Hope you can help me by finding the reason for my > problem.Is there a particular need for Scientific/RHEL4? You might find it easier to simply use Centos/RHEL5.1 (which comes with Xen 3.1) as dom0, and use RHEL4 as domU. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fabian Lueghausen
2008-Mar-28  10:25 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Thanks for your reply! The answer is unfortunately: Yes, there is a need für Scientific/RHEL4. I can''t change this distribution, sorry! Any idea? Fabian Fajar A. Nugraha schrieb:> Fabian Lueghausen wrote: >> Hello list, >> >> I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this >> mission failed.. Hope you can help me by finding the reason for my >> problem. > > Is there a particular need for Scientific/RHEL4? > You might find it easier to simply use Centos/RHEL5.1 (which comes > with Xen 3.1) as dom0, and use RHEL4 as domU. > > Regards, > > Fajar > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Timm
2008-Mar-28  14:34 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Fabian--did you do a depmod on the kernel tree and do a mkinitrd on your machine after you compiled the kernel? The error you are getting to me looks like you do not have the block devices loaded right in the initrd images you have and thus it can''t find the root directory to continue the linux boot, maybe it is not even loading the vmlinuz-2.6.18xen correctly. Or did you try to use the pre-built rpms or tarballs for RHEL/SL that are on the www.xen.org site? I have not tried the 3.1.0 version of those on SL4 but there are rpms there for SL4. I did use the Xen 3.0.4 precompiled version for SL4 on SL4 and that works fine. Steve Timm On Fri, 28 Mar 2008, Fabian Lueghausen wrote:> Hello list, > > I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission > failed.. Hope you can help me by finding the reason for my problem. > I downloaded the xen sources from > http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz and > compiled them by running "make" and "./install.sh". This seemed to work. > After setting up grub like this, > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to > this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/hda3 console=tty0 > console=ttyS0,9600 > # initrd /initrd-version.img > boot=/dev/hda1 > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > # > title Scientific Linux (2.6.9-11.EL) > root (hd0,0) > kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0 > console=ttyS0,9600 > initrd /initrd-2.6.9-11.EL.img > *# > title Xen 3.1 / XenLinux 2.6 > root (hd0,0) > kernel /xen-3.1.0.gz dom0_mem=256000 noreboot > module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0 > console=ttyS0,9600** > module /initrd-2.6.18-xen.img > * > > I shut down my machine and restarted it. But it won''t come up... as you can > see right here: > > (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot > > (...) > > System RAM: 511MB (523356KB) > Xen heap: 10MB (10272KB) > Domain heap initialised: DMA with 32 bits > PAE enabled, limit: 16GB > Processor #0 15:0 APIC version 20 > IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23 > Enabling APIC mode: Flat, Using 1 I/O APICs > Using scheduler: SMP Credit Scheduler (credit) > Detected 1694.889MHz processor > CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a > Mapping CPU0 to node 255 > Total of 1 processors activated. > ENABLING IO-APIC IRQs > -> Using new ACK method > Platform timer is 1.193MHz PIT > Brought up 1 CPUs > *** LOADING DOMAIN 0 *** > Xen kernel: 32-bit, PAE, lsb > Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c > PHYSICAL MEMORY ARRANGEMENT: > Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to > be allocated) > VIRTUAL MEMORY ARRANGEMENT: > Loaded kernel: c....... -> c....... > Init. ramdisk: c....... -> c....... > Phys-Mach mag: c....... -> c....... > Start info: c....... -> c....... > Page tables: c....... -> c....... > Boot stack: c....... -> c....... > TOTAL: c....... -> c....... > ENTRY ADRESS: c....... -> c....... > Dom0 has maximum 1VCPUs > Initrd len 0x112200, start at 0xc0460000 > Scrubbing Free RAM: .. done. > Xen trace buffers: disabled > Std Loglevel: Errors and warnings > Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > *Kernel Panic - not syncing: Attempted to kill init!* > > Is there anyone who has an idea what I''m doing wrong?! Tried it by myself for > a few hours, but I''m in the dark... > > Thanks for every reply to this email! > > Ciao, > Fabian > >-- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fabian Lueghausen
2008-Mar-28  15:39 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
Hey Steven, yes, I did a depmod on the kernel tree and created an initrd after compiling the kernel. This initrd image is being loaded when starting the machine. The latest prebuilt rpm''s on www.xen.org are for RHEL*5*, *not* *4*. I tried to run the rpm for *xen 3.0.2* and *RHEL4.1* (downloaded in the archiv <http://www.xen.org/download/dl_x30rhel4.html>) but this did not work, because PAE is not supported by this package. Thanks for this hint! *More ideas? * Fabian Steven Timm schrieb:> Fabian--did you do a depmod on the kernel tree and do a mkinitrd > on your machine after you compiled the kernel? The error > you are getting to me looks like you do not have the block > devices loaded right in the initrd images you have and thus > it can''t find the root directory to continue > the linux boot, maybe it is not even loading the vmlinuz-2.6.18xen > correctly. > > Or did you try to use the pre-built rpms or tarballs for RHEL/SL that > are on the www.xen.org site? I have not tried the 3.1.0 version > of those on SL4 but there are rpms there for SL4. I did use the > Xen 3.0.4 precompiled version for SL4 on SL4 and that works fine. > > Steve Timm > > > On Fri, 28 Mar 2008, Fabian Lueghausen wrote: > >> Hello list, >> >> I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this >> mission failed.. Hope you can help me by finding the reason for my >> problem. >> I downloaded the xen sources from >> http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz >> and compiled them by running "make" and "./install.sh". This seemed >> to work. >> After setting up grub like this, >> >> # grub.conf generated by anaconda >> # >> # Note that you do not have to rerun grub after making changes to >> this file >> # NOTICE: You have a /boot partition. This means that >> # all kernel and initrd paths are relative to /boot/, eg. >> # root (hd0,0) >> # kernel /vmlinuz-version ro root=/dev/hda3 console=tty0 >> console=ttyS0,9600 >> # initrd /initrd-version.img >> boot=/dev/hda1 >> default=0 >> timeout=5 >> splashimage=(hd0,0)/grub/splash.xpm.gz >> hiddenmenu >> # >> title Scientific Linux (2.6.9-11.EL) >> root (hd0,0) >> kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0 >> console=ttyS0,9600 >> initrd /initrd-2.6.9-11.EL.img >> *# >> title Xen 3.1 / XenLinux 2.6 >> root (hd0,0) >> kernel /xen-3.1.0.gz dom0_mem=256000 noreboot >> module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0 >> console=ttyS0,9600** >> module /initrd-2.6.18-xen.img >> * >> >> I shut down my machine and restarted it. But it won''t come up... as >> you can see right here: >> >> (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot >> >> (...) >> >> System RAM: 511MB (523356KB) >> Xen heap: 10MB (10272KB) >> Domain heap initialised: DMA with 32 bits >> PAE enabled, limit: 16GB >> Processor #0 15:0 APIC version 20 >> IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23 >> Enabling APIC mode: Flat, Using 1 I/O APICs >> Using scheduler: SMP Credit Scheduler (credit) >> Detected 1694.889MHz processor >> CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a >> Mapping CPU0 to node 255 >> Total of 1 processors activated. >> ENABLING IO-APIC IRQs >> -> Using new ACK method >> Platform timer is 1.193MHz PIT >> Brought up 1 CPUs >> *** LOADING DOMAIN 0 *** >> Xen kernel: 32-bit, PAE, lsb >> Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c >> PHYSICAL MEMORY ARRANGEMENT: >> Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to >> be allocated) >> VIRTUAL MEMORY ARRANGEMENT: >> Loaded kernel: c....... -> c....... >> Init. ramdisk: c....... -> c....... >> Phys-Mach mag: c....... -> c....... >> Start info: c....... -> c....... >> Page tables: c....... -> c....... >> Boot stack: c....... -> c....... >> TOTAL: c....... -> c....... >> ENTRY ADRESS: c....... -> c....... >> Dom0 has maximum 1VCPUs >> Initrd len 0x112200, start at 0xc0460000 >> Scrubbing Free RAM: .. done. >> Xen trace buffers: disabled >> Std Loglevel: Errors and warnings >> Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >> *Kernel Panic - not syncing: Attempted to kill init!* >> >> Is there anyone who has an idea what I''m doing wrong?! Tried it by >> myself for a few hours, but I''m in the dark... >> >> Thanks for every reply to this email! >> >> Ciao, >> Fabian >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Timm
2008-Mar-28  15:55 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
If you can get to the archives, follow the link to xen 3.0.4, that has prebuilts for RHEL4 and it supports pae. It doesn''t support 32 on 64 though, and the prebuilts are only for 32-bit. There are rhel4.5 prebuilt rpms on xen 3.1.0 too for 32 bit but I have not tried them. And as far as the initrd.img, make sure it is a reasonable size, something like 2.5MB, if you do it wrong it will be much smaller than that. Steve On Fri, 28 Mar 2008, Fabian Lueghausen wrote:> Hey Steven, > > yes, I did a depmod on the kernel tree and created an initrd after compiling > the kernel. This initrd image is being loaded when starting the machine. > The latest prebuilt rpm''s on www.xen.org are for RHEL*5*, *not* *4*. > I tried to run the rpm for *xen 3.0.2* and *RHEL4.1* (downloaded in the > archiv <http://www.xen.org/download/dl_x30rhel4.html>) but this did not work, > because PAE is not supported by this package. > Thanks for this hint! > > *More ideas? * > > Fabian > > > Steven Timm schrieb: >> Fabian--did you do a depmod on the kernel tree and do a mkinitrd >> on your machine after you compiled the kernel? The error >> you are getting to me looks like you do not have the block >> devices loaded right in the initrd images you have and thus >> it can''t find the root directory to continue >> the linux boot, maybe it is not even loading the vmlinuz-2.6.18xen >> correctly. >> >> Or did you try to use the pre-built rpms or tarballs for RHEL/SL that >> are on the www.xen.org site? I have not tried the 3.1.0 version >> of those on SL4 but there are rpms there for SL4. I did use the >> Xen 3.0.4 precompiled version for SL4 on SL4 and that works fine. >> >> Steve Timm >> >> >> On Fri, 28 Mar 2008, Fabian Lueghausen wrote: >> >>> Hello list, >>> >>> I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but this mission >>> failed.. Hope you can help me by finding the reason for my problem. >>> I downloaded the xen sources from >>> http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz >>> and compiled them by running "make" and "./install.sh". This seemed to >>> work. >>> After setting up grub like this, >>> >>> # grub.conf generated by anaconda >>> # >>> # Note that you do not have to rerun grub after making changes to >>> this file >>> # NOTICE: You have a /boot partition. This means that >>> # all kernel and initrd paths are relative to /boot/, eg. >>> # root (hd0,0) >>> # kernel /vmlinuz-version ro root=/dev/hda3 console=tty0 >>> console=ttyS0,9600 >>> # initrd /initrd-version.img >>> boot=/dev/hda1 >>> default=0 >>> timeout=5 >>> splashimage=(hd0,0)/grub/splash.xpm.gz >>> hiddenmenu >>> # >>> title Scientific Linux (2.6.9-11.EL) >>> root (hd0,0) >>> kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet console=tty0 >>> console=ttyS0,9600 >>> initrd /initrd-2.6.9-11.EL.img >>> *# >>> title Xen 3.1 / XenLinux 2.6 >>> root (hd0,0) >>> kernel /xen-3.1.0.gz dom0_mem=256000 noreboot >>> module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet console=tty0 >>> console=ttyS0,9600** >>> module /initrd-2.6.18-xen.img >>> * >>> >>> I shut down my machine and restarted it. But it won''t come up... as you >>> can see right here: >>> >>> (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot >>> >>> (...) >>> >>> System RAM: 511MB (523356KB) >>> Xen heap: 10MB (10272KB) >>> Domain heap initialised: DMA with 32 bits >>> PAE enabled, limit: 16GB >>> Processor #0 15:0 APIC version 20 >>> IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23 >>> Enabling APIC mode: Flat, Using 1 I/O APICs >>> Using scheduler: SMP Credit Scheduler (credit) >>> Detected 1694.889MHz processor >>> CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a >>> Mapping CPU0 to node 255 >>> Total of 1 processors activated. >>> ENABLING IO-APIC IRQs >>> -> Using new ACK method >>> Platform timer is 1.193MHz PIT >>> Brought up 1 CPUs >>> *** LOADING DOMAIN 0 *** >>> Xen kernel: 32-bit, PAE, lsb >>> Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc045f53c >>> PHYSICAL MEMORY ARRANGEMENT: >>> Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952 pages to >>> be allocated) >>> VIRTUAL MEMORY ARRANGEMENT: >>> Loaded kernel: c....... -> c....... >>> Init. ramdisk: c....... -> c....... >>> Phys-Mach mag: c....... -> c....... >>> Start info: c....... -> c....... >>> Page tables: c....... -> c....... >>> Boot stack: c....... -> c....... >>> TOTAL: c....... -> c....... >>> ENTRY ADRESS: c....... -> c....... >>> Dom0 has maximum 1VCPUs >>> Initrd len 0x112200, start at 0xc0460000 >>> Scrubbing Free RAM: .. done. >>> Xen trace buffers: disabled >>> Std Loglevel: Errors and warnings >>> Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >>> *Kernel Panic - not syncing: Attempted to kill init!* >>> >>> Is there anyone who has an idea what I''m doing wrong?! Tried it by myself >>> for a few hours, but I''m in the dark... >>> >>> Thanks for every reply to this email! >>> >>> Ciao, >>> Fabian >>> >>> >> > > >-- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fabian Lueghausen
2008-Mar-28  18:01 UTC
Re: [Xen-users] Booting dom0: Kernel Panic - not syncing: Attempted to kill init!
I tried this, but the result is the same as before.
Uninstalled the old package and installed xen-3.0.4.1-1.i386.rpm 
<http://bits.xensource.com/oss-xen/release/3.0.4-1/kernel-3.0.4-rhel4x/RPMS/i386/xen-3.0.4.1-1.i386.rpm>...
No Chance!
I also made a new initrd:
    *depmod 2.6.16-xen
    mkinitrd /boot/initrd-2.6.16-xen.img 2.6.16-xen*
    *ls -l /boot/*
    insgesamt 20268
    -rw-rw-r--  1 root root   60367 13. Apr 2006  config-2.6.16-xen
    -rw-rw-r--  1 root root   65773 25. Mär 12:02 config-2.6.18-xen
    -rw-r--r--  1 root root   48299  9. Jun 2005  config-2.6.9-11.EL
    drwxr-xr-x  2 root root    1024 28. Mär 18:29 grub
    -rw-r--r--  1 root root  402831 28. Mär 18:08 initrd-2.6.16-xen.img
    -rw-r--r--  1 root root  514762 18. Mär 16:27 initrd-2.6.18-xen.img
    -rw-r--r--  1 root root  398126 27. Jul 2006  initrd-2.6.9-11.EL.img
    drwx------  2 root root   12288 27. Jul 2006  lost+found
    -rw-r--r--  1 root root   81860 17. Feb 2005  memtest86+-1.26
    -rw-r--r--  1 root root   15401 18. Apr 2005  message
    -rw-r--r--  1 root root   15401 18. Apr 2005  message.ja
    -rw-rw-r--  1 root root  807208 13. Apr 2006  System.map-2.6.16-xen
    -rw-rw-r--  1 root root  789972 25. Mär 12:02 System.map-2.6.18-xen
    -rw-r--r--  1 root root  715755  9. Jun 2005  System.map-2.6.9-11.EL
    -rw-r--r--  1 root root 4276240 13. Apr 2006  vmlinux-syms-2.6.16-xen
    -rw-r--r--  1 root root 4219038 25. Mär 12:02 vmlinux-syms-2.6.18-xen
    -rw-r--r--  1 root root 1529773 13. Apr 2006  vmlinuz-2.6.16-xen
    -rw-r--r--  1 root root 1524718 25. Mär 12:02 vmlinuz-2.6.18-xen
    -rw-r--r--  1 root root 1435233  9. Jun 2005  vmlinuz-2.6.9-11.EL
    lrwxrwxrwx  1 root root      18 28. Mär 17:01 vmlinuz-2.6-xen ->
    vmlinuz-2.6.16-xen
    -rw-r--r--  1 root root  268787  5. Jan 2007  xen-3.0.4.1.gz
    lrwxrwxrwx  1 root root      14 28. Mär 17:30 xen-3.0.gz ->
    xen-3.0.4.1.gz
    lrwxrwxrwx  1 root root      14 28. Mär 17:30 xen-3.gz -> xen-3.0.4.1.gz
    lrwxrwxrwx  1 root root      14 28. Mär 17:30 xen.gz -> xen-3.0.4.1.gz
    -rw-r--r--  1 root root 3433684  5. Jan 2007  xen-syms-3.0.4.1
    *more /boot/grub/menu.lst*
    boot=/dev/hda1
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    #
    title Xen 3.0 / XenLinux 2.6
     root (hd0,0)
     kernel /xen.gz dom0_mem=256000
     module /vmlinuz-2.6-xen ro root=LABEL=/ rhgb quiet console=tty0
    console=ttyS0,9600
     module /initrd-2.6.16-xen.img
But... no success at all!
:-|
Fabian
Steven Timm schrieb:> If you can get to the archives, follow the link to xen 3.0.4,
> that has prebuilts for RHEL4 and it supports pae.
> It doesn''t support 32 on 64 though, and the prebuilts are only
> for 32-bit.
>
> There are rhel4.5 prebuilt rpms on xen 3.1.0 too for 32 bit but
> I have not tried them.
>
> And as far as the initrd.img, make sure it is a reasonable size,
> something like 2.5MB, if you do it wrong it will be much smaller
> than that.
>
> Steve
>
>
> On Fri, 28 Mar 2008, Fabian Lueghausen wrote:
>
>> Hey Steven,
>>
>> yes, I did a depmod on the kernel tree and created an initrd after 
>> compiling the kernel. This initrd image is being loaded when starting 
>> the machine.
>> The latest prebuilt rpm''s on www.xen.org are for RHEL*5*,
*not* *4*.
>> I tried to run the rpm for *xen 3.0.2* and *RHEL4.1* (downloaded in 
>> the archiv <http://www.xen.org/download/dl_x30rhel4.html>) but
this
>> did not work, because PAE is not supported by this package.
>> Thanks for this hint!
>>
>> *More ideas? *
>>
>> Fabian
>>
>>
>> Steven Timm schrieb:
>>> Fabian--did you do a depmod on the kernel tree and do a mkinitrd
>>> on your machine after you compiled the kernel?  The error
>>> you are getting to me looks like you do not have the block
>>> devices loaded right in the initrd images you have and thus
>>> it can''t find the root directory to continue
>>> the linux boot, maybe it is not even loading the vmlinuz-2.6.18xen
>>> correctly.
>>>
>>> Or did you try to use the pre-built rpms or tarballs for RHEL/SL
that
>>> are on the www.xen.org site?  I have not tried the 3.1.0 version
>>> of those on SL4 but there are rpms there for SL4.  I did use the
>>> Xen 3.0.4 precompiled version for SL4 on SL4 and that works fine.
>>>
>>> Steve Timm
>>>
>>>
>>> On Fri, 28 Mar 2008, Fabian Lueghausen wrote:
>>>
>>>> Hello list,
>>>>
>>>> I tried to install Xen 3.1.0 on Scientific Linux (RHEL4), but
this
>>>> mission failed.. Hope you can help me by finding the reason for
my
>>>> problem.
>>>> I downloaded the xen sources from 
>>>>
http://bits.xensource.com/oss-xen/release/3.1.0/src.tgz/xen-3.1.0-src.tgz
>>>> and compiled them by running "make" and
"./install.sh". This seemed
>>>> to work.
>>>> After setting up grub like this,
>>>>
>>>>   # grub.conf generated by anaconda
>>>>   #
>>>>   # Note that you do not have to rerun grub after making
changes to
>>>>   this file
>>>>   # NOTICE:  You have a /boot partition.  This means that
>>>>   #          all kernel and initrd paths are relative to
/boot/, eg.
>>>>   #          root (hd0,0)
>>>>   #          kernel /vmlinuz-version ro root=/dev/hda3
console=tty0
>>>>   console=ttyS0,9600
>>>>   #          initrd /initrd-version.img
>>>>   boot=/dev/hda1
>>>>   default=0
>>>>   timeout=5
>>>>   splashimage=(hd0,0)/grub/splash.xpm.gz
>>>>   hiddenmenu
>>>>   #
>>>>   title Scientific Linux (2.6.9-11.EL)
>>>>    root (hd0,0)
>>>>    kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/ rhgb quiet
console=tty0
>>>>   console=ttyS0,9600
>>>>    initrd /initrd-2.6.9-11.EL.img
>>>>   *#
>>>>   title Xen 3.1 / XenLinux 2.6
>>>>    root (hd0,0)
>>>>    kernel /xen-3.1.0.gz dom0_mem=256000 noreboot
>>>>    module /vmlinuz-2.6.18-xen ro root=LABEL=/ rhgb quiet
console=tty0
>>>>   console=ttyS0,9600**
>>>>    module /initrd-2.6.18-xen.img
>>>>   *
>>>>
>>>> I shut down my machine and restarted it. But it won''t
come up... as
>>>> you can see right here:
>>>>
>>>>   (XEN) Command line: /xen-3.1.0.gz dom0_mem=256000 noreboot
>>>>
>>>>       (...)
>>>>
>>>>   System RAM: 511MB (523356KB)
>>>>   Xen heap: 10MB (10272KB)
>>>>   Domain heap initialised: DMA with 32 bits
>>>>   PAE enabled, limit: 16GB
>>>>   Processor #0 15:0 APIC version 20
>>>>   IOAPIC[0]: apic_id 1, version 32, adress 0xfec00000, GSI 0-23
>>>>   Enabling APIC mode: Flat, Using 1 I/O APICs
>>>>   Using scheduler: SMP Credit Scheduler (credit)
>>>>   Detected 1694.889MHz processor
>>>>   CPU0: Intel(R) Pentium(R) 4 CPU 1700MHz stepping 0a
>>>>   Mapping CPU0 to node 255
>>>>   Total of 1 processors activated.
>>>>   ENABLING IO-APIC IRQs
>>>>    -> Using new ACK method
>>>>   Platform timer is 1.193MHz PIT
>>>>   Brought up 1 CPUs
>>>>   *** LOADING DOMAIN 0 ***
>>>>    Xen kernel: 32-bit, PAE, lsb
>>>>    Guest kernel: 32-bit, PAE, lsb, paddr 0xc0100000 ->
0xc045f53c
>>>>   PHYSICAL MEMORY ARRANGEMENT:
>>>>    Dom0 alloc.: 000000001f000000 -> 000000001f800000 (61952
pages to
>>>>   be allocated)
>>>>   VIRTUAL MEMORY ARRANGEMENT:
>>>>    Loaded kernel: c....... -> c.......
>>>>    Init. ramdisk: c....... -> c.......
>>>>    Phys-Mach mag: c....... -> c.......
>>>>    Start info:    c....... -> c.......
>>>>    Page tables:   c....... -> c.......
>>>>    Boot stack:    c....... -> c.......
>>>>    TOTAL:         c....... -> c.......
>>>>    ENTRY ADRESS:  c....... -> c.......
>>>>   Dom0 has maximum 1VCPUs
>>>>   Initrd len 0x112200, start at 0xc0460000
>>>>   Scrubbing Free RAM: .. done.
>>>>   Xen trace buffers: disabled
>>>>   Std Loglevel: Errors and warnings
>>>>   Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>>>>   *Kernel Panic - not syncing: Attempted to kill init!*
>>>>
>>>> Is there anyone who has an idea what I''m doing wrong?!
Tried it by
>>>> myself for a few hours, but I''m in the dark...
>>>>
>>>> Thanks for every reply to this email!
>>>>
>>>> Ciao,
>>>> Fabian
>>>>
>>>>
>>>
>>
>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users