<div dir="ltr">Hi,<div><br></div><div>you are right, this is a bug. I have created a new bug report:</div><div><a href="http://dev.opennebula.org/issues/2172">http://dev.opennebula.org/issues/2172</a><br></div><div><br></div>
<div>thanks for the feedback,</div><div>Jaime</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 5:17 AM, MENDOZA, John Robert T. <span dir="ltr"><<a href="mailto:bert@asti.dost.gov.ph" target="_blank">bert@asti.dost.gov.ph</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi Jon, <br>
<br>
Thanks for the feedback. I don't believe its an issue with libvirtd
versions, but with the utilities managing libvirt. Opennebula can
already use the openvswitch bridges when defined in a VM xml
configuration file. <br>
<br>
Upon inspection of the attach_nic script, we can see there that it's
using "virsh attach-inteface" while attach_disk uses "virsh
attach-device" and uses an xml config file as input. The virsh
utility does not support openvswitch bridges when specified in the
command line yet. <br>
<br>
I'm seeing how we can device a workaround for this. Either we
re-program the attach_nic script to use "attach-device" or
encapsulate the ovs bridge as a libvirt network definition as
suggested in the libvirt-users list. <br>
<br>
<a href="https://www.redhat.com/archives/libvirt-users/2013-May/msg00034.html" target="_blank">https://www.redhat.com/archives/libvirt-users/2013-May/msg00034.html</a><br>
<br>
<br>
Thanks, <br>
Bert<div><div class="h5"><br>
<br>
<br>
<br>
<br>
<div>On Sunday, 14 July, 2013 04:32 PM, Jon
wrote:<br>
</div>
<blockquote type="cite">Hello John,
<div><br>
</div>
<div>I also get an error, see below.</div>
<div>I'm on ubuntu 13.04 using libvirt 1.0.2 and ovs versions : </div>
<div><br>
</div>
<div>
<div>ovs-vswitchd (Open vSwitch) 1.9.0</div>
<div>Compiled Mar 1 2013 14:34:38</div>
<div>OpenFlow versions 0x1:0x1</div>
</div>
<div><br>
</div>
<div>This is the relevant entry in my VM log:</div>
<div><br>
</div>
<div>
<div>Sun Jul 14 02:19:17 2013 [VMM][I]: Successfully execute
network driver operation: pre.</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][I]: Command execution fail:
/var/tmp/one/vmm/kvm/attach_nic one-24 02:00:0a:2a:00:65
ovsbr0 - 24 192.168.0.35</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][E]: attach_nic: Command
"virsh --connect qemu:///system attach-interface --domain
one-24 --type bridge --source ovsbr0 --mac 02:00:0a:2a:00:65"
failed: error: Failed to attach interface</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][I]: error: Unable to add
bridge ovsbr0 port vnet1: Operation not supported</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][E]: Could not attach NIC
(02:00:0a:2a:00:65) to one-24</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][I]: ExitCode: 1</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][I]: Failed to execute
virtualization driver operation: attach_nic.</div>
<div>Sun Jul 14 02:19:17 2013 [VMM][E]: Error attaching new VM
NIC: Could not attach NIC (02:00:0a:2a:00:65) to one-24</div>
<div><br>
</div>
<div>The oned log basically echos the same.</div>
<div><br>
</div>
<div>I have not tried to manually run the command though.</div>
<div><br>
</div>
<div>I also migrated the vm to a different host just in case it
was an ovs misconfig on the first host, but received the same
error.</div>
<div><br>
</div>
<div>Wondering if it's maybe just the version of libvirt we're
using.</div>
<div><br>
</div>
<div>This is really the first I've tested NIC hotplugging so
please take my results with a grain of salt.</div>
<div><br>
</div>
<div>Best Regards,</div>
<div>Jon A</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">On Sun, Jul 14, 2013 at 1:10 AM,
MENDOZA, John Robert T. <span dir="ltr"><<a href="mailto:bert@asti.dost.gov.ph" target="_blank">bert@asti.dost.gov.ph</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Everyone,<br>
<br>
Hope everyone is doing ok. :)<br>
<br>
Just want to ask if anybody has tried the NIC hot plug
functionality<br>
with OpenVSwitch. I'm testing ONE 4.0.1 and am having error
messages<br>
pertaining to the creation of the virtual ports for the VMs.
It<br>
outputs "error: Unable to add bridge ovsbr0 port vnetX:
Operation not<br>
supported". I did some Google'ing and it seems that the
virsh CLI<br>
utility has not been updated to support OpenVSwitch bridges
as it still<br>
treats the type bridge argument to be a linux bridge. I'm
thinking of<br>
recoding the "attach_nic" script to create an xml file and
use "virsh<br>
attach-device" to hot plug the NIC the same way disk hot
plugging is<br>
done. Any thoughts? Or is there something else I should
know why ONE<br>
used "attach-interface" in the first place?<br>
<br>
Thanks,<br>
John Robert Mendoza<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Join us at <a href="http://opennebulaconf.com/" style="color:rgb(17,85,204)" target="_blank">OpenNebulaConf2013</a> in Berlin, <span><span>24-26 September, 2013</span></span><br>
--<div>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:jmelis@opennebula.org" target="_blank">jmelis@opennebula.org</a></div>
</div>
</div>