[one-users] FW: Problem in deploying a VM

Wed Apr 22 09:18:38 PDT 2009

Hello,

You have to change the target of the first disk to "sda", the rest of  
the deployment file seems OK. It will be also nice to change fstab of  
that image so the swap is pointing to sdb.

Bye

On Apr 22, 2009, at 6:00 PM, Harishbabu Nagaraj wrote:

> Hi Javier,
>        Find the VM description file as below, Let us know if there  
> is any mistake in this.
>
> NAME   = vm-example
> CPU    = 0.5
> MEMORY = 128
> OS     = [
>  kernel   = "/boot/vmlinuz-2.6.27.7-9-xen",
>  initrd   = "/boot/initrd-2.6.27.7-9-xen",
>  root     = "sda1" ]
> DISK   = [
>  source   = "/opt/nebula/images/Rhel_server_singlepart.img",
>  target   = "sda1",
>  readonly = "no" ]
> DISK   = [
>  type     = "swap",
>  size     = 1024,
>  target   = "sdb"]
>
> NIC    = [ NETWORK = "Public VLAN" ]
>
> Thanks,
> Harish
>
> -----Original Message-----
> From: Javier Fontan [mailto:jfontan at fdi.ucm.es]
> Sent: Wednesday, April 22, 2009 8:54 PM
> To: Harishbabu Nagaraj
> Cc: Ruben S. Montero; users at opennebula.org; Sarath Kumar Bheemaraju
> Subject: Re: [one-users] FW: Problem in deploying a VM
>
>
> Hello,
>
> Can you send me the VM description file you are sending to ONE. I
> think that the device specification is wrong but I have to check it.
>
> Bye
>
> On Apr 22, 2009, at 1:55 PM, Harishbabu Nagaraj wrote:
>
>> Hi Javier/All,
>>       Since most of the people tried open nebula on OpenSuse 11.1,I
>> installed OpenSuse 11.1 and xen 3.3.1. I am trying to deploy the VM
>> on the same host machine.
>> My deployment file is as follows,
>> name = 'one-4'
>> #O CPU_CREDITS = 128
>> memory  = '512'
>> kernel = '/boot/vmlinuz-2.6.27.7-9-xen'
>> #kernel = "/usr/lib/xen/boot/hvmloader"
>> ramdisk = '/boot/initrd-2.6.27.7-9-xen'
>> root = '/dev/sda5'
>> disk = [
>>    'tap:aio:/opt/nebula/ONE/var//4/images/disk.1,sda5,w',
>>    'tap:aio:/opt/nebula/ONE/var//4/images/disk.0,sda1,w',
>> ]
>> vif = [
>>    'mac=50:20:20:20:20:20,bridge=br0',
>> ]
>> vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=5']
>>
>> My Host machine (OpenSuse 11.1) partition details is as follows,
>>
>> A4MD09512:/etc/xen/vm # df -h
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sda5             109G   43G   60G  42% /
>> udev                  894M  136K  894M   1% /dev
>> /dev/sda1             190M   44M  137M  25% /boot
>>
>> I have created RHEL 5.2 image file manually using Xen virt-manager.
>> Find below the file type I have created manually,
>>
>> oneadmin at A4MD09512:/opt/nebula/ONE/bin> file ../../images/
>> Rhel_server_singlepart.img
>>
>> ../../images/Rhel_server_singlepart.img: x86 boot sector; partition
>> 1: ID=0x83, active, starthead 1, startsector 63, 14715477 sectors;
>> partition 2: ID=0x82, starthead 0, startsector 14715540, 2040255
>> sectors
>>
>> I am giving the above image created as the source image for open
>> nebula.
>> If I try to boot, VM is getting booted but it giving an error
>> "invalid root filesystem -- exiting to /bin/sh" and booting is not
>> complete.
>> I know its not able find the root file system, but is there any
>> issue with my configuration as such.
>>
>> Let me know where I am doing wrong.  Thanks in Advance.
>>
>> Thanks,
>> Harish
>>
>> -----Original Message-----
>> From: Javier Fontan [mailto:jfontan at fdi.ucm.es]
>> Sent: Tuesday, April 21, 2009 5:56 PM
>> To: Harishbabu Nagaraj
>> Cc: Ruben S. Montero; users at opennebula.org; Sarath Kumar Bheemaraju
>> Subject: Re: [one-users] FW: Problem in deploying a VM
>>
>>
>> Hello,
>>
>> On Apr 21, 2009, at 1:18 PM, Harishbabu Nagaraj wrote:
>>
>>> Output of $ file /opt/nebula/images/Rhel_Server_5.3.img
>>>
>>> /opt/nebula/images/Rhel_Server_5.3.img: x86 boot sector; partition
>>> 1: ID=0x83, active, starthead 1, startsector 63, 20878
>>> 2 sectors; partition 2: ID=0x8e, starthead 0, startsector 208845,
>>> 16161390 sectors, code offset 0x48
>>>
>>> Let us know if you need any more details.
>>
>>
>> The image you have is a disk image with partitions. From what I see  
>> it
>> already has defined 2 partitions, the first one is a linux partition
>> and the second one LVM. Here is an excerpt of of partition types got
>> with "sfdisk -T":
>>
>> 82  Linux swap / Solaris
>> 83  Linux
>> 8e  Linux LVM
>>
>> To use that kind of disk images you have to specify the disk as sda
>> (or hda) as it is a whole disk. The OS will create the sda1 and sda2
>> devices accordingly. Also change the swap image to sdb or any other
>> device to not clash with the already existing lvm partition in sda2.
>>
>> I hope it helps.
>>
>> Bye
>>
>> --
>> Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
>> DSA Research Group: http://dsa-research.org
>> Globus GridWay Metascheduler: http://www.GridWay.org
>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>>
>>
>> http://www.mindtree.com/email/disclaimer.html
>
> --
> Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>
>
> http://www.mindtree.com/email/disclaimer.html

-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org