[one-users] Xen Paravirtualized error - cfg and template
Javier Fontan
jfontan at opennebula.org
Thu Oct 17 10:14:03 PDT 2013
This should add that to your VM. Add any other parameter needed.
OS=[
ROOT='xvda1 ro'
]
On Thu, Sep 12, 2013 at 5:35 AM, <kenny.kenny at bol.com.br> wrote:
> i solved this problem, i just put sda1 in the target parameter.
>
>
> Do you know what i need to do to pass this parameter root = '/dev/xvda1 ro'
> by opennebula ?
>
> ________________________________
>
> De: kenny.kenny at bol.com.br
> Enviada: Segunda-feira, 9 de Setembro de 2013 14:06
> Para: Ruben S. Montero < rsmontero at opennebula.org >
> Assunto: Re: [one-users] Xen Paravirtualized error - cfg and template
>
> Thanks Ruben.
>
>
> Do you know what i need to do in the template file to have sda1 and sda2
> (like my xen.cfg) in the deployment.0 ?
>
>
> ________________________________
> Em 09/09/2013 13:22, Ruben S. Montero < rsmontero at opennebula.org > escreveu:
> That's the context device, either add a target for it (as part of CONTEXT
> definition) or remove the context section
> http://opennebula.org/documentation:rel4.2:template#context_section
>
> CONTEXT=[NETWORK="YES",SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]"]
>
> Cheers
>
>
> On Mon, Sep 9, 2013 at 6:19 PM, <kenny.kenny at bol.com.br> wrote:
>>
>> Thanks for the reply.
>>
>> I take a look at the deployment.0 and i see that:
>> name = 'one-45'
>> #O CPU_CREDITS = 256
>> memory = '256'
>> vcpus = '1'
>> bootloader = "/usr/lib/xen/bin/pygrub"
>> disk = [
>> 'file:/var/lib/one//datastores/0/45/disk.0,sda,w',
>> 'file:/var/lib/one//datastores/0/45/disk.1,sdb,w',
>> 'tap:aio:/var/lib/one//datastores/0/45/disk.2,hda,r',
>> ]
>> vif = [
>> ' mac=02:00:0a:00:03:6a,ip=10.0.3.106,bridge=virbr0',
>> ]
>> vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=45,vncpasswd=123456']
>>
>> I did´nt configure the disk in bold. Whyy opennebula created this?
>>
>> My template:
>>
>> CLUSTER_100="100"
>> CONTEXT=[NETWORK="YES",SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]"]
>> CPU="1"
>> DISK=[DEV_PREFIX="sd",DRIVER="file:",IMAGE_ID="7",READONLY="no"]
>> DISK=[DEV_PREFIX="sd",DRIVER="file:",READONLY="no",SIZE="256",TYPE="swap"]
>> GRAPHICS=[LISTEN="0.0.0.0",PASSWD="123456",TYPE="VNC"]
>> MEMORY="256"
>> NIC=[NETWORK_ID="1"]
>> OS=[BOOTLOADER="/usr/lib/xen/bin/pygrub",ROOT="sda"]
>> REQUIREMENTS="CLUSTER_ID=\"100\""
>> VCPU="1"
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
>> ________________________________
>> Em 09/09/2013 05:25, Ruben S. Montero < rsmontero at opennebula.org >
>> escreveu:
>> Hi
>>
>> Take a look at a file named "deployment.0", it is the .cfg file generated
>> by OpenNebula. Compare this file with your working cfg file, probably you
>> are not using the right bus/mapping. OpenNebula uses a disk approach to
>> automatically set targets (sda, sdb,...) while your template uses a
>> partition based layout (sda1, sda2...). So probably you'll need to set
>> TARGET attribute in the Image template or in the VM template in the DISK
>> attribute.
>>
>> Cheers
>>
>> Ruben
>>
>>
>> On Sun, Sep 8, 2013 at 9:33 PM, <kenny.kenny at bol.com.br> wrote:
>>>
>>> Hello,
>>> I have a xen 4.2 , running ok on a ubuntu 12.10 machine.
>>>
>>> When i create the virtual machine by xm create ubuntu.cfg , it is ok.
>>> But when i create the virtual machine, with the same image disk by
>>> opennebula (4.2) i get this error in domU ( i see the error by xm console
>>> in xen host):
>>>
>>> 1.274565] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised:
>>> dm-devel at redhat.com
>>> [ 1.274590] EFI Variables Facility v0.08 2004-May-17
>>> [ 1.274975] TCP cubic registered
>>> [ 1.275354] NET: Registered protocol family 10
>>> [ 1.276538] NET: Registered protocol family 17
>>> [ 1.276557] Registering the dns_resolver key type
>>> [ 1.276762] registered taskstats version 1
>>> [ 6.388086] XENBUS: Waiting for devices to initialise:
>>> 25s...20s...15s...10s...5s...0s...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...
>>> Gave up waiting for root device. Common problems:
>>> - Boot args (cat /proc/ cmdline)
>>> - Check rootdelay= (did the system wait long enough?)
>>> - Check root= (did the system wait for the right device?)
>>> - Missing modules (cat /proc/modules; ls /dev)
>>> ALERT! /dev/xvda2 does not exist. Dropping to a shell!
>>>
>>> my ubuntu.cfg :
>>> #kernel = "/vmlinuz"
>>> #ramdisk = "/initrd.gz"
>>> bootloader ='/usr/lib/xen/bin/pygrub'
>>> name = "ubuntu3"
>>> memory = '512'
>>> dhcp = 'dhcp'
>>> vif = ['mac=00:00:00:8F:D9:46']
>>>
>>> disk = [
>>> 'file:/vms/images/ubuntu3/disk.img,sda2,w',
>>> 'file:/vms/images/ubuntu3/swap.img,sda1,w',
>>> ]
>>> on_poweroff = 'destroy'
>>> on_reboot = 'restart'
>>> on_crash = 'restart'
>>>
>>> Anybody knows what is the problem ?
>>> How can i "convert" a xen .cfg to a opennebula template ?
>>>
>>> Thanks.
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>>
>>
>> --
>> --
>> Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013
>> --
>> Ruben S. Montero, PhD
>> Project co-Lead and Chief Architect
>> OpenNebula - The Open Source Solution for Data Center Virtualization
>> www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
>>
>
>
>
>
> --
> --
> Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013
> --
> Ruben S. Montero, PhD
> Project co-Lead and Chief Architect
> OpenNebula - The Open Source Solution for Data Center Virtualization
> www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
--
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan
More information about the Users
mailing list