Re: [Users] [rhevm-api] Assign IP address to VM using Java SDK
On 14.02.14 18:37, Tejesh M wrote:
Thanks, now i could see the cloud-init option in Run Once.. I did
selected
"Other Linux" instead of exact Linux flavor. And sorry, instead of Reply
All, i clicked on Reply and sent that mail.
Now, when i start VM from Run Once with Cloud-init options like Hostname &
Root Password, in the startup screen of VM, it show the error as attached
screenshot.
It's looks like a cloud-init error,
Can you post the log file from the guest which suppose to be at:
/var/log/cloud-init.log
On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez <jhernand(a)redhat.com> wrote:
> On 02/14/2014 12:27 PM, Tejesh M wrote:
> > Here is the list:
> >
> > [root@rhevm ~]# rpm -qa 'rhevm*'
> >
> > rhevm-lib-3.3.0-0.46.el6ev.noarch
> > rhevm-setup-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch
> > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch
> > rhevm-restapi-3.3.0-0.46.el6ev.noarch
> > rhevm-3.3.0-0.46.el6ev.noarch
> > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch
> > rhevm-image-uploader-3.3.1-2.el6ev.noarch
> > rhevm-setup-plugins-3.3.0-4.el6ev.noarch
> > rhevm-cli-3.3.0.13-1.el6ev.noarch
> > rhevm-log-collector-3.3.1-5.el6ev.noarch
> > rhevm-dependencies-3.3.5-1.el6ev.noarch
> > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch
> > rhevm-tools-3.3.0-0.46.el6ev.noarch
> > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch
> > rhevm-iso-uploader-3.3.0-2.el6ev.noarch
> > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch
> > rhevm-backend-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch
> > rhevm-userportal-3.3.0-0.46.el6ev.noarch
> > rhevm-dwh-3.3.0-29.el6ev.noarch
> > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch
> > rhevm-reports-3.3.0-28.el6ev.noarch
> > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch
> > rhevm-doc-3.3.0-3.el6eng.noarch
> > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch
> > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch
> >
>
> Ok, you are using RHEV-M 3.3, that is correct, it has support for
> cloud-init. The only reason I can think of that prevents using the
> cloud-init options in 3.3 is that the operating system isn't defined as
> a Linux variant. Select the VM, click the "Edit" button and make sure to
> select a Linux operating system in the "Operating System" list. The
> closer to the actual operating system the better. Then try again "Run
> Once".
>
> To avoid making this for every VM you create, you should do the change
> in the template as well.
>
> By the way, please reply to the list, there may be other people
> interested in your same issue.
>
> --
> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
> 3ºD, 28016 Madrid, Spain
> Inscrita en el Reg. Mercantil de Madrid - C.I.F. B82657941 - Red Hat S.L.
>
--
Thanks & Regards
Tejesh