You could add the following ppa and upgrade to a more recent version of libvirt:

https://launchpad.net/~pdffs/+archive/precise-virt



El 03/03/14 21:51, María Noelia Gil escribió:
I forgot to add the following line:

2014-03-03 20:24:07,964 WARN  [kvm.resource.LibvirtComputingResource] 
(main:null) LibVirt version 0.9.10 required for guest cpu mode, but version 
0.9.8 detected, so it will be disabled

El 03/03/2014, a las 01:09, Marcus <shadow...@gmail.com> escribió:

It doesn't look like you've enabled debug, you're only getting WARN
and INFO messages. Please enable debug.

On Sun, Mar 2, 2014 at 4:40 PM, María Noelia Gil <marianoelia....@um.es> wrote:
When I run "CloudStack-setup-agent" shows the following:

Starting to configure your system:
Configure Apparmor ...        [OK]
Configure Network ...         [OK]
Configure Libvirt ...
[OK]
Configure Firewall ...
[OK]
Configure Nfs ...             [OK]
Configure cloudAgent ...
[OK]
CloudStack Agent setup is done!

The log file displays the following.

2014-03-03 00:32:44,320 INFO  [cloud.agent.AgentShell] (main:null) Agent started
2014-03-03 00:32:44,321 INFO  [cloud.agent.AgentShell] (main:null) 
Implementation Version is 4.2.1
2014-03-03 00:32:44,322 INFO  [cloud.agent.AgentShell] (main:null) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2014-03-03 00:32:44,323 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to using properties file for storage
2014-03-03 00:32:44,324 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to the constant time backoff algorithm
2014-03-03 00:32:44,326 INFO  [cloud.utils.LogUtils] (main:null) log4j 
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2014-03-03 00:32:44,384 INFO  [cloud.agent.Agent] (main:null) id is 0
2014-03-03 00:32:44,396 INFO  [resource.virtualnetwork.VirtualRoutingResource] 
(main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
2014-03-03 00:32:45,020 WARN  [kvm.resource.LibvirtComputingResource] 
(main:null) LibVirt version 0.9.10 required for guest cpu mode, but version 
0.9.8 detected, so it will be disabled
2014-03-03 00:32:45,114 INFO  [kvm.resource.LibvirtComputingResource] 
(main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
2014-03-03 00:32:45,145 INFO  [cloud.agent.Agent] (main:null) Agent [id = 0 : 
type = LibvirtComputingResource : zone = default : pod = default : workers = 5 
: host = localhost : port = 8250
2014-03-03 00:32:45,154 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to localhost:8250
2014-03-03 00:32:45,333 INFO  [utils.nio.NioClient] (Agent-Selector:null) SSL: 
Handshake done
2014-03-03 00:32:45,334 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connected to localhost:8250
2014-03-03 00:32:45,662 INFO  [cloud.serializer.GsonHelper] 
(Agent-Handler-1:null) Default Builder inited.
2014-03-03 00:32:45,733 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
Proccess agent startup answer, agent id = 0
2014-03-03 00:32:45,733 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) Set 
agent id 0
2014-03-03 00:32:45,737 INFO  [cloud.agent.Agent] (AgentShutdownThread:null) 
Stopping the agent: Reason = sig.kill
2014-03-03 00:32:45,738 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
Startup Response Received: agent id = 0

I do not get to fix the error.

Thanks.

El 02/03/2014, a las 00:25, Marcus <shadow...@gmail.com> escribió:

changing



--
Fernando Guillén Camba
Unidade de Xestión de Infraestruturas TIC
Centro de Investigación en Tecnoloxías da Información (CITIUS)
Teléfono: 8818 16409
Correo: citius....@usc.es

Reply via email to