2012년 5월 4일 금요일

When starting Ubuntu domU on xen, an error raised: Boot loader didn't return any data


A few days ago, I upgraded a server's OS and hypervisor. I had a Ubuntu 12.04 VM (PVM) on the old system and I migrated the VM to new system, of course, this was running well on old system.

                         [old]                         [new]
OS:               CentOS 5.6       =>      CentOS 6.2 
Hypervisor:     Xen 3.0.3         =>      Xen 4.0.1

But, It raised an error when I started the VM on new one.     
Error: Boot loader didn't return any data!

/var/log/xen/xend.log was: 
[2012-04-27 18:13:32 6622] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: domid=24
[2012-04-27 18:13:32 6622] DEBUG (XendDomainInfo:2416) No device model
[2012-04-27 18:13:32 6622] DEBUG (XendDomainInfo:2418) Releasing devices
[2012-04-27 18:13:32 6622] ERROR (XendDomainInfo:106) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 104, in create vm.start()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 469, in start XendTask.log_progress(31, 60, self._initDomain)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line 209, in log_progress retval = func(*args, **kwds)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2820, in _initDomain self._configureBootloader()
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 3266, in _configureBootloaderbootloader_args, kernel, ramdisk, args)
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendBootloader.py", line 215, in bootloader raise VmError, msg VmError: Boot loader didn't return any data!



I was googling and the search result recommended that firstly, excute the command "/usr/bin/pygrub with the VM image and secondly, boot as the py-grub.    


Run pygrub command to check whether the vm image boot normally 
$ /usr/bin/pygrub ./vm01.img

Using to parse /boot/grub/grub.cfg
WARNING:root:Unknown directive load_video
WARNING:root:Unknown directive terminal_output
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive else
WARNING:root:Unknown directive export
WARNING:root:Unknown image directive recordfail
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 713, in
    chosencfg = run_grub(file, entry, fs, incfg["args"])
  File "/usr/bin/pygrub", line 548, in run_grub
    g = Grub(file, fs)
  File "/usr/bin/pygrub", line 204, in __init__
    self.read_config(file, fs)
  File "/usr/bin/pygrub", line 412, in read_config
    self.cf.parse(buf)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 400, in parse
    self.add_image(Grub2Image(title, img))
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 316, in __init__
    _GrubImage.__init__(self, title, lines)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 85, in __init__
    self.reset(lines)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 101, in reset
    self._parse(lines)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 96, in _parse
    map(self.set_from_line, lines)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 326, in set_from_line
    setattr(self, self.commands[com], arg.strip())
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 104, in set_root
    self._root = GrubDiskPart(val)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 55, in __init__
    (self.disk, self.part) = str.split(",", 2)
  File "/usr/lib64/python2.6/site-packages/grub/GrubConf.py", line 80, in set_part
    self._part = int(val)
ValueError: invalid literal for int() with base 10: 'msdos1'


I found something was wrong related to keyword "msdos1", the next step is check the grub.cfg file.



Boot the VM using pv-grub to check which is wrong in the grub.cfg
# Modify config file to boot using pv-grub
$ vi ./vm01.cfg


# Comment out default bootloader
# bootloader="/usr/bin/pygrub"



# Add Pvgrub lines (Ubuntu uses grub.cfg)
kernel="/usr/lib/xen/boot/pv-grub-x86_64.gz"
extra="(hd0,0)/grub/grub.cfg"




$ xm create vm01.cfg -c
    GNU GRUB  version 0.97  (1048576K lower / 0K upper memory)
       [ Minimal BASH-like line editing is supported.   For
         the   first   word,  TAB  lists  possible  command
         completions.  Anywhere else TAB lists the possible
         completions of a device/filename. ]
grubdom> cat (hd0,0)/grub/grub.cfg
......
set root='(hd0,msdos1)'
......
......


CentOS didn't recognize the keyword "msdos1" which used in the Ubuntu. ( I also created a Ubuntu 12.04 VM on Ubuntu dom0, it was booted successfully) Looking at the /boot/grub/menu.list in CentOS, it defined as "root (hd0,0)"  
I changed the value of the property "root", before change, I needed to mount the VM image.



Mount VM image and change values
$ fdisk -ul ./vm01.img

You must set cylinders.
You can do this from the extra functions menu.

Disk ./vm01.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders, total 0 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b0b36

      Device          Boot      Start         End             Blocks     Id  System
./vm01.img1        *        2048      499711          248832   83  Linux
Partition 1 does not end on cylinder boundary.
./vm01.img2                501758   104855551    52176897    5  Extended
Partition 2 has different physical/logical endings: phys=(1023, 254, 63) logical=(6526, 243, 53)
./vm02.img5               501760   104855551    52176896   8e  Linux LVM

# offset: 2048 * 512 = 1048576 
$ losetup -o 1048576 /dev/loop1 ./vm01.img
$ mkdir /mnt/tmp
$ mount /dev/loop1 /mnt/tmp/
$ ls /mnt/tmp
abi-3.2.0-24-generic     initrd.img-3.2.0-24-generic  memtest86+_multiboot.bin
config-3.2.0-24-generic  lost+found                   System.map-3.2.0-24-generic
grub                     memtest86+.bin               vmlinuz-3.2.0-24-generic
$ cp /mnt/tmp/grub/grub.cfg /mnt/tmp/grub/grub.cfg.orig
$ vi /mnt/tmp/grub/grub.cfg
Replace set root='(hd0,msdos1)'   with  set root='(hd0,0)'



Once update the values, needs to umount.
$ umount /mnt/tmp
$ losetup -d /dev/loop1


Try creating the VM again and the booting was fine.
$ xm create vm01.cfg
$ xm list 

Name                          ID  Mem   VCPUs      State   
Domain-0                     0   2987     6          r-----     
vm01                          93  1024     1          r-----     

............

References: 
2. Mount KVM/Xen virtual disk image outside guest OS: http://blog.leenix.co.uk/2010/07/howto-mount-kvmxen-virtual-disk-image.html
3. PVGrub Howto: http://wiki.xen.org/wiki/PVGrub_HowTo


댓글 13개:

  1. OS: Ubuntu 12.04
    Hypervisor: Xen 4.1.0

    when i am trying to Launch Instance am getting libvirt error.


    /var/log/xen/xend.log :

    [2012-05-07 19:20:32 12338] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=11
    [2012-05-07 19:20:32 12338] DEBUG (XendDomainInfo:2406) No device model
    [2012-05-07 19:20:32 12338] DEBUG (XendDomainInfo:2408) Releasing devices
    [2012-05-07 19:20:32 12338] ERROR (SrvBase:88) Request start failed.
    Traceback (most recent call last):
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/web/SrvBase.py", line 85, in perform
    return op_method(op, req)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/server/SrvDomain.py", line 77, in op_start
    return self.xd.domain_start(self.dom.getName(), paused)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomain.py", line 1070, in domain_start
    dominfo.start(is_managed = True)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain
    self._configureBootloader()
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader
    raise VmError, msg
    VmError: Boot loader didn't return any data!

    답글삭제
  2. /var/log/xen/xend.log :

    [2012-05-07 18:09:45 10868] DEBUG (XendDomain:1036) Creating new managed domain: instance-00000007
    [2012-05-07 18:09:45 10868] DEBUG (SrvDomain:76) Starting domain instance-00000007 False
    [2012-05-07 18:09:45 10868] DEBUG (XendDomainInfo:2498) XendDomainInfo.constructDomain
    [2012-05-07 18:09:45 10868] DEBUG (balloon:187) Balloon: 918544 KiB free; need 16384; done.
    [2012-05-07 18:09:45 10868] DEBUG (XendDomain:476) Adding Domain: 2
    [2012-05-07 18:09:45 10868] DEBUG (XendDomainInfo:2836) XendDomainInfo.initDomain: 2 256
    [2012-05-07 18:09:45 11543] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/lib/xen-4.1/bin/pygrub', '--args=root=/dev/xvda ', '--output=/var/run/xend/boot/xenbl.8011', '/var/lib/nova/instances/instance-00000007/disk'].
    [2012-05-07 18:09:45 10868] ERROR (XendBootloader:214) Boot loader didn't return any data!
    [2012-05-07 18:09:45 10868] ERROR (XendDomainInfo:488) VM start failed
    Traceback (most recent call last):
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain
    self._configureBootloader()
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader
    raise VmError, msg
    VmError: Boot loader didn't return any data!

    답글삭제
  3. Hi, Netra.
    I think this can cause on various reasons. So its answer is not one. I need more information.

    Can I ask more questions about this?
    - What king of OS is installed for physical host? Is it Ubuntu 12.04?
    - When did you get the above error? You installed OS of the VM successfully and then you got a problem when reboot?
    - It is case of migrating VM to newer Xen?

    Best regards,
    Yeonki

    답글삭제
  4. This 12.04 fresh install.
    OS installed fine. When i use the image and do a Launch instance it fails giving bootloader erro on xend log.
    This is a new install and no migration.

    Details of logs below.

    We followed the procedure as is in this link to nova/glance up
    http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin

    Instead of kvm we have xen installed using nova-compute and nova-compute-xen and did
    sudo apt-get install xen-hypervisor-4.1-amd64 xen-utils-4.1 xenwatch xen-tools xen-utils-common xenstore-utils

    root@ubuntu:/home/vutp# virsh version
    Compiled against library: libvir 0.9.8
    Using library: libvir 0.9.8
    Using API: Xen 0.9.8
    Running hypervisor: Xen 4.1.0

    root@ubuntu:/home/vutp# xm info
    host : ubuntu
    release : 3.2.0-23-generic
    version : #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
    machine : x86_64
    nr_cpus : 2
    nr_nodes : 1
    cores_per_socket : 2
    threads_per_core : 1
    cpu_mhz : 2194
    hw_caps : 178bf3ff:ebd3fbff:00000000:00000010:00002001:00000000:0000011f:00000000
    virt_caps : hvm
    total_memory : 5887
    free_memory : 897
    free_cpus : 0
    xen_major : 4
    xen_minor : 1
    xen_extra : .2
    xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
    xen_scheduler : credit
    xen_pagesize : 4096
    platform_params : virt_start=0xffff800000000000
    xen_changeset : unavailable
    xen_commandline : placeholder
    cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu2)
    cc_compile_by : stefan.bader
    cc_compile_domain : canonical.com
    cc_compile_date : Thu Mar 8 14:31:11 UTC 2012
    xend_config_format : 4
    root@ubuntu:/home/vutp#


    root@ubuntu:/home/vutp# ps -ef|grep xen
    root 17 2 0 May07 ? 00:00:00 [xenwatch]
    root 18 2 0 May07 ? 00:00:00 [xenbus]
    root 1833 1 0 May07 ? 00:00:01 /usr/lib/xen-4.1/bin/xenstored --pid-file=/var/run/xenstore.pid
    root 1838 1 0 May07 ? 00:00:00 /usr/lib/xen-4.1/bin/xenconsoled --pid-file=/var/run/xenconsoled.pid
    root 12337 1 0 May07 ? 00:00:00 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend start
    root 12338 12337 0 May07 ? 00:00:27 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend start
    root 21760 21672 0 09:58 pts/0 00:00:00 grep --color=auto xen

    답글삭제
  5. When you created an VM, did you use *.cfg file and then execute the command like:
    $ xm create vm01.cfg -c

    If you did this, can you check whether the following exists in your vm's configuration file:
    bootloader="/usr/bin/pygrub"

    답글삭제
  6. Hi Yeonki,

    I am having the same problem with a fresh install, I am not sure exactly what is the problem but here I am putting my complete installation process. Maybe you can point us in the right direction.

    @server02:/var/lib/xen/images/ubuntu-netboot$ uname -a
    Linux server02 3.2.0-33-generic #52-Ubuntu SMP Thu Oct 18 16:29:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

    server02:/etc/network$ sudo fdisk -l

    Disk /dev/sda: 73.4 GB, 73407820800 bytes
    255 heads, 63 sectors/track, 8924 cylinders, total 143374650 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x000e93e4

    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 1953791 975872 83 Linux
    /dev/sda2 60549118 143374335 41412609 5 Extended
    /dev/sda3 1953792 60547071 29296640 83 Linux
    /dev/sda5 126599168 143374335 8387584 82 Linux swap / Solaris
    /dev/sda6 60549120 126599167 33025024 8e Linux LVM

    Partition table entries are not in disk order

    Disk /dev/sdb: 73.4 GB, 73407820800 bytes
    255 heads, 63 sectors/track, 8924 cylinders, total 143374650 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00061542

    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 143374335 71686144 8e Linux LVM


    @server02:/etc/network$ sudo pvdisplay
    --- Physical volume ---
    PV Name /dev/sda6
    VG Name VolGroup00
    PV Size 31.50 GiB / not usable 3.00 MiB
    Allocatable yes
    PE Size 4.00 MiB
    Total PE 8062
    Free PE 8062
    Allocated PE 0
    PV UUID KSHrVG-OEkR-Y8eT-Rcsj-sxSJ-WiDQ-Orp9v9

    --- Physical volume ---
    PV Name /dev/sdb1
    VG Name VolGroup00
    PV Size 68.37 GiB / not usable 2.00 MiB
    Allocatable yes
    PE Size 4.00 MiB
    Total PE 17501
    Free PE 17501
    Allocated PE 0
    PV UUID wYhGAU-QT0k-oxS0-yBGx-JVnd-8NXk-GpX7xw

    server02:/etc/network$ sudo vgdisplay VolGroup00
    --- Volume group ---
    VG Name VolGroup00
    System ID
    Format lvm2
    Metadata Areas 2
    Metadata Sequence No 1
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 0
    Open LV 0
    Max PV 0
    Cur PV 2
    Act PV 2
    VG Size 99.86 GiB
    PE Size 4.00 MiB
    Total PE 25563
    Alloc PE / Size 0 / 0
    Free PE / Size 25563 / 99.86 GiB
    VG UUID wtznZA-CuAW-eE6n-ZLcG-5Sn5-m2Gy-1NVENF

    @server02:~$ sudo xm list
    Name ID Mem VCPUs State Time(s)
    Domain-0 0 7455 2 r----- 244.4

    답글삭제
  7. configuration continue:

    @server02:/var/lib/xen/images/ubuntu-netboot$ ls
    initrd.gz vmlinuz

    Set up the initial guest configuration: /etc/xen/ubuntu.cfg

    me = "VM01"

    memory = 512

    disk = ['phy:/dev/VolGroup00/VM01,xvda,w']
    vif = [' ']

    kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
    ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
    extra = "debian-installer/exit/always_halt=true -- console=hvc0"


    Start the VM and connect to console (-c):

    @server02:/$sudo xm create /etc/xen/VM01.cfg -c

    In the installation process I choose to create Full LVM partition plus grub installation

    Install the Ubuntu as VM

    Set up the initial guest configuration and update it: /etc/xen/ubuntu.cfg

    me = "VM01"

    memory = 512

    disk = ['phy:/dev/VolGroup00/VM01,xvda,w']
    vif = [' ']
    bootloader = "/usr/bin/pygrub"
    kernel = "/var/lib/xen/images/ubuntu-netboot/vmlinuz"
    ramdisk = "/var/lib/xen/images/ubuntu-netboot/initrd.gz"
    extra = "debian-installer/exit/always_halt=true -- console=hvc0"

    @server02:/etc/xen$ sudo xm create /etc/xen/VM01.cfg -c
    Using config file "/etc/xen/VM01.cfg".
    Error: Boot loader didn't return any data!

    christian@server02:/etc/xen$ sudo fdisk -l /dev/VolGroup00/VM01

    Disk /dev/VolGroup00/VM01: 10.7 GB, 10737418240 bytes
    255 heads, 63 sectors/track, 1305 cylinders, total 20971520 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00033568

    Device Boot Start End Blocks Id System
    /dev/VolGroup00/VM01p1 2048 499711 248832 83 Linux
    /dev/VolGroup00/VM01p2 501758 20969471 10233857 5 Extended
    /dev/VolGroup00/VM01p5 501760 20969471 10233856 8e Linux LVM


    The important things are:
    - Sector size -> 512
    - Start of the partition slice -> 2048

    Now fire up an calculator and multiply these number to get the correct offset:
    512 * 2048 = 1048576

    With this value you can already mount the partition.

    christian@server02:/etc/xen$ sudo mount -o offset=1048576 /dev/VolGroup00/VM01 /xen

    - Open the grub.cfg file (/grub/grub.cfg) in your favorite editor.
    - Change msdos infos to a normal grub entry
    - replace hd0,msdos1 -> hd0,0

    Trying to create VM

    @server02:/var/log/xen$ sudo xm create /etc/xen/VM01.cfg
    Using config file "/etc/xen/VM01.cfg".
    Error: Boot loader didn't return any data!



    log

    [2012-11-28 11:28:28 1272] DEBUG (XendDomainInfo:3071) XendDomainInfo.destroy: domid=5
    [2012-11-28 11:28:28 1272] DEBUG (XendDomainInfo:2406) No device model
    [2012-11-28 11:28:28 1272] DEBUG (XendDomainInfo:2408) Releasing devices
    [2012-11-28 11:28:28 1272] ERROR (XendDomainInfo:108) Domain construction failed
    Traceback (most recent call last):
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 106, in create
    vm.start()
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 474, in start
    XendTask.log_progress(31, 60, self._initDomain)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendTask.py", line 209, in log_progress
    retval = func(*args, **kwds)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2838, in _initDomain
    self._configureBootloader()
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 3285, in _configureBootloader
    bootloader_args, kernel, ramdisk, args)
    File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendBootloader.py", line 215, in bootloader
    raise VmError, msg
    VmError: Boot loader didn't return any data!

    답글삭제
  8. Hi, Christian

    First, it looks normal in your DomO configuration.

    However, It doesn't seem to be solution that you did following:
    "Open the grub.cfg file (/grub/grub.cfg) in your favorite editor.
    Change msdos infos to a normal grub entry
    replace hd0,msdos1 -> hd0,0"
    Because your DomO's OS is Ubuntu. My case only should work when the OS of DomO is CentOs or RedHat.

    I'd like to know that you tried to create VM which had another OS (not ubuntu) in DomU?

    답글삭제
  9. Hi Yeonki,

    Thanks for your reply.

    My hardware doesnt support virtualization so I have to do PV. In that sense I can only install Ubuntu in DomU. I am only creating Ubuntu VMs in this Dom0 machine.

    I found out that I am not getting an error on msdos1 argument once booting but on WARNING:root:Unknown image directive recordfail, I think.

    @server02:/$ sudo /usr/bin/pygrub /dev/VolGroup00/VM01
    Using to parse /grub/grub.cfg
    WARNING:root:Unknown directive load_video
    WARNING:root:Unknown directive terminal_output
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive export
    WARNING:root:Unknown image directive recordfail
    WARNING:root:Unknown image directive gfxmode
    WARNING:root:Unknown image directive recordfail
    WARNING:root:Unknown image directive linux16
    WARNING:root:Unknown image directive linux16
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive else
    WARNING:root:Unknown directive source
    linux (kernel /var/run/xend/boot/boot_kernel.oWMMn4)(ramdisk /var/run/xend/boot/boot_ramdisk.OrM_CD)(args "root=/dev/mapper/nagios01-root ro console=hvc0 quiet splash $vt_handoff ")

    I will post if I find the solution.

    Txs,
    Ch

    답글삭제
  10. Hi, Christian.

    How about changing ubuntu.cfg file like this:
    # Comment out bootloader
    # bootloader="/usr/bin/pygrub"
    ....
    kernel="/usr/lib/xen/boot/pv-grub-x86_64.gz"
    extra="(hd0,0)/grub/grub.cfg"
    ....

    답글삭제
  11. Hi Yeonky,

    Thanks for your feedback. Indeed was a configuration problem on the .cfg file. If we use the bootloader statement it can not be run at the same time with the kernel and ramdisk statement, they are mutually exclusive. And I added the extra statement, can you please explain what that statement does?

    The VM is now running and I have network connectivity.

    답글삭제
  12. Hi I have one doubt, I want to run domu with my customized kernel.
    How Can I do that ?

    답글삭제
  13. You are able to set kernel by changing in configuration file of the VM.

    $ vi ./vm1.cfg
    ...
    kernel = "location of your customized kernel"
    ...

    Regards,
    Yeonki.

    답글삭제