On Fri, Apr 19, 2013 at 7:34 AM, Abhinandan Prateek <cloudst...@aprateek.com > wrote:
> > > On 18/04/13 10:02 PM, "Rohit Yadav" <bhais...@apache.org> wrote: > > >On Thu, Apr 18, 2013 at 7:47 PM, Abhinandan Prateek > ><cloudst...@aprateek.com > >> wrote: > > > >> > >> While debugging the VMWare system template fixed the cd rom device name > >> that was causing the systemvm.iso not to load. > >> After this the SSVM and CPVM are coming up fine. > >> > >> On router VM creation though it failed as this file > >> /etc/udev/rules.d/70-persistent-net.rules was present in the template > >>as > >> a directory ! > >> This file is recreated on reboot so I have created another template > >>after > >> removing this directory. > >> > >> > >Oh man! Yes Abhi we don't need this file. I remember removing this file > >which is done in cleanup.sh: > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob;f=tools/ap > >pliance/definitions/systemvmtemplate/cleanup.sh;h=9e98ab03531f0c8fee6c0402 > >31e5d0f4871ae777;hb=f4240e1cea58be0ea7b50c77a018d7c63e3faf15 > > > >Maybe I missed it while manually installing vmware-tools via vmware > >fusion. > >The open-vm-tools based appliance won't have this issue: > > > http://people.apache.org/~bhaisaab/cloudstack/systemvmtemplates/systemvmte > >mplate-openvmtools-vmware.ova > > Yes, the template in general works fine. But due to presence of that > directory the cloud-early-config that checks for sanity of that file > continues to reboot. Do make that change in the script and generate a new > set. > Cool! Fixed on master: 81e1ba3bb406f9546f0d46ccbfa3fbbb35b762e2 Fired up a new systemvm build: http://jenkins.cloudstack.org/job/build-systemvm-master/143/ > > > > > > >> Please, confirm if that is right. I will publish the template soon as it > >> is still uploading. > >> > > > >Cool, Abhi did you reuse the appliance I had shared or created your own? > >Share any special steps that were needed to be done. > > I started with the one generated by jenkins that you setup. There were > some issues to make it work with cloudstack. > Once we have a fully functional appliance I will list down the additional > steps. Some of them can be then fixed in the scripts. > Sure, thanks. Cheers. > > > >Cheers. > > > > > >> > >> -abhi > >> > >> > > >
