Hi, As per you given the info,
Your secondary storage is "/export/secondary, But you have downloaded the template into /mnt/secondary. Please check the below command and reply it. You reran command is : # cloud-install-sys-tmplt -m* /mnt/secondary* -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2-h xenserver -F Please run this below command instead of above cloud-install-sys-tmplt -m */export/secondary* -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2-h xenserver -F ---- Thanks, Yugnadhar Yetham On Thu, Oct 24, 2013 at 9:00 PM, Lisa B. <nordlicht1...@hotmail.de> wrote: > Hey! > > I have installed XenServer 6.2 and Cloudstack 4.2. > Added local primary storage via CS UI > Added NFS secondary storage "/export/secondary" via CS UI > Added NFS secondary storage "/export/secondary" via XenCenter to the host > (to check the connectivity between hypervisor host and management server > (also NFS server)) > > I followed the instructions on how to download and install the system vm > template via command line.The UI shows the system vm template as downloaded > and ready. > > The automatically added "CentOS 5.6(64-bit) no GUI (XenServer)" is "ready: > no" and its state field is empty. > A manually added ISO from a local webserver is also "ready: no" and has an > empty state field. > > I also added the NFS /export/secondary directory as NFS secondary storage > staging. Is that correct? I got confused whether the staging is necessary > or not.(?) > > The SSVM tries to start about every 2 minutes (CS UI shows both SSVM and > CPVM in either starting or stopped state). In XenCenter I am observing that > the VM gets started for two seconds and is powered down immediately. > In XenCenter I can see Virtual disks "Template routing-1" and "ROOT-2601" > in <local primary storage uuid of host>. > When the SSVM tries to start, XenCenter shows v-2601-VM as the connected > VM for ROOT-2601 for 2 seconds. The ROOT-2601 remains on the host, but the > VM shuts down immediately. v-2601-VM will start once more, connect to the > ROOT-2601 volume and immediately shut down again. After the second attempt > the ROOT-2601 will be deleted and on the next try the instance id will > increase by 1 (2602). > > The Xenserver error log points to a problem with the pygrub bootloader. > [BOOTLOADER_FAILED, OpaqueRef:f7ae32b4-a32a-6278-7ecb-9904bbd20875, Unable > to find partition containing kernel > (starting from line 132 in the attached logfile) > > I mounted nfs:/export/secondary/template/tmpl/1/1 to /tmp/secondary on the > xenserver host but that didn't make any difference. > > I also reran the systemvm template command > cloud-install-sys-tmplt -m /mnt/secondary -u > http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2-h > xenserver -F > Is it still the correct URL for CS 4.2? It was successfully installed once > again as it was during installation. > > Now where should I investigate more? I assume the SSVM has to start first > and then download the templates so I should fix the SSVM issue first. But > how? > > You can find the variables passed to the SSVM and my network details below. > > Thanks in advance! > Lisa > > variables passed to ssvm on startup > > -- quiet console=hvc0% > template=domP% > type=secstorage% > host=192.168.2.50% > port=8250% > name=s-2601-VM% > zone=1% > pod=1% > guid=s-2601-VM% > > resource=org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource% > instance=SecStorage% > sslcopy=true% > role=templateProcessor% > mtu=1500% > eth2ip=192.168.2.151% > eth2mask=255.255.255.0% > gateway=192.168.2.1% > eth0ip=169.254.3.153% > eth0mask=255.255.0.0% > eth1ip=192.168.2.68% > eth1mask=255.255.255.0% > mgmtcidr=192.168.2.0/24% > localgw=192.168.2.1% > private.network.device=eth1% > eth3ip=192.168.2.69% > eth3mask=255.255.255.0% > storageip=192.168.2.69% > storagenetmask=255.255.255.0% > storagegateway=192.168.2.1% > internaldns1=192.168.2.1% > dns1=192.168.2.1 > > (basic) network setup: > #zone > # name: cloudstack1 > # externer dns: 192.168.2.1 > # interner dns: 192.168.2.1 > #pod > # name: cloudstack1-pod1 > # gateway: 192.168.2.1 > # netzmaske: 255.255.255.0 > # ip-range: 192.168.2.51 - 192.168.2.90 > #add guest network (cloudstack1-pod1> ip allocations) > # schnittstelle: 192.168.2.1 > # netzmaske: 255.255.255.0 > # ip range: 192.168.2.151 - 192.168.2.190 > #host hinzufügen > # host name: 192.168.2.98
