[one-users] ESX ability to see existing VMs

[Jonathan Kelley]

I apologize for being naive but how do you register the VMs on ESX. I
attached my ESX node with ./onehost commands and it show up.

Now how do I add the VMs which are not registered on the ESX but live in the
datastores on that ESX machine?

Or do they have to live in the shared storage path?

Thanks,
Jon


On Tue, Mar 16, 2010 at 5:54 AM, Tino Vazquez <tinova at fdi.ucm.es> wrote:

> Hi,
>
> So here is how it works: OpenNebula tries to register the VM, if
> already registered, it fails, if not, it registers the image and boots
> it up.
>
> If a VM is previously registered, OpenNebula won't know about it,
> won't report it, and will fail if you try to deploy it with onevm.
>
> Regards,
>
> -Tino
>
> --
> Constantino Vázquez, Grid & Virtualization Technology
> Engineer/Researcher: http://www.dsa-research.org/tinova
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>
>
>
> On Mon, Mar 15, 2010 at 12:32 PM, Jonathan Kelley <jkelley at vm-labs.com>
> wrote:
> > Hi Tino,
> >
> > Yes my hosts are registered in esx and I can see them in vSphere, through
> > perl API and libvirt. Nothing shows up in opennebula commands. Does the
> > driver support esxi 4?
> >
> > Thanks.
> > -Jon
> >
> > On Mar 15, 2010, at 6:40 AM, Tino Vazquez <tinova at fdi.ucm.es> wrote:
> >
> >> Hi Jonathan,
> >>
> >> By register in ESX I mean that the Hypervisor is aware of the VM, even
> >> though it may not be running. If you use VMware's Virtual
> >> Infrastructure Client (VIC), you will be able to see which VMs are
> >> registered in a specific ESX (if they appear in the left side's tree
> >> view, then they are registered).
> >>
> >> Regards,
> >>
> >> -Tino
> >>
> >> --
> >> Constantino Vázquez, Grid & Virtualization Technology
> >> Engineer/Researcher: http://www.dsa-research.org/tinova
> >> DSA Research Group: http://dsa-research.org
> >> Globus GridWay Metascheduler: http://www.GridWay.org
> >> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> >>
> >>
> >>
> >> On Mon, Mar 8, 2010 at 7:17 PM, Jonathan Kelley <jkelley at vm-labs.com>
> >> wrote:
> >>>
> >>> Hi Tino,
> >>>
> >>> Thanks for your response. What do you mean by unregister them? Giving
> >>> the vmx file path or something to OpenNebula will then register them?
> >>>
> >>> Thanks,
> >>> Jon
> >>>
> >>>
> >>> On Mon, Mar 8, 2010 at 10:13 AM, Tino Vazquez <tinova at fdi.ucm.es>
> wrote:
> >>>>
> >>>> Hi Jonathan,
> >>>>
> >>>> OpenNebula will try and register existing VMs, so any preregistered
> >>>> VMs won't be able to be used with OpenNebula. To correctly use them,
> >>>> you will need to unregister them by hand first.
> >>>>
> >>>> Hope it helps,
> >>>>
> >>>> -Tino
> >>>>
> >>>> --
> >>>> Constantino Vázquez, Grid & Virtualization Technology
> >>>> Engineer/Researcher: http://www.dsa-research.org/tinova
> >>>> DSA Research Group: http://dsa-research.org
> >>>> Globus GridWay Metascheduler: http://www.GridWay.org
> >>>> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Mar 2, 2010 at 9:26 PM, Jonathan Kelley <jkelley at vm-labs.com>
> >>>> wrote:
> >>>>>
> >>>>> Hello,
> >>>>> I am fairly new to OpenNebula (today) but I got my ESX host to be
> added
> >>>>> (after some problems realizing I absolutely needed FQDN).
> >>>>> However my question is what is to come of the VMs that exist on my
> ESX
> >>>>> host.
> >>>>> Can OpenNebula register those VMs? Or can I only add/create new ones?
> >>>>> I am running OpenNebula 1.4 and ESXi 4.0.
> >>>>> Thanks,
> >>>>> Jon Kelley
> >>>>>
> >>>>> _______________________________________________
> >>>>> Users mailing list
> >>>>> Users at lists.opennebula.org
> >>>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >>>>>
> >>>>>
> >>>>
> >>>
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20100316/8f19106a/attachment-0003.htm>