[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] [Xen-devel] Xen doesn't boot on grub2 or xend doesn't start



Walter,

thank you to reply.
I tried You suggested, but it didn't work. More some idea?

Pasi,

I have posted in xen-devel coz in "Xen Users Netiquette <http://wiki.xen.org/wiki/XenUsersNetiquette>" advise to report problems about unstable/testing xen versions there. But, it's OK, I just wanna resolve my problem. :)

Let's go... I really tried to fix the grub but I couldn't.

my grub.cfg is after this mail

Thanks, Eduardo


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="3"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod lvm
insmod part_msdos
insmod ext2
set root='(debian-02-root)'
search --no-floppy --fs-uuid --set da8b402b-b224-4552-80df-754339518e4d
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set fcc01979-0cf3-4dbe-863a-ab32d2636fec
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=15
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod part_msdos
insmod ext2
set root='(debian-02-root)'
search --no-floppy --fs-uuid --set da8b402b-b224-4552-80df-754339518e4d
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
  set color_normal=light-gray/black
  set color_highlight=white/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/08_xen ###
menuentry "Xen Unstable / Debian Squeeze kernel 2.6.32.40" {
### MY ATTEMPT
    insmod ext2
    set root='(hd0,msdos1)'
    multiboot (hd0,msdos1)/boot/xen-4.2-unstable.gz dummy dom0_mem=512M
    module (hd0,msdos1)/boot/vmlinuz-2.6.32.40 dummy root=UUID=fcc01979-0cf3-4dbe-863a-ab32d2636fec ro quiet console=tty0 nomodeset
    module (hd0,msdos1)/boot/initrd.img-2.6.32.40

### MODEL Configuring and Installing Remus
    #insmod ext2
    #set root='(hd0,1)'
    #multiboot (hd0,1)/boot/xen-4.2-unstable.gz dummy dom0_mem=512M
    #module (hd0,1)/boot/vmlinuz-2.6.32.40 dummy root=UUID=8e339522-dab5-4a81-8066-c41cc3908a15 ro quiet console=tty0 nomodeset
    #module (hd0,1)/boot/initrd.img-2.6.32.40
 
### MODEL UBUNTU FORUM
    ##insmod multiboot
    #insmod part_msdos
    #insmod ext2
    #set root=(hd0,msdos1)
    #search --no-floppy --fs-uuid --set fcc01979-0cf3-4dbe-863a-ab32d2636fec
    #multiboot /boot/xen-4.2-unstable.gz
    #module /boot/vmlinuz-2.6.32.40 root=/dev/sda1
    #module /boot/initrd.img-2.6.32.40
}
### END /etc/grub.d/08_xen ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32.40' --class debian --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set fcc01979-0cf3-4dbe-863a-ab32d2636fec
    echo    'Loading Linux 2.6.32.40 ...'
    linux    /vmlinuz-2.6.32.40 root=/dev/mapper/debian--02-root ro  quiet
    echo    'Loading initial ramdisk ...'
    initrd    /initrd.img-2.6.32.40
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686' --class debian --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set fcc01979-0cf3-4dbe-863a-ab32d2636fec
    echo    'Loading Linux 2.6.32-5-xen-686 ...'
    linux    /vmlinuz-2.6.32-5-xen-686 root=/dev/mapper/debian--02-root ro  quiet
    echo    'Loading initial ramdisk ...'
    initrd    /initrd.img-2.6.32-5-xen-686
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class gnu-linux --class gnu --class os {
    insmod part_msdos
    insmod ext2
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set fcc01979-0cf3-4dbe-863a-ab32d2636fec
    echo    'Loading Linux 2.6.32-5-686 ...'
    linux    /vmlinuz-2.6.32-5-686 root=/dev/mapper/debian--02-root ro  quiet
    echo    'Loading initial ramdisk ...'
    initrd    /initrd.img-2.6.32-5-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Em 24 de abril de 2012 10:13, Walter Robert Ditzler <ditwal001@xxxxxxxxx> escreveu:
hi,

for boot order, if manually set:
***
update-rc.d xencommons defaults 19 18
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
update-rc.d xen-watchdog defaults 22 23
***

and dont forget in /etc/default/grub
***
# SET THE DEFAULT BOOT KERNEL, NUMBER COUNTED FROM THE TOP BEGINNING WITH 0
GRUB_DEFAULT=10
# SOMETIMES IS NICE TO HAVE FIX MEMORY ALLOCATION TO AVOID CRASHING IF ALL
MEMORY IS USED
GRUB_CMDLINE_XEN="dom0_mem=1024M"
***

thanks walter

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Pasi Kärkkäinen
Sent: Dienstag, 24. April 2012 15:00
To: José Eduardo França
Cc: xen-users@xxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-users] [Xen-devel] Xen doesn't boot on grub2 or xend
doesn't start

On Tue, Apr 24, 2012 at 09:54:26AM -0300, José Eduardo França wrote:
>    Pasi,
>

This thread really belongs to xen-users mailinglist (added to CC).
So let's drop xen-devel from the CC list in the replies..


>    I didn't really understand when You said "I was talking about dom0
Linux
>    kernel, not about Xen", coz I understand you must be in xen to access
>    dom0.
>    Look: in my grub2 I have these options in grub2:
>
>    Xen Unstable / Debian Squeeze kernel 2.6.32.40
>    Debian GNU/Linux, with Linux 2.6.32.40
>    Debian GNU/Linux, with Linux 2.6.32-5-686
>

Please paste the entries from your grub.cfg

>    I select first option and the system returns:
>
>    error: couldn't open file
>    error: you need to load the multiboot kernel first
>

So the grub entry is broken. Please fix it.

>    The second option is in graphical environment but keyboard and mouse
don't
>    work there. I thought You said to enter within this option (but I think
>    this option is not important)
>

Of course you need to boot to Xen to be able to use Xen.
I recommend using just the text-only modes.

>    And the third option is my environment where I compiled and installed
xen
>    and Debian GNU/Linux, with Linux 2.6.32.40.
>    Here I do command "# /etc/init.d/xend start" and the system returns
>    "xencommons should be started first", but I had done
>    "/etc/init.d/xencommons start" before and no error message returned
!!!???
>

Did you realize Xen is the hypervisor (xen.gz), and in addition to Xen you
also need Xen-enabled Linux dom0 kernel ?

http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F


>    and then... what do you think?
>


-- Pasi


>    Eduardo
>
>    Em 23 de abril de 2012 13:45, José Eduardo França
<[1]jefranca@xxxxxxxxx>
>    escreveu:
>
>      Pasi
>
>      I didn't think this. I'll be in my job tomorrow an I'll reply there.
>
>      Thank you
>
>      Em 23 de abril de 2012 13:23, Pasi Kärkkäinen <[2]pasik@xxxxxx>
>      escreveu:
>
>        On Mon, Apr 23, 2012 at 01:13:49PM -0300, José Eduardo França
wrote:
>        >    Hi Pasi,
>        >
>        >    thank you for reply.
>        >
>        >    I'm using Debian Squeeze, and I'm compiling Xen from source
>        (.tar.gz). I
>        >    ran "make install-tools PYTHON_PREFIX_ARG=" to install Xen.
>        >
>        >    Notice: I couldn't run in xen_unstable or dom0 then I returned
to
>        install
>        >    environment (Debian Squeeze)
>        >
>        >    My attempt with modules and now with xenstored command
>        (oxenstored command
>        >    works) was in Debian Squeeze. In this case I think I can't
load
>        these
>        >    modules or run this command, but I'm not sure. Then your
>        questions can not
>        >    be in this scope. What do you think?
>        >
>
>        I was talking about dom0 Linux kernel, not about Xen.
>
>        -- Pasi
>
>        >    Thanks, Eduardo
>        >
>        >    Em 23 de abril de 2012 03:36, Pasi Kärkkäinen
>        <[1][3]pasik@xxxxxx> escreveu:
>        >
>        >      On Sun, Apr 22, 2012 at 04:21:10PM -0300, José Eduardo
França
>        wrote:
>        >      >    hi guys,
>        >      >
>        >
>        >      Hello,
>        >      >    It's my first time here and in a mailing lists, I only
>        participated
>        >      in
>        >      >    forums before. Please, If I make a mistake you should
>        advise me.
>        >      Let's go!
>        >      >
>        >      >    I was reading "xencommons not start" in a Remus Forum
in
>        order to
>        >      install
>        >      >    Remus.
>        >      >    Well* I followed the tutorial
>        >      >
>        >
>
<[1][2][4]http://remusha.wikidot.com/configuring-and-installing-remus>,
>        I
>        >      reboot
>        >      >    in xen_unstable and I had a error message:
>        >      >
>        >      >    error: couldn't open file
>        >      >    error: you need to load the multiboot kernel first
>        >      >
>        >      >    then I redid tutorial after "Adapt Grub" and in a
moment I
>        do
>        >      command:
>        >      >
>        >      >    # /etc/init.d/xend start
>        >      >    xencommons should be started first.
>        >      >
>        >      >    but I had done "/etc/init.d/xencommons start" before
and
>        no error
>        >      message
>        >      >    returned !!!???
>        >      >
>        >      >    I also tried insert modules manually (coz in other
mailing
>        list
>        >      said to
>        >      >    put some modules - see my setups after this mail) but I
>        had:
>        >      >
>        >      >    # modprobe xen-evtchn
>        >      >    FATAL: Module xen_evtchn not found.
>        >      >
>        >
>        >      So xen event channel support is not compiled as a module?
>        >      is it enabled at all in your dom0 kernel config?
>        >
>        >
>
[3][5]http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F
>        >      -- Pasi
>        >
>        > References
>        >
>        >    Visible links
>        >    1. mailto:[6]pasik@xxxxxx
>        >    2.
[7]http://remusha.wikidot.com/configuring-and-installing-remus
>        >    3.
>
> [8]http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F
>
> References
>
>    Visible links
>    1. mailto:jefranca@xxxxxxxxx
>    2. mailto:pasik@xxxxxx
>    3. mailto:pasik@xxxxxx
>    4. http://remusha.wikidot.com/configuring-and-installing-remus
>    5. http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F
>    6. mailto:pasik@xxxxxx
>    7. http://remusha.wikidot.com/configuring-and-installing-remus
>    8.
> http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.