cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjeev Neelarapu <>
Subject RE: cloudstack 4.1 KVM There no secondary storage for secondary VM
Date Thu, 03 Oct 2013 05:48:57 GMT
If you have created the bridges as per the instructions in section " Configuring the
network bridges" then you need to specify those bridge names (e.g cloudbr0 and cloudbr1) as
traffic labels in the physical network for respective traffics like guest and management traffic.
 After this destroy all the vms (If any are already created) and re-launch. 

Hope this will solve the problem.


-----Original Message-----
From: motty cruz [] 
Sent: Tuesday, October 01, 2013 11:05 PM
Subject: Re: cloudstack 4.1 KVM There no secondary storage for secondary VM

yes, I did.however i think cloudstack traffic is trying to go through public network and NFS
server in an a private network. each hypervisor has two network cards, public and private
private is nic ifcfg-eth0 and public ifcfg-eth1

the management has only one network interface, configured to static on the private network(same
subnet as nfs server)

I believe that my problem is network bridges on my hypervisor machine,  I followed this guide:

but no success.

On Tue, Oct 1, 2013 at 9:08 AM, <> wrote:

> Do you have an NFS share created and added to Cloudstack for it to use 
> as Secondary Storage?
> ----- Original Message -----
> From: "motty cruz" <>
> To:
> Sent: Monday, September 30, 2013 8:43:05 PM
> Subject: cloudstack 4.1 KVM There no secondary storage for secondary 
> VM
> Hello, I need help!
> I have installed CloudStack 4.1 on CentOS, I have two hypervisors KVM 
> running on CentOS 6.4. both KVM hypervison have 2 network cards one 
> have static public IP and 2nd has a private IP. can someone point the 
> steps to have basic network to run with CloudStack?
> currently I have cloudstack working but the error I'm getting is 
> "There are no secondary storage for secondary VM" I know is because my 
> network interfaces are not configure correctly.
> Thanks,
>  Motty

View raw message