[one-users] Problem boot VM template with opennebula

[Javier Fontan]

The problem is the root parameter:

--8<------
dracut Warning: No root device "block:/dev//dev/xvda1" found
------>8--

In OpenNebula template you should drop de "/dev/" prefix and "ro" parameter:

--8<------
OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
"/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ]
------>8--

In case you want to add the "ro" parameter or any other one you should
use KERNEL_CMD parameter [1].

Cheers

[1] http://docs.opennebula.org/4.4/user/references/template.html#os-and-boot-options-section

On Wed, Mar 19, 2014 at 5:40 PM, Cuquerella Sanchez, Javier
<javier.cuquerella at atos.net> wrote:
> Hi,
>
> I have a problem when starting a virtual machine. me the error that appears is:
>
> Freeing unused kernel memory: 1260k freed
> Write protecting the kernel read-only data: 10240k
> Freeing unused kernel memory: 972k freed
> Freeing unused kernel memory: 1732k freed
> dracut: dracut-004-283.el6
> device-mapper: uevent: version 1.0.3
> device-mapper: ioctl: 4.22.6-ioctl (2011-10-19) initialised: dm-devel at redhat.com
> udev: starting version 147
> dracut: Starting plymouth daemon
> xlblk_init: register_blkdev major: 202
> blkfront: xvda1: barriers disabled
> XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...
> dracut Warning: No root device "block:/dev//dev/xvda1" found
> dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
> dracut Warning: Signal caught!
> dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Not tainted 2.6.32-279.el6.x86_64 #1
> Call Trace:
>  [<ffffffff814fd11a>] ? panic+0xa0/0x168
>  [<ffffffff81070bd2>] ? do_exit+0x862/0x870
>  [<ffffffff8117ca75>] ? fput+0x25/0x30
>  [<ffffffff81070c38>] ? do_group_exit+0x58/0xd0
>  [<ffffffff81070cc7>] ? sys_exit_group+0x17/0x20
>  [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b
>
>
> The template is:
>
> NAME   = Encourage5
> MEMORY = 4096
> CPU    = 1
> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD = "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "/dev/xvda1 ro" ]
> DISK =[ DRIVER="file:", IMAGE_ID="27", TARGET="xvda1" ]
> DISK =[ TYPE  = "swap", SIZE = 1024, TARGET = "sdb"  ]
> NIC = [ NETWORK_ID = 3 ]
> GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0, PORT=5901, TYPE=vnc ]
> RAW=[ DATA="device_model='/usr/lib64/xen/bin/qemu-dm'", TYPE=xen ]
>
>
> used as a virtual disk image. img, created with dd. If I lift the image with xen: xm create encourage.cfg machine working properly. the configuration file for xen is:
>
> cat ../encourage/encourage.cfg
> name = "encourage"
>
> memory = 4096
> maxmem = 4096
> vcpus = 1
>
> #bootloader = "/usr/bin/pygrub"
> #bootloader = "/usr/lib64/xen/bin/pygrub"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
>
> disk = ['file:/home/jcuque/encourage/encourage2.img,xvda1,w','file:/home/jcuque/encourage/encourage2.swap,xvda2,w']
> vif = ['bridge=br0']
> kernel = "/boot/vmlinuz-2.6.32-279.el6.x86_64"
> ramdisk = "/boot/initramfs-2.6.32-279.el6.x86_64.img"
> root = "/dev/xvda1 ro"
>
>
> Can you help me? Tell me if you need more date
>
> Thanks
> regards
>
> ---------------------------------------------------
> Javier Cuquerella Sánchez
>
> Javier.cuquerella at atos.net
> Atos Research & Innovation
> Systems Administrator
> Albarracin 25
> 28037-Madrid (SPAIN)
> Tfno: +34.91.214.8080
> www.atosresearch.eu
> es.atos.net
>



-- 
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan