I don't see " failing to get physical interface from bridge" in agent.log.
I am pasting the first few lines from the agent.log before attempt was made to
start the system vms:
2013-01-28 22:04:37,354 INFO [utils.component.ComponentLocator] (main:null)
Unable to find components.xml
2013-01-28 22:04:37,356 INFO [utils.component.ComponentLocator] (main:null)
Skipping configuration using components.xml
2013-01-28 22:04:37,356 INFO [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.1.0.20130128045141
2013-01-28 22:04:37,356 INFO [cloud.agent.AgentShell] (main:null)
agent.properties found at /etc/cloud/agent/agent.properties
2013-01-28 22:04:37,358 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to using properties file for storage
2013-01-28 22:04:37,360 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to the constant time backoff algorithm
2013-01-28 22:04:37,430 INFO [cloud.agent.Agent] (main:null) id is
2013-01-28 22:04:37,445 ERROR [cloud.resource.ServerResourceBase] (main:null)
Nics are not configured!
2013-01-28 22:04:37,450 INFO [cloud.resource.ServerResourceBase] (main:null)
Designating private to be nic cloudbr0
2013-01-28 22:04:37,547 INFO [resource.virtualnetwork.VirtualRoutingResource]
(main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
2013-01-28 22:04:38,482 INFO [kvm.resource.LibvirtComputingResource]
(main:null) No libvirt.vif.driver specififed. Defaults to BridgeVifDriver.
2013-01-28 22:04:38,545 INFO [cloud.agent.Agent] (main:null) Agent [id = new :
type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host =
10.223.57.2 : port = 8250
2013-01-28 22:04:38,558 INFO [utils.nio.NioClient] (Agent-Selector:null)
Connecting to 10.223.57.2:8250
2013-01-28 22:04:38,796 INFO [utils.nio.NioClient] (Agent-Selector:null) SSL:
Handshake done
2013-01-28 22:04:39,239 INFO [cloud.serializer.GsonHelper]
(Agent-Handler-1:null) Default Builder inited.
2013-01-28 22:04:39,294 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
Proccess agent startup answer, agent id = 0
2013-01-28 22:04:39,294 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Set
agent id 0
2013-01-28 22:04:39,300 INFO [cloud.agent.Agent] (Agent-Handler-2:null)
Startup Response Received: agent id = 0
2013-01-28 22:04:39,570 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null)
Proccess agent ready command, agent id = 1
2013-01-28 22:04:39,570 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null)
Set agent id 1
2013-01-28 22:04:39,571 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null)
Ready command is processed: agent id = 1
2013-01-28 22:04:39,667 INFO [cloud.agent.Agent] (agentRequest-Handler-5:null)
Proccess agent ready command, agent id = 1
2013-01-28 22:04:39,667 INFO [cloud.agent.Agent] (agentRequest-Handler-5:null)
Set agent id 1
2013-01-28 22:04:39,667 INFO [cloud.agent.Agent] (agentRequest-Handler-5:null)
Ready command is processed: agent id = 1
2013-01-28 22:07:08,861 WARN [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Exception
com.cloud.exception.InternalErrorException: Failed to create vnet 1363: Set
name-type for VLAN subsystem. Should be visible in /proc/net/vlan/configERROR:
trying to add VLAN #1363 to IF -:br-1363:- error: No such deviceFailed to
create vlan 1363 on pif: br-1363.
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVnet(BridgeVifDriver.java:170)
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.createVlanBr(BridgeVifDriver.java:156)
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:119)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3301)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3069)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3093)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1174)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
at com.cloud.utils.nio.Task.run(Task.java:83)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
-Thanks
Sangeetha
-----Original Message-----
From: Marcus Sorensen [mailto:[email protected]]
Sent: Monday, January 28, 2013 4:09 PM
To: [email protected]
Subject: Re: Not able to start System Vms on KVM host
Looking at the ipv6 branch... do you see a "failing to get physical interface
from bridge" in your agent log?
On Mon, Jan 28, 2013 at 5:07 PM, Marcus Sorensen <[email protected]> wrote:
> What sort of system is this? I'm just wondering when to expect 'em'
> type devices. This is going to get ugly if we can't anticipate a
> reasonable naming convention for physical nics.
>
>
>
> On Mon, Jan 28, 2013 at 4:40 PM, Sangeetha Hariharan
> <[email protected]> wrote:
>> em1
