You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "angeline shen (JIRA)" <ji...@apache.org> on 2013/03/18 04:32:16 UTC
[jira] [Commented] (CLOUDSTACK-101) OVS support in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604847#comment-13604847 ]
angeline shen commented on CLOUDSTACK-101:
------------------------------------------
Hi Hugo:
1. Per https://issues.apache.org/jira/browse/CLOUDSTACK-101
https://issues.apache.org/jira/browse/CLOUDSTACK-824
Is the requirement for OS CentOS 6.3 KVM or OS Ubuntu 12.10 KVM?
I was informed that CentOS 6.3 does not include Openvswitch . Unsure if this means non support for Openvswitch.
However, I found http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
Which provide procedures for installing KVM and Openvswitch 1.7.1 on CentOS 6.3
I was informed that Ubuntu 12.10 include Openvswitch.
2. Per http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
where Openvswitch 1.7.1 works with http://libvirt.org/sources/libvirt-0.10.1.tar.gz
I tested ACS 4.1 cloudsstack agent (which uses libvirt-0.9.10-21.el6.x86_64) with
Openvswitch 1.7.1 (which uses libvirt-0.10.1)
after adding host to Cloudstack management, SSVM failed to start with cloudstack agent errors in
Agentlog513.doc:
2013-03-15 00:00:05,273 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Failed to start domain: v-2-VM: unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
2013-03-15 00:00:05,274 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-2:null) Exception
org.libvirt.LibvirtException: unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Domain.processError(Unknown Source)
at org.libvirt.Domain.create(Unknown Source)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:1035)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3084)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1160)
at com.cloud.agent.Agent.processRequest(Agent.java:525)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
Cloudstack-agent.out:
2013-03-15 00:08:05,114{GMT} WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:) Failed to start domain: v-2-VM: unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
2013-03-15 00:08:05,115{GMT} WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:) Exception
org.libvirt.LibvirtException: unsupported configuration: this qemu binary requires libvirt to be compiled with yajl
at org.libvirt.ErrorHandler.processError(Unknown Source)
at org.libvirt.Connect.processError(Unknown Source)
at org.libvirt.Domain.processError(Unknown Source)
at org.libvirt.Domain.create(Unknown Source)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startDomain(LibvirtComputingResource.java:1035)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3084)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1160)
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)
2013-03-15 00:08:05,115{GMT} WARN [cloud.agent.Agent] (agentRequest-Handler-5:) Caught:
java.lang.NullPointerException
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.cleanupVMNetworks(LibvirtComputingResource.java:4211)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.handleVmStartFailure(LibvirtComputingResource.java:2980)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3104)
at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1160)
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)
3. So CentOS 6.3 KVM does not support openvswitch 1.7.1
attempt to use ASF 4.1 cloudstack-agent using libvirt-0.9.10-21 with openvswitch 1.7.1 using libvirt-0.10 failed
Attached agentlog503.doc cloudstack-agenterror.doc cloudstack-agent-out.doc
> OVS support in KVM
> ------------------
>
> Key: CLOUDSTACK-101
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-101
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Prasanna Santhanam
> Assignee: Hugo Trippaers
> Labels: kvm, ovs
> Fix For: 4.1.0
>
>
> OVS support currently works for XenServer but not in KVM. This is to improve the KVM agent to support OVS which has been part of the Linux kernel mainline for sometime now.
> Release Planning:
> Dev list discussion: http://markmail.org/thread/x2zncdgac52essxf
> Functional Spec: unknown
> Feature Branch: unknown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira