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

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

  • To: xen-devel@xxxxxxxxxxxxx
  • From: José Eduardo França <jefranca@xxxxxxxxx>
  • Date: Sun, 22 Apr 2012 16:21:10 -0300
  • Delivery-date: Sun, 22 Apr 2012 19:21:52 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

hi guys,

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 <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.

Please, help me

PS: I'm sorry to my English, coz I'm brazilian.

My setups are:

- fdisk

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          32      248832   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              32       30395   243889153    5  Extended
/dev/sda5              32       30395   243889152   8e  Linux LVM

- blkid

root@debian-02:/home/franca# blkid
/dev/sda5: UUID="RVwX4M-56HI-Tu9q-CLkP-V0jx-Ft7W-b0bPHP" TYPE="LVM2_member"
/dev/sda1: UUID="fcc01979-0cf3-4dbe-863a-ab32d2636fec" TYPE="ext3"
/dev/mapper/debian--02-root: UUID="da8b402b-b224-4552-80df-754339518e4d" TYPE="ext3"
/dev/mapper/debian--02-swap_1: UUID="d5eb1ff7-b7d8-4b60-95e3-f4bb5ae32932" TYPE="swap"

My scripts are:

- 08_xen

exec tail -n +3 $0
menuentry "Xen Unstable / Debian Squeeze kernel" {
    insmod ext2
        set root='(hd0,msdos1)'
        multiboot (hd0,msdos1)/boot/xen-4.2-unstable.gz dummy dom0_mem=512M
        module (hd0,msdos1)/boot/vmlinuz- dummy root=UUID=fcc01979-0cf3-4dbe-863a-ab32d2636fec ro quiet console=tty0 nomodeset
        module (hd0,msdos1)/boot/initrd.img-

### 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- dummy root=UUID=8e339522-dab5-4a81-8066-c41cc3908a15 ro quiet console=tty0 nomodeset
        #module (hd0,1)/boot/initrd.img-

    #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- root=/dev/sda1
        #module /boot/initrd.img-

- modules

# /etc/modules: kernel modules to load at boot time.
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.


- fstab

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/mapper/debian--02-root /               ext3    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=fcc01979-0cf3-4dbe-863a-ab32d2636fec /boot           ext3    defaults        0       2
/dev/mapper/debian--02-swap_1 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
none /proc/xen xenfs defaults 0 0
Xen-devel mailing list



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