On 16 October 2014 16:10, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > >> My eye is not much more trained at this table but I'll have a peek in the >> code. It seems to e that cloudstack should be configuring the bridge >> instead of the cloud0 device. I have no idea if this is a config err of >> yours or a bug. >> >> My assuptions: >> you are using kvm as hypervisor >> > > ack. > > >> you are running version 4.3.1 >> > > dpkg -l |grep cloudstack > ii cloudstack-agent 4.3.1 > all CloudStack agent > ii cloudstack-cli 4.3.1 > all The CloudStack CLI called CloudMonkey > ii cloudstack-common 4.3.1 > all A common package which contains files which are shared by > several CloudStack packages > ii cloudstack-management 4.3.1 > all CloudStack server library > > > >> >> any other info? I might want to see your logs during install and zone >> definition later, you still have them? >> > > > I still have all the log files on the server. > > The VMs should be connected to the same 172.16.x.x network as the host > because of access to multicast devices is needed. > > For the rest, we've been looking around on the system until it started > dawning on us that there were some scripts trying to download things and > got blocked by not using the proxy. > > We could not figure out whay the SVMs said starting; but got stuck there. > > I downloaded the SVM images with the script and the VMS started. >
The log file is http://crichton.supercomputerrobot.com/~marc/downloads/management-server.log.2014-10-14.gz and the firewall has been disabled already; so it should not be dependent on this.
