[Users] [rhevm-api] Assign IP address to VM using Java SDK

[Juan Hernandez]

On 02/14/2014 03:28 PM, Tejesh M wrote:
> Tried with disabling the ISO Domain, still it is check for network
> instead of mount the CDROM
> 
> and my RHEV version is RHEV-H 6.5-20140121.0.el6ev
> 

Ok, that is the same version I'm testing with.

Please try to connect to the hypervisor and see what is the command line
of the qemu-kvm process created when you start the VM.

We will also probably need to look at the VDSM log file. It is in the
hypervisor, in /var/log/vdsm/vdsm.log.

> 
> On Fri, Feb 14, 2014 at 7:29 PM, Juan Hernandez <jhernand at redhat.com
> <mailto:jhernand at redhat.com>> wrote:
> 
>     On 02/14/2014 02:48 PM, Tejesh M wrote:
>     > CDROM is attached, but it is mounting the default iso from ISO Domain.
>     >
> 
>     Do you have that default CDROM explicitly attached to the VM? If so then
>     you need to detach it. To be absolutely sure that there isn't any CDROMs
>     from the ISO domain attached to the VM you can just put the ISO domain
>     in maintenance, just for testing this.
> 
>     What version of the hypervisor are you using?
> 
>     >
>     > On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez
>     <jhernand at redhat.com <mailto:jhernand at redhat.com>
>     > <mailto:jhernand at redhat.com <mailto:jhernand at redhat.com>>> wrote:
>     >
>     >     On 02/14/2014 02:07 PM, 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.
>     >     >
>     >     >
>     >
>     >     The messages in that screen shot mean that cloud-init is trying to
>     >     locate its configuration via the network instead of inside the
>     CDROM. So
>     >     this probably means that the CDROM isn't attached correctly to
>     the VM.
>     >     Please try to find the options of the qemu-kvm command as I
>     described in
>     >     a previous mail.
>     >
>     >     >
>     >     >
>     >     > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez
>     >     <jhernand at redhat.com <mailto:jhernand at redhat.com>
>     <mailto:jhernand at redhat.com <mailto:jhernand at redhat.com>>
>     >     > <mailto:jhernand at redhat.com <mailto:jhernand at redhat.com>
>     <mailto:jhernand at redhat.com <mailto:jhernand at redhat.com>>>> wrote:
>     >     >
>     >     >     On 02/14/2014 12:27 PM, Tejesh M wrote:
>     >     >     > Here is the list:
>     >     >     >
>     >     >     > [root at 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


-- 
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.