Re: Getting crazy with KVM network config

Dag Sonstebo writes: > > > Hi Mario, > first of all you may be better off just configuring untagged bridges on top of your NIC and let CloudStack take care of VLAN tagging But with one network card I need to probably to tag at least management network else manager cannot

Re: Getting crazy with KVM network config

On 1/8/16 2:32 PM, Mario Giammarco wrote: > ilya 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

Re: Getting crazy with KVM network config

ilya 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:

Re: Getting crazy with KVM network config

Mario Dont see anything crazy with what you are doing so far. I would suggest that you initially keep it simple and setup cloudstack with basic zone. The communication workflow you've been asking is as follows: CloudStack Management Server talks to KVM host on port 3922 CloudStack KVM Agent

Re: Getting crazy with KVM network config

Hi Mario, first of all you may be better off just configuring untagged bridges on top of your NIC and let CloudStack take care of VLAN tagging - I.e. if you don’t have the suggested VLANs 100/200/300 already configured and in use they don’t make sense. With regards to networking you configure

Getting crazy with KVM network config

Hello, I am evaluating cloudstack 4.7 I have followed instructions for creating kvm hosts with openvswitch networking (and vlan 100, 200, 300 as suggested) Tried creating a basic zone network in different ways. It seems ok but it cannot reaches secondary storage. It is due to the fact that I