FYI
On Mon, Feb 20, 2012 at 3:06 PM, Tino Vazquez <[email protected]> wrote: > Dear Vladimir, > > comments inline, > > -- > Constantino Vázquez Blanco, MSc > Project Engineer > OpenNebula - The Open-Source Solution for Data Center Virtualization > www.OpenNebula.org | @tinova79 | @OpenNebula > > > > On Sat, Feb 18, 2012 at 2:43 AM, Vladimir Vuksan <[email protected]> wrote: >> I get I need vSphere CLI if I am gonna do dynamic network modes. It would be >> helpful to make that very clear on the VMWare driver page. > > It is an optional requirement, stated in the drivers page and in the > networking page for vmware, that is, the information is already > duplicated. > > That said we are >> still left with the limitation of not being able to use the unpaid version >> of ESXi with OpenNebula. I have installed vSphere CLI and I'm still get >> >> >> error: internal error HTTP response code 500 for call to 'RegisterVM_Task'. >> Fault: ServerFaultCode - fault.RestrictedVersion.summary > > Check the VI client, you are probably trying to register the same VM > twice, you will need to manually remove the VM from the ESX > hypervisor. > > regards, > > -T > > >> >> Am I missing something ? >> >> Thanks, >> >> Vladimir >> >> >> On Fri, 17 Feb 2012, Ruben S. Montero wrote: >> >>> Please read the documentation >>> >>> http://www.opennebula.org/documentation:rel3.2:vmwarenet >>> >>> There you will find the two network modes for VMware and the >>> requirements for each mode (dynamic requires vSphere CLI, as described >>> in the first sentence) >>> >>> Also as stated in the documentation, release notes for example, >>> *clearly* says that: >>> >>> "Notable improvements include, but are not limited to: >>> >>> VMware, out-of-the-box support for VMware that now includes live >>> migration, advanced contextualization, image and network management." >>> >>> OpenNebula 3.2 includes full-feature support for VMware. >>> >>> Thanks for the feedback and good luck! >>> >>> Ruben >>> >>> >>> On Fri, Feb 17, 2012 at 9:42 PM, Vladimir Vuksan <[email protected]> wrote: >>>> >>>> I faked this by creating an empty executable file which got me to this >>>> error >>>> >>>> error: internal error HTTP response code 500 for call to >>>> 'RegisterVM_Task'. >>>> Fault: ServerFaultCode - fault.RestrictedVersion.summary >>>> >>>> I googled it and found this post >>>> >>>> >>>> http://lists.opennebula.org/pipermail/users-opennebula.org/2011-December/007223.html >>>> >>>> which basically says that only way you can get ESXi going is to either be >>>> in >>>> perpetual evaluation mode or by the unrestricted version of ESXi. >>>> >>>> I would think this should be prominently mentioned in the documentation >>>> so >>>> people don't waste time. >>>> >>>> Thanks, >>>> >>>> Vladimir >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >>> >>> >>> >>> >>> -- >>> Ruben S. Montero, PhD >>> Project co-Lead and Chief Architect >>> OpenNebula - The Open Source Solution for Data Center Virtualization >>> www.OpenNebula.org | [email protected] | @OpenNebula >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
