[one-users] Xen onevm - please give more information
marimuthu.balasubramanian at wipro.com
marimuthu.balasubramanian at wipro.com
Sun Jan 11 20:05:18 PST 2009
Hi,
Thanks for your reply. We are able to move further. But when we submit VM template using "onevm" command the status is displayed as "failed". The following error message is logged in the log file.
"Message received: TRANSFER FAILURE 47 Error message not available"
The VM Template details are :
=============================
NAME = nodevm
CPU = 0.5
MEMORY = 128
OS = [kernel="/boot/vmlinuz-2.6.25.18-0.2-xen",initrd=
"/boot/initrd-2.6.2 5.18-0.2.xen",root="sda4" ]
DISK =
[source="/home/wipro/vm-image/disk0",target="sda4",readonly="no"]
DISK =
[type="swap",size=1024,target="sdb"]
NIC = [MAC = "00:03:0D:AD:D4:76",
bridge = eth0"]
Machine details are
===================
1. Machine 1 (Front-end) at ip 10.101.102.66: This has Open Nebula
installed on Ubuntu OS. The machine is NFS server. 2. Machine 2
(node) at ip 10.101.102.46 : This has Xen installed on Open Suse 11 (OS).
The machine 2(Node) has boot partition at /dev/sda4 partion. My doubt is whether we have to specify "/dev/sda4" or just "sda4". I have just mentioned the "swap" as mentioned in the document. Is the swap details are related to machine 2(node).
What is criteria to specify the size of the swap?
Regards
Marimuthu
-----Original Message-----
From: Ruben S. Montero [mailto:rubensm at dacya.ucm.es]
Sent: Thursday, January 08, 2009 2:12 AM
To: users at lists.opennebula.org
Cc: Marimuthu Balasubramanian (WT01 - Innovation Group); Lalithamba Vishwanathaiah (WT01 - Innovation Group)
Subject: Re: [one-users] Xen onevm - please give more information
Hi Marimuthu,
You setup seems completely right. Just a quick question, can you do ssh to
Machine2 without being prompt for a password (with the user running oned).
Also you may find some error information in $ONE_LOCATION/var/oned.log or in $ONE_LOCATION/var/sched.log.
Also you can use
NIC = [ network = "Public VLAN" ]
in you r template. Then OpenNebula will lease a MAC/address to your VM using the Public VLAN network. This will be automatically binded to eth0 as you specify in your template. (Note that you have to either configure the IP for the VM manually or with a context script, check:
http://www.opennebula.org:80/doku.php?id=documentation:rel1.2:nm#network_context_for_the_vm
)
Cheers
Ruben
On Wednesday 07 January 2009 15:59:57 marimuthu.balasubramanian at wipro.com
wrote:
> Hi Ruben,
>
> I am a newbie to Cloud Computing and OpenNebula.
> We are trying to configure opennebula as below but we are stuck up at
> onevm command.
>
> Following are the steps we have executed.
>
> 1. Machine 1 (Front-end) at ip 10.101.102.66: This has Open Nebula
> installed on Ubuntu OS. The machine is NFS server. 2. Machine 2
> (node) at ip 10.101.102.46 : This has Xen installed on Open Suse 11 (OS).
>
> We have started Machine 2 in Xen Mode and we have created a virtual
> machine
> (domU) on the same machine. We have 2 VM's available - dom0 and domU
>
> I have copied the disk image of domU (machine 2) to Front-end machine
> folder (/home/wipro/vm-image).
>
> As per transfer manager guide, I created a <VM_DIR> in machine 2.
> I have shared $ONE_LOCATION/var directory of Frontend to the node and
> its mounted to <VM_DIR> of node.
>
> Added <VM_DIR> entry in oned.conf.
>
>-----------------------------------------------------------------------
>----
>----------------------------------------------
>
> >From front-end machine executed the commands as follows :
>
> 1. onehost create 10.101.102.46 im_xen vmm_xen tm_ssh
>
> 2. onehost list :
>
> root at wipro-desktop:/opt/nebula/var
> <mailto:root at wipro-desktop:/opt/nebula/var> # onehost list HID NAME
> RVM TCPU FCPU ACPU TMEM FMEM STAT 13 10.101.102.46
> 0 0 100 on
>
> We are not sure why is RVM and TCPU showing 0 ? Pl give your inputs.
>
> 3. The VM network template is as follows :
>
> NAME="Public VLAN"
> TYPE=FIXED
> BRIDGE=eth0
> LEASES=[IP=10.101.102.46,MAC=00:03:0D:AD:D4:76]
>
> 4. Submitted the above template as : onevnet create <Template name>
>
> 5. onevnet list :
>
> NID NAME TYPE BRIDGE
> 3 Public VLAN Fixed eth0
>
> 6. onevnet show "Public VLAN" :
>
> NID : 3
> UID : 0
> Network Name : Public VLAN
> Type : Fixed
> Bridge : eth0
> ....: Template :....
> BRIDGE=eth0
> LEASES=IP=10.101.102.46,MAC=00:03:0D:AD:D4:76
> NAME=Public VLAN
> TYPE=FIXED
> ....: Leases :....
> IP = 10.101.102.46 MAC = 00:03:0d:ad:d4:76 USED = 0 VID = -1
>
> 7. The VM Template details are :
>
> NAME = nodevm
> CPU = 0.5
> MEMORY = 128
> OS = [kernel="/boot/vmlinuz-2.6.25.18-0.2-xen",initrd=
> "/boot/initrd-2.6.2 5.18-0.2.xen",root="sda4" ]
> DISK =
> [source="/home/wipro/vm-image/disk0",target="sda4",readonly="no"] DISK =
> [type="swap",size=1024,target="sdb"]
> NIC = [MAC = "00:03:0D:AD:D4:76",
> bridge = eth0"]
>
> 8. Submitted VM Template as : onevm submit <template>
>
> 9. root at wipro-desktop:/opt/nebula/var
> <mailto:root at wipro-desktop:/opt/nebula/var> # onevm list ID NAME STAT
> CPU MEM HOSTNAME TIME
> 33 nodevm pend 0 0 00 00:39:51
>
> We are not sure why the status is in the Pending state ?
> We followed the details provided in
>http://trac.opennebula.org/ticket/54
>
><http://blr-sjp-mbx01.wipro.com/exchweb/bin/redir.asp?URL=http://trac.o
>penn ebula.org/ticket/54> but still shows pending status.
>
> Can you pl provide inputs on why we are getting pending status ?
> Are we doing any thing wrong ?
> Regards
> Marimuthu
> Wipro Technologies
> Bangalore
>
> ________________________________
>
> From: users-bounces at lists.opennebula.org on behalf of Carlos Bernal
> Sent: Wed 1/7/2009 6:39 PM
> To: users at lists.opennebula.org
> Subject: Re: [one-users] Xen images with pygrub
>
> Ruben S. Montero escribió:
> > Hi,
> > This feature has been implemented, changes are in the trunk.
> > You can safely apply the patch from the changeset
> > (http://trac.opennebula.org/changeset/295) to the beta1 source tree.
> > If you give it a try let us know if it worked for you. We've also
> > updated the documentation, take a look at:
> >
> >
> >http://www.opennebula.org/doku.php?id=documentation:rel1.2:ug#os_and_
> >boot
> >_options_section
> >
> > Cheers
> >
> > Ruben
>
> Thank you!
>
> I'll try it as soon as possible.
>
> Cheers
> --
> Carlos Bernal Tijerín
> Centro Informático Científico de Andalucía (CICA) Avda.Reina Mercedes,
> s/n 41012 - Sevilla (España) Consejería de Innovación, Ciencia y
> Empresa Junta de Andalucía
>
>
>
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain proprietary, confidential or privileged
> information. If you are not the intended recipient, you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
--
+---------------------------------------------------------------+
Dr. Ruben Santiago Montero
Associate Professor
Distributed System Architecture Group (http://dsa-research.org)
URL: http://dsa-research.org/doku.php?id=people:ruben
Weblog: http://blog.dsa-research.org/?author=7
GridWay, http://www.gridway.org
OpenNEbula, http://www.opennebula.org
+---------------------------------------------------------------+
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
More information about the Users
mailing list