I don't see a mention of cloud0 in the log. It might come from within the agent itself trying to restore some defaults after a reset or delete.
I do note some other perculiar thing: Around the following log fragment a lot of nulls are in the file. Also the meassage is not filling one with hope: note that the nuls are output from 'lsmod|grep kvm'. Is this the problem you tackeled in Dusseldorf? 2014-10-14 17:59:05,664 DEBUG [c.c.u.s.SSHCmdHelper] (catalina-exec-11:ctx-ba00ae78 ctx-b1389dca) Executing cmd: cloudstack-setup-agent -m 10.158.231.29 -z 1 -p 1 -c 1 -g 4a9064dc-4e61-3c36-949f-d474d64f5e56 -a --pubNic=cloudbr0 --prvNic=cloudbr0 --guestNic=cloudbr0 2014-10-14 17:59:06,774 DEBUG [c.c.u.s.SSHCmdHelper] (catalina-exec-11:ctx-ba00ae78 ctx-b1389dca) cloudstack-setup-agent -m 10.158.231.29 -z 1 -p 1 -c 1 -g 4a9064dc-4e61-3c36-949f-d474d64f5e56 -a --pubNic=cloudbr0 --prvNic=cloudbr0 --guestNic=cloudbr0 output:Starting to configure your system: Checking KVM...[Failed] Please enable KVM on this machine Try to restore your system: On Thu, Oct 16, 2014 at 5:16 PM, Marc Leeman <marc.lee...@gmail.com> wrote: > No: > > I killed the process at the boot the day before yesterday (thanks to the > cloudstack guys that I made to miss the boot crawl): there was indeed a > problem with that; NO vsm were starting. > > After killing the old stuck programs; we got further and after downloading > the svm images manually with the http_proxy var; the svms started. > > However then we hit the bridging problem. > -- Daan
