<div dir="ltr"><div>Tried with disabling the ISO Domain, still it is check for network instead of mount the CDROM<br><br></div>and my RHEV version is RHEV-H 6.5-20140121.0.el6ev<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Feb 14, 2014 at 7:29 PM, Juan Hernandez <span dir="ltr"><<a href="mailto:jhernand@redhat.com" target="_blank">jhernand@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 02/14/2014 02:48 PM, Tejesh M wrote:<br>
> CDROM is attached, but it is mounting the default iso from ISO Domain.<br>
><br>
<br>
Do you have that default CDROM explicitly attached to the VM? If so then<br>
you need to detach it. To be absolutely sure that there isn't any CDROMs<br>
from the ISO domain attached to the VM you can just put the ISO domain<br>
in maintenance, just for testing this.<br>
<br>
What version of the hypervisor are you using?<br>
<br>
><br>
> On Fri, Feb 14, 2014 at 6:54 PM, Juan Hernandez <<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a><br>
> <mailto:<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a>>> wrote:<br>
><br>
> On 02/14/2014 02:07 PM, Tejesh M wrote:<br>
> > Thanks, now i could see the cloud-init option in Run Once.. I did<br>
> > selected "Other Linux" instead of exact Linux flavor. And sorry,<br>
> instead<br>
> > of Reply All, i clicked on Reply and sent that mail.<br>
> ><br>
> > Now, when i start VM from Run Once with Cloud-init options like<br>
> Hostname<br>
> > & Root Password, in the startup screen of VM, it show the error as<br>
> > attached screenshot.<br>
> ><br>
> ><br>
><br>
> The messages in that screen shot mean that cloud-init is trying to<br>
> locate its configuration via the network instead of inside the CDROM. So<br>
> this probably means that the CDROM isn't attached correctly to the VM.<br>
> Please try to find the options of the qemu-kvm command as I described in<br>
> a previous mail.<br>
><br>
> ><br>
> ><br>
> > On Fri, Feb 14, 2014 at 5:09 PM, Juan Hernandez<br>
> <<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a> <mailto:<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a>><br>
> > <mailto:<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a> <mailto:<a href="mailto:jhernand@redhat.com">jhernand@redhat.com</a>>>> wrote:<br>
> ><br>
> > On 02/14/2014 12:27 PM, Tejesh M wrote:<br>
> > > Here is the list:<br>
> > ><br>
> > > [root@rhevm ~]# rpm -qa 'rhevm*'<br>
> > ><br>
> > > rhevm-lib-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-setup-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-spice-client-x86-msi-3.3-8.el6_5.noarch<br>
> > > rhevm-branding-rhev-3.3.0-1.5.el6ev.noarch<br>
> > > rhevm-restapi-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-sdk-java-javadoc-1.0.0.29-0.1.el6ev.noarch<br>
> > > rhevm-image-uploader-3.3.1-2.el6ev.noarch<br>
> > > rhevm-setup-plugins-3.3.0-4.el6ev.noarch<br>
> > > rhevm-cli-3.3.0.13-1.el6ev.noarch<br>
> > > rhevm-log-collector-3.3.1-5.el6ev.noarch<br>
> > > rhevm-dependencies-3.3.5-1.el6ev.noarch<br>
> > > rhevm-spice-client-x64-msi-3.3-8.el6_5.noarch<br>
> > > rhevm-tools-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-sdk-python-3.3.0.21-1.el6ev.noarch<br>
> > > rhevm-iso-uploader-3.3.0-2.el6ev.noarch<br>
> > > rhevm-websocket-proxy-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-backend-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-spice-client-x64-cab-3.3-8.el6_5.noarch<br>
> > > rhevm-userportal-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-dwh-3.3.0-29.el6ev.noarch<br>
> > > rhevm-dbscripts-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-reports-3.3.0-28.el6ev.noarch<br>
> > > rhevm-sdk-java-1.0.0.29-0.1.el6ev.noarch<br>
> > > rhevm-doc-3.3.0-3.el6eng.noarch<br>
> > > rhevm-webadmin-portal-3.3.0-0.46.el6ev.noarch<br>
> > > rhevm-spice-client-x86-cab-3.3-8.el6_5.noarch<br>
> > ><br>
> ><br>
> > Ok, you are using RHEV-M 3.3, that is correct, it has support for<br>
> > cloud-init. The only reason I can think of that prevents using the<br>
> > cloud-init options in 3.3 is that the operating system isn't<br>
> defined as<br>
> > a Linux variant. Select the VM, click the "Edit" button and<br>
> make sure to<br>
> > select a Linux operating system in the "Operating System"<br>
> list. The<br>
> > closer to the actual operating system the better. Then try again<br>
> > "Run Once".<br>
> ><br>
> > To avoid making this for every VM you create, you should do<br>
> the change<br>
> > in the template as well.<br>
> ><br>
> > By the way, please reply to the list, there may be other people<br>
> > interested in your same issue.<br>
> ><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta<br>
3ºD, 28016 Madrid, Spain<br>
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div>Thanks & Regards</div>
<div>Tejesh</div>
</div>