thr3ads.net - libvirt users - [libvirt-users] Using source installed open vswitch with libvirt(or virsh). [May 2013]

If this information is useful, please help other people find it:
Share via:

황진환

2013-May-27 09:22 UTC

[libvirt-users] Using source installed open vswitch with libvirt(or virsh).

P{font-size:10pt; line-height:16; margin-left:0; margin-top:0;
margin-right:0; margin-bottom:0; font-family:gulim;}
	(English is not my first language Sorry for my poor English )

	&nbsp;

	OS :&nbsp;

	Linux nc233 2632-220171el6x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012 x86_64
x86_64 x86_64 GNU/Linux

	CentOS release 63 (Final)

	open vswitch : 11190

	virsh : 100

	ibvirtd (libvirt) : 100

	&nbsp;

	I have tried to see what the virsh setting can do to open vswitch(ovs)
until now I had installed open vswitch from a source, not by using rpm or
rpm build of the source (I had tried to do &#39;ovs rpm build&#39;
described
at INSTALLRHEL included in ovs, But i failed to do it)

	&nbsp;

	What i tried is
this(http://blogscottloweorg/2012/11/07/using-vlans-with-ovs-and-libvirt/)

	&nbsp;I installed and started up ovs and it looked like properly working I
could create and delete bridges and ports with
&#39;ovs-vsctl&#39;&nbsp;

	&nbsp;

	1 what i created before running &#39;virsh net-define&#39;&nbsp;

	--------------------------------------------

	# ovs-vsctl show

	76d9d6aa-cfce-4868-bf99-7d16bcfe38eb

	&nbsp; &nbsp; Bridge &quot;br0&quot;

	&nbsp; &nbsp; &nbsp; &nbsp; Port &quot;br0&quot;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interface
&quot;br0&quot;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; type: internal

	&nbsp; &nbsp; &nbsp; &nbsp; Port &quot;eth1&quot;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interface
&quot;eth1&quot;

	--------------------------------------------

	&nbsp;

	&nbsp;

	2 And then runned &#39;virsh net-define netxml&#39;

	&#39;netxml&#39; i used

	--------------------------------------------

	&lt;network&gt;

	&nbsp; &nbsp; &lt;name&gt;ovs-network&lt;/name&gt;

	&nbsp; &nbsp; &lt;forward mode=&#39;bridge&#39;/&gt;

	&nbsp; &nbsp; &lt;bridge name=&#39;br0&#39;/&gt;

	&nbsp; &nbsp; &lt;virtualport
type=&#39;openvswitch&#39;/&gt;

	&nbsp; &nbsp; &lt;portgroup name=&#39;vlan-01&#39;
default=&#39;yes&#39;&gt;

	&nbsp; &nbsp; &lt;/portgroup&gt;

	&nbsp; &nbsp; &lt;portgroup name=&#39;vlan-02&#39;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;vlan&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;tag
id=&#39;2&#39;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/vlan&gt;

	&nbsp; &nbsp; &lt;/portgroup&gt;

	&nbsp; &nbsp; &lt;portgroup name=&#39;vlan-03&#39;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;vlan&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;tag
id=&#39;3&#39;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/vlan&gt;

	&nbsp; &nbsp; &lt;/portgroup&gt;

	&nbsp; &nbsp; &lt;portgroup name=&#39;vlan-all&#39;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;vlan
trunk=&#39;yes&#39;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;tag
id=&#39;2&#39;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;tag
id=&#39;3&#39;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/vlan&gt;

	&nbsp; &nbsp; &lt;/portgroup&gt;

	&lt;/network&gt;

	--------------------------------------------

	&nbsp;

	&nbsp;

	3 vmxml which was used for &#39;virsh define vmxml&#39;

	--------------------------------------------

	&lt;domain type=&quot;kvm&quot;&gt;

	&nbsp; &nbsp; &lt;name&gt;vm&lt;/name&gt;

	&nbsp; &nbsp; &lt;memory&gt;1048576&lt;/memory&gt;

	&nbsp; &nbsp; &lt;vcpu&gt;1&lt;/vcpu&gt;

	&nbsp; &nbsp; &lt;os&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;type
arch=&quot;x86_64&quot;
machine=&quot;pc&quot;&gt;hvm&lt;/type&gt; &nbsp;
&nbsp; &nbsp; &nbsp;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;boot
dev=&quot;hd&quot;/&gt;

	&nbsp; &nbsp; &lt;/os&gt;

	&nbsp; &nbsp; &lt;features&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;acpi/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;apic/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;pae/&gt;

	&nbsp; &nbsp; &lt;/features&gt;

	&nbsp; &nbsp; &lt;clock mode=&quot;localtime&quot;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;timer
name=&quot;rtc&quot;
tickpolicy=&quot;catchup&quot;
wallclock=&quot;guest&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;timer
name=&quot;hpet&quot;
present=&quot;no&quot;/&gt;

	&nbsp; &nbsp; &lt;/clock&gt;

	&nbsp; &nbsp; &lt;devices&gt;

	&nbsp; &nbsp; &nbsp; &nbsp;
&lt;!--&lt;emulator&gt;/usr/libexec/qemu-kvm&lt;/emulator&gt;--&gt;

	&nbsp; &nbsp; &nbsp; &nbsp;
&lt;emulator&gt;/usr/bin/qemu-system-x86_64&lt;/emulator&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;!--&lt;disk
device=&quot;disk&quot;
type=&quot;block&quot;&gt;--&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;disk
device=&quot;disk&quot;
type=&quot;file&quot;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;!--&lt;driver
cache=&quot;none&quot; name=&quot;qemu&quot;
type=&quot;qcow2&quot;/&gt;--&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;driver
cache=&quot;writeback&quot; io=&quot;threads&quot;
name=&quot;qemu&quot;
type=&quot;qcow2&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;source
file=&quot;/root/img/vmimg&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;target bus=&quot;virtio&quot;
dev=&quot;vda&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/disk&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;interface
type=&quot;network&quot;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;mac
address=&quot;d2:0d:45:a3:92:ea&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;source
network=&#39;ovs-network&#39;
portgroup=&#39;vlan-02&#39;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/interface&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;console
type=&quot;pty&quot;&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&lt;target
port=&quot;0&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;/console&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;input
bus=&quot;usb&quot;
type=&quot;tablet&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;input
bus=&quot;ps2&quot;
type=&quot;mouse&quot;/&gt;

	&nbsp; &nbsp; &nbsp; &nbsp; &lt;graphics
autoport=&quot;yes&quot;
keymap=&quot;en-us&quot; listen=&quot;0000&quot;

	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
port=&quot;-1&quot;
type=&quot;vnc&quot;/&gt;

	&nbsp; &nbsp; &lt;/devices&gt;

	&lt;/domain&gt;

	--------------------------------------------

	&nbsp;

	&nbsp;

	4 runned &#39;virsh start vm&#39;, and failed

	(messages had not been printed in english at my server, so i googled and
tried to choose simillar sentecne which were shown in libvirt related
threads please consider it)

	-----------------------------------------

	#virsh start vm

	error : Failled to start domain vm

	error : Unable to add port vnet0 to OVS bridge br0

	-----------------------------------------

	&nbsp;

	&nbsp;

	At that time, /var/log/libvirt/libvirtdlog&nbsp;

	(these are also translated)

	-----------------------------------------

	2013-05-23 04:32:14588+0000: 11455: error : virNetDevGetMTU:343 : Cannot
get interface MTU on &#39;ovsbr0&#39;: No such device&nbsp;

	2013-05-23 04:32:14678+0000: 11455: error : virExecWithHook:419 : Cannot
find &#39;ovs-vsctl&#39; in path: No such file or directory

	2013-05-23 04:32:14679+0000: 11455: error :
virNetDevOpenvswitchRemovePort:173 : Unable to delete port (null) from OVS:
command does not allowed

	-----------------------------------------

	&nbsp;

	&nbsp;

	I think above errors comes from install location of OVS as written in
libvirtdlog How can i solve that by hands? (I&#39;m also trying to solve the
problem by installing ovs, using rpm build) There are not only fedora or
ubuntu linux, so the solution may exist Are there a way to get libvirt to
recognize ovs-vsctl? (As i mentioned above, ovs-vsctl and ovs are properly
working)

	&nbsp;

	Thank you for reading

Eric Blake

2013-May-28 20:44 UTC

head link

Re: [libvirt-users] Using source installed open vswitch with libvirt(or virsh).

On 05/27/2013 03:22 AM, 황진환 wrote:> P{font-size:10pt; line-height:16; margin-left:0; margin-top:0;
> margin-right:0; margin-bottom:0; font-family:gulim;}
[Please fix your mailer to send plain-text.  This gobbledy-gook is
annoying to anyone with a plain-text mail client.]
> 	(English is not my first language Sorry for my poor English )
> 
> 	&nbsp;
> 
> 	OS :&nbsp;
> 
> 	Linux nc233 2632-220171el6x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012
x86_64
> x86_64 x86_64 GNU/Linux
It looks like all the '.' in your message disappeared, making it rather
illegible.
> 	virsh : 100
> 
> 	ibvirtd (libvirt) : 100
CentOS 6.3 did not ship with libvirt 1.0.0; have you self-built some
packages?  If that's the case, would you mind trying again with 1.0.5
(or even help us test our 1.0.6 release candidate)?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Laine Stump

2013-May-31 16:56 UTC

head link

Re: [libvirt-users] Using source installed open vswitch with libvirt(or virsh).

On 05/27/2013 05:22 AM, ??? wrote:>
>  
> At that time, /var/log/libvirt/libvirtd.log 
> (these are also translated)
> -----------------------------------------
> 2013-05-23 04:32:14.588+0000: 11455: error : virNetDevGetMTU:343 :
> Cannot get interface MTU on 'ovsbr0': No such device 
> 2013-05-23 04:32:14.678+0000: 11455: error : virExecWithHook:419 :
> Cannot find 'ovs-vsctl' in path: No such file or directory
> 2013-05-23 04:32:14.679+0000: 11455: error :
> virNetDevOpenvswitchRemovePort:173 : Unable to delete port (null) from
> OVS: command does not allowed.
> -----------------------------------------
>  
>  
> I think above errors comes from install location of OVS as written in
> libvirtd.log.

Correct. When you built and installed openvswitch, it apparently was
installed in some alternate place (/usr/local?) that isn't in the PATH
supplied to libvirtd when it starts.

The simplest solution would be to find ovs-vsctl, and make a symlink to
it from /usr/bin/ovs-vsctl.

BTW, since you're apparently already building upstream libvirt from
source, I'll repeat Eric's request to try libvirt-1.0.5 or the
libvirt-1.0.6-rc2 instead of 1.0.0; many things have been accomplished
in the last 6 months.

Possibly Parallel Threads

Search for more apparently analagous threads

libvirt users - May 2013 - Using source installed open vswitch with libvirt(or virsh).

[libvirt-users] Using source installed open vswitch with libvirt(or virsh).

Re: [libvirt-users] Using source installed open vswitch with libvirt(or virsh).

Re: [libvirt-users] Using source installed open vswitch with libvirt(or virsh).

Possibly Parallel Threads