[one-users] VM remains in status BOOT

Daems Dirk dirk.daems at vito.be
Mon Jan 20 02:08:12 PST 2014


Hi Tino,



The deployment file is created.

See the contents below:



<domain type='vmware'>

        <name>one-26</name>

        <memory>524288</memory>

        <os>

                <type arch='i686'>hvm</type>

        </os>

        <devices>

                <disk type='file' device='disk'>

                        <source file='[135] 26/disk.0/disk.vmdk'/>

                        <target dev='hda'/>

                </disk>

                <disk type='file' device='cdrom'>

                        <source file='[135] 26/disk.1.iso'/>

                        <target dev='hdb'/>

                        <readonly/>

                </disk>

                <interface type='bridge'>

                        <source bridge='one-pg-7'/>

                        <mac address='02:00:c0:a8:0a:e5'/>

                </interface>

        </devices>

</domain>



Best regards,

Dirk

________________________________________

From: Tino Vazquez [cvazquez at c12g.com]

Sent: Monday, January 20, 2014 11:04 AM

To: Daems Dirk

Cc: users at lists.opennebula.org<mailto:users at lists.opennebula.org>

Subject: Re: [one-users] VM remains in status BOOT



Hi Dirk,



That means that the ESX is not even trying to boot up the VM. Let's

see if at least the deployment file is generated, in the front-end,

what are the contents of :



/var/lib/one/vms/26/deployment.0



Regards,



-Tino



--

OpenNebula - Flexible Enterprise Cloud Made Simple



--

Constantino Vázquez Blanco, PhD, MSc

Senior Infrastructure Architect at C12G Labs

www.c12g.com<http://www.c12g.com> | @C12G | es.linkedin.com/in/tinova



--

Confidentiality Warning: The information contained in this e-mail and

any accompanying documents, unless otherwise expressly indicated, is

confidential and privileged, and is intended solely for the person

and/or entity to whom it is addressed (i.e. those identified in the

"To" and "cc" box). They are the property of C12G Labs S.L..

Unauthorized distribution, review, use, disclosure, or copying of this

communication, or any part thereof, is strictly prohibited and may be

unlawful. If you have received this e-mail in error, please notify us

immediately by e-mail at abuse at c12g.com<mailto:abuse at c12g.com> and delete the e-mail and

attachments and any copy from your system. C12G thanks you for your

cooperation.





On Mon, Jan 20, 2014 at 9:19 AM, Daems Dirk <dirk.daems at vito.be<mailto:dirk.daems at vito.be>> wrote:

> Hi Tino,

>

>

>

> I don't see a vmware.log file in that directory:

>

>

>

> ~ # ls -al /vmfs/volumes/135/27/disk.0/

>

> drwxr-xr-x    1 root     root           560 Jan 17 12:28 .

>

> drwxr-xr-x    1 root     root           700 Jan 17 12:29 ..

>

> -rw-------    1 root     root     107374080 Jan 17 12:28 disk-flat.vmdk

>

> -rw-------    1 root     root           505 Jan 17 12:28 disk.vmdk

>

> ~ #

>

>

>

> FYI: I use the ttylinx VMWare image which is available in the OpenNebula

> marketplace.

>

>

>

> Best regards,

>

> Dirk

>

> ________________________________________

>

> From: Tino Vazquez [cvazquez at c12g.com]

>

> Sent: Friday, January 17, 2014 6:47 PM

>

> To: Daems Dirk

>

> Cc: users at lists.opennebula.org<mailto:users at lists.opennebula.org>

>

> Subject: Re: [one-users] VM remains in status BOOT

>

>

>

> Hi,

>

>

>

> Ok, let's see if we get more info from the vmware.log (please send it

>

> through), which can be found under the following path in the ESX:

>

>

>

> /vmfs/volumes/<system-ds-id>/27/disk.0/vmware.log

>

>

>

> Best regards,

>

>

>

> -Tino

>

>

>

> --

>

> OpenNebula - Flexible Enterprise Cloud Made Simple

>

>

>

> --

>

> Constantino Vázquez Blanco, PhD, MSc

>

> Senior Infrastructure Architect at C12G Labs

>

> www.c12g.com<http://www.c12g.com> | @C12G | es.linkedin.com/in/tinova

>

>

>

> --

>

> Confidentiality Warning: The information contained in this e-mail and

>

> any accompanying documents, unless otherwise expressly indicated, is

>

> confidential and privileged, and is intended solely for the person

>

> and/or entity to whom it is addressed (i.e. those identified in the

>

> "To" and "cc" box). They are the property of C12G Labs S.L..

>

> Unauthorized distribution, review, use, disclosure, or copying of this

>

> communication, or any part thereof, is strictly prohibited and may be

>

> unlawful. If you have received this e-mail in error, please notify us

>

> immediately by e-mail at abuse at c12g.com<mailto:abuse at c12g.com> and delete the e-mail and

>

> attachments and any copy from your system. C12G thanks you for your

>

> cooperation.

>

>

>

>

>

> On Fri, Jan 17, 2014 at 2:01 PM, Daems Dirk <dirk.daems at vito.be<mailto:dirk.daems at vito.be>> wrote:

>

>> Hi Tino,

>

>>

>

>>

>

>>

>

>> No, the VM is even not visible in the VSphere client.

>

>>

>

>> See the outputs of the onevm list and show commands below:

>

>>

>

>>

>

>>

>

>> -bash-4.1$ onevm list

>

>>

>

>>     ID USER     GROUP    NAME            STAT UCPU    UMEM HOST

>

>> TIME

>

>>

>

>>     27 oneadmin oneadmin MinimalVM       boot    0      0K devmesx1.i   0d

>

>> 00h29

>

>>

>

>>

>

>>

>

>>

>

>>

>

>> -bash-4.1$ onevm show 27

>

>>

>

>> VIRTUAL MACHINE 27 INFORMATION

>

>>

>

>> ID                  : 27

>

>>

>

>> NAME                : MinimalVM

>

>>

>

>> USER                : oneadmin

>

>>

>

>> GROUP               : oneadmin

>

>>

>

>> STATE               : ACTIVE

>

>>

>

>> LCM_STATE           : BOOT

>

>>

>

>> RESCHED             : No

>

>>

>

>> HOST                : devmesx1.intern.vgt.vito.be

>

>>

>

>> START TIME          : 01/17 13:28:37

>

>>

>

>> END TIME            : -

>

>>

>

>> DEPLOY ID           : -

>

>>

>

>>

>

>>

>

>> VIRTUAL MACHINE MONITORING

>

>>

>

>> NET_TX              : 0K

>

>>

>

>> USED CPU            : 0

>

>>

>

>> USED MEMORY         : 0K

>

>>

>

>> NET_RX              : 0K

>

>>

>

>>

>

>>

>

>> PERMISSIONS

>

>>

>

>> OWNER               : um-

>

>>

>

>> GROUP               : ---

>

>>

>

>> OTHER               : ---

>

>>

>

>>

>

>>

>

>> VM DISKS

>

>>

>

>>  ID TARGET IMAGE                               TYPE SAVE SAVE_AS

>

>>

>

>>   0 hda    ttylinux - VMware                   file   NO       -

>

>>

>

>>

>

>>

>

>> VM NICS

>

>>

>

>>  ID NETWORK              VLAN BRIDGE       IP              MAC

>

>>

>

>>   0 VMWareNetwork         yes vSwitch2     192.168.10.229

>> 02:00:c0:a8:0a:e5

>

>>

>

>>                                            fe80::400:c0ff:fea8:ae5

>

>>

>

>>

>

>>

>

>> VIRTUAL MACHINE HISTORY

>

>>

>

>> SEQ HOST            ACTION           REAS           START        TIME

>

>> PROLOG

>

>>

>

>>   0 devmesx1.intern none             none  01/17 13:28:38   0d 00h29m

>

>> 0h01m22s

>

>>

>

>>

>

>>

>

>> VIRTUAL MACHINE TEMPLATE

>

>>

>

>> AUTOMATIC_REQUIREMENTS="CLUSTER_ID = 120"

>

>>

>

>> CONTEXT=[

>

>>

>

>>   DISK_ID="1",

>

>>

>

>>   ETH0_IP="192.168.10.229",

>

>>

>

>>   NETWORK="YES",

>

>>

>

>>   TARGET="hdb" ]

>

>>

>

>> CPU="1"

>

>>

>

>> MEMORY="512"

>

>>

>

>> OS=[

>

>>

>

>>   ARCH="i686" ]

>

>>

>

>> TEMPLATE_ID="8"

>

>>

>

>> VMID="27"

>

>>

>

>>

>

>>

>

>> Regards,

>

>>

>

>> Dirk

>

>>

>

>>

>

>>

>

>> -----Original Message-----

>

>>

>

>> From: Tino Vazquez [mailto:cvazquez at c12g.com]

>

>>

>

>> Sent: vrijdag 17 januari 2014 13:48

>

>>

>

>> To: Daems Dirk

>

>>

>

>> Cc: users at lists.opennebula.org<mailto:users at lists.opennebula.org>

>

>>

>

>> Subject: Re: [one-users] VM remains in status BOOT

>

>>

>

>>

>

>>

>

>> Hi Dirk,

>

>>

>

>>

>

>>

>

>> Just checking, if you connect with the vSphere client, the VM is the _not_

>

>> running in the ESX?

>

>>

>

>>

>

>>

>

>> Regards,

>

>>

>

>>

>

>>

>

>> -Tino

>

>>

>

>> --

>

>>

>

>> OpenNebula - Flexible Enterprise Cloud Made Simple

>

>>

>

>>

>

>>

>

>> --

>

>>

>

>> Constantino Vázquez Blanco, PhD, MSc

>

>>

>

>> Senior Infrastructure Architect at C12G Labs www.c12g.com<http://www.c12g.com> | @C12G |

>

>> es.linkedin.com/in/tinova

>

>>

>

>>

>

>>

>

>> --

>

>>

>

>> Confidentiality Warning: The information contained in this e-mail and any

>

>> accompanying documents, unless otherwise expressly indicated, is

>

>> confidential and privileged, and is intended solely for the person and/or

>

>> entity to whom it is addressed (i.e. those identified in the "To" and "cc"

>

>> box). They are the property of C12G Labs S.L..

>

>>

>

>> Unauthorized distribution, review, use, disclosure, or copying of this

>

>> communication, or any part thereof, is strictly prohibited and may be

>

>> unlawful. If you have received this e-mail in error, please notify us

>

>> immediately by e-mail at abuse at c12g.com<mailto:abuse at c12g.com> and delete the e-mail and

>

>> attachments and any copy from your system. C12G thanks you for your

>

>> cooperation.

>

>>

>

>>

>

>>

>

>>

>

>>

>

>> On Fri, Jan 17, 2014 at 11:48 AM, Daems Dirk <dirk.daems at vito.be<mailto:dirk.daems at vito.be>> wrote:

>

>>

>

>>> Hi,

>

>>

>

>>>

>

>>

>

>>> I installed OpenNebula 4.2. I successfully configured a VMWare host, VMFS

>

>>> datastores and VMWare dynamic networking.

>

>>

>

>>> Now I want to deploy a VM on the VMWare host. The problem is that the VM

>

>>> remains in status BOOT. A directory with the VM ID is created in the VMFS

>

>>> system datastore and it contains a set of files. According to the logs

>>> the

>

>>> network configuration seems to be ok as well. If I look in the vSphere

>

>>> client, I see that a virtual machine group is added to the vSwitch.

>

>>

>

>>>

>

>>

>

>>> VM log file content:

>

>>

>

>>>

>

>>

>

>>> Fri Jan 17 11:43:07 2014 [DiM][I]: New VM state is ACTIVE.

>

>>

>

>>> Fri Jan 17 11:43:07 2014 [LCM][I]: New VM state is PROLOG.

>

>>

>

>>> Fri Jan 17 11:44:29 2014 [LCM][I]: New VM state is BOOT Fri Jan 17

>

>>

>

>>> 11:44:29 2014 [VMM][I]: Generating deployment file:

>

>>

>

>>> /var/lib/one/vms/26/deployment.0 Fri Jan 17 11:44:49 2014 [VMM][I]:

>

>>> Successfully execute network driver operation: pre.

>

>>

>

>>>

>

>>

>

>>> What cloud be wrong? Where should I start looking for problems? In the

>

>>> oned.log file I don't see anything abnormal.

>

>>

>

>>>

>

>>

>

>>> Any help appreciated!

>

>>

>

>>>

>

>>

>

>>> Best regards,

>

>>

>

>>> Dirk

>

>>

>

>>> VITO Disclaimer: http://www.vito.be/e-maildisclaimer

>

>>

>

>>> _______________________________________________

>

>>

>

>>> Users mailing list

>

>>

>

>>> Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>

>

>>

>

>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

>

>>

>

>> VITO Disclaimer: http://www.vito.be/e-maildisclaimer

>

>>

>

>> _______________________________________________

>

>> Users mailing list

>

>> Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>

>

>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

>

>>

>

> VITO Disclaimer: http://www.vito.be/e-maildisclaimer

>

> _______________________________________________

> Users mailing list

> Users at lists.opennebula.org<mailto:Users at lists.opennebula.org>

> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

>

VITO Disclaimer: http://www.vito.be/e-maildisclaimer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140120/6313b1ac/attachment-0002.htm>


More information about the Users mailing list