On 1/8/16 2:32 PM, Mario Giammarco wrote: > ilya <ilya.mailing.lists@...> writes: > >> In order for CloudStack to talk to System VM, it uses the KVM host as >> proxy, because the SystemVM is on link-local (unroutable) network. >> Specifically, CloudStack will connect to KVM on 3922 and execute a >> command called cloudstack-ssh >> >> example: cloudstack-ssh 169.254.0.139 >> > Thank you for these info. > Infact I tried to start with basic networking the configuration seemed all > ok, the system vm take a management and guest ip but then... nothing.
Would you please explain what you mean as "nothing". What state is your system VM in? > Now I discover that cloudstack uses also link-local network. > > So I have management (included storage), public, guest and link-local > > If these networks must be supported on kvm host I need to have 4 > vlans/bridges. How should I call them? > Assuming you have a server with only 2 NICs you can run your vlan trunking over these 2 links, here is one way how this might work. As mentioned by Dag, there is no need to create VLAN trunks on the host, cloudstack will manage that on your behalf. eth0 and eth1 - must be bonded as bond0 bond0 must be mapped to bridge mybridge0 create virtual interface for mybridge0 as mybridge0:1 and assign the ip address for host management via ssh (or anything else) in cloudstack, under physical network set Public, Management and Guest traffic labels as "mybridge0" If you trunking is done properly, you should be good to go... One thing to note, once the system vm start, run "top" command to check on host utilization, if CPU is around 100% for qemu process for extended period of time, you may have a kernel/qemu issue. If you run latest redhat 6 or 7 based kernel, you should be ok. Lastly, if you follow cloudstack guide, the trunks that are referenced in the docs, would need to exist on the switch, otherwise - it might/will not work, hence basic zone - is easiest model to go. Regards, ilya > Am I right? > > Thanks again, > Mario >
