[prev in list] [next in list] [prev in thread] [next in thread]
List: openvswitch-discuss
Subject: [ovs-discuss] VM doesn't power on after open vswitch installation
From: jpettit () nicira ! com (Justin Pettit)
Date: 2010-02-18 5:23:23
Message-ID: 50DE42F9-2834-4D6A-99E3-A69A22BDE896 () nicira ! com
[Download RAW message or body]
Unfortunately, quite a few things have been conspiring against getting this release out--including a plane crash that knocked our power out all day today. Barring more unforeseen circumstances, I should be able to get the release out tomorrow.
I apologize for the delay.
--Justin
On Feb 16, 2010, at 1:22 AM, Justin Pettit wrote:
> Great! I'll work on getting a new release out tomorrow with the fixes.
>
> Thanks for working with us on this.
>
> --Justin
>
>
> On Feb 16, 2010, at 1:18 AM, devang.vyas at aol.in wrote:
>
>> Thanks a lot Justin.
>> vif script patch solved the issue.
>>
>> --DV
>>
>>
>> -----Original Message-----
>> From: Justin Pettit <jpettit at nicira.com>
>> To: devang.vyas at aol.in
>> Cc: discuss at openvswitch.org
>> Sent: Tue, 16 Feb 2010 1:35 pm
>> Subject: Re: [ovs-discuss] VM doesn't power on after open vswitch installation
>>
>> Having looked at logs you sent me offline, I suspect they were fixed in this
>> patch from our "next" branch:
>>
>>
>> http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=13ffee26f
>>
>>
>> I'm not able to get the patch ported and tested with the "master" branch
>> tonight. If you're feeling adventurous you can apply them to your live system.
>> Applying the "vif" script patch should be trivial and may even get your VMs
>> booting. If you're still having problems, you'd need to patch
>> "InterfaceReconfigureVswitch.py", which will require a bit of tweaking since it
>> uses new facilities from the "next" branch.
>>
>> Alternatively, you can wait for tomorrow, when I should have it patched and a
>> new tarball available. Sorry about the problem!
>>
>> --Justin
>>
>>
>> On Feb 15, 2010, at 11:26 PM,
>> devang.vyas at aol.in
>> wrote:
>>
>>>
>>> ouput for 'ps ax | grep ovs':
>>> 3240 ? S<s 0:00 /usr/sbin/ovs-vswitchd --pidfile=/var/run/ovs-vswitchd.pid
>> --detach --no-chdir --fake-proc-net -vANY:CONSOLE:EMER -vANY:SYSLOG:ERR
>> -vANY:FILE:INFO --log-file=/var/log/ovs-vswitchd.log /etc/ovs-vswitchd.conf
>>> 3243 ? S<s 0:00 /usr/sbin/ovs-brcompatd --no-chdir
>> --appctl-command=/usr/bin/ovs-appctl --target=/var/run/ovs-vswitchd.`cat
>> /var/run/ovs-vswitchd.pid`.ctl %s --pidfile=/var/run/ovs-brcompatd.pid --detach
>> -vANY:CONSOLE:EMER -vANY:SYSLOG:ERR -vANY:FILE:INFO --log-file=/var/log/ovs-brcompatd.log
>> /etc/ovs-vswitchd.conf
>>>
>>> tail /var/log/messages
>>>
>>> Feb 16 12:46:47 xen100 xapi: [ warn|xen100.xyz|399|Async.VM.start
>> R:a805d8c72b1a|xapi] vif QoS failed: parameter "kbps" not an integer
>> (vm=56956c26-da9a-8177-0c58-78df18c157ad,vif=4c23e89c-147f-e3b8-c2a2-6ea42ea5c080)
>>> Feb 16 12:46:47 xen100 scripts-vif: unknown interface type
>>> Feb 16 12:46:47 xen100 scripts-vif: unknown interface type
>>> Feb 16 12:47:31 xen100 xapi: [ info|xen100.xyz|391 inet-RPC|session.login_with_password
>> D:63509ec8fc87|xapi] Session.create trackid=90f6489ae1f36d9a2f9487f3dbf26848
>> pool=false uname=root is_local_superuser=true auth_user_sid=
>>> Feb 16 12:47:31 xen100 xapi: [ info|xen100.xyz|460 inet-RPC||taskhelper] task
>> Connection to VM console R:b0f1c61faf98 (uuid:def8378c-4443-7afd-225a-30a841d3b4f6)
>> created (trackid=90f6489ae1f36d9a2f9487f3dbf26848)
>>>
>>> Check attachment for ovs-vswitchd.log and ovs-brcompatd.log
>>>
>>> Thanks,
>>> DV
>>>
>>> -----Original Message-----
>>> From: Justin Pettit <
>> jpettit at nicira.com
>>>
>>> To:
>> devang.vyas at aol.in
>>
>>> Sent: Tue, 16 Feb 2010 12:26 pm
>>> Subject: Re: [ovs-discuss] VM doesn't power on after open vswitch installation
>>>
>>> Can you run "ps ax | grep ovs"? Would you be comfortable sending me
>>> "/var/log/messages" and "/var/log/ovs*"? My guess is that there's some
>>> integration issue and that if you used a build from the "next" repository that
>>
>>> you'd be okay. Unfortunately, it contains massive changes, and we're still
>>> working through integration issues and it's insufficiently documented.
>>>
>>> --Justin
>>>
>>>
>>> On Feb 15, 2010, at 10:50 PM,
>>>
>> devang.vyas at aol.in
>>
>>> wrote:
>>>
>>>> I am following steps given in INSTALL.XenServer file to build RPM and
>> install
>>> it on XenServer.
>>>>
>>>> Thanks,
>>>> DV
>>>>
>>>> -----Original Message-----
>>>> From: Justin Pettit <
>>>
>> jpettit at nicira.com
>>
>>>>
>>>> To:
>>>
>> devang.vyas at aol.in
>>
>>>
>>>> Cc:
>>>
>> discuss at openvswitch.org
>>
>>>
>>>> Sent: Mon, 15 Feb 2010 9:43 pm
>>>> Subject: Re: [ovs-discuss] VM doesn't power on after open vswitch
>> installation
>>>>
>>>> Can you answer the rest of the questions I asked? Are you generating your
>> own
>>>
>>>> RPM? If not, are you using the scripts in "xenserver"?
>>>>
>>>> Also, can you send us the contents of ovs-vswitchd.conf before and after you
>>
>>>> start the VM? Are you running bridge compatibility (ie, ovs-brcompatd and
>> the
>>>
>>>> bridge kernel module)?
>>>>
>>>> --Justin
>>>>
>>>>
>>>> On Feb 15, 2010, at 2:03 AM,
>>>>
>>>
>> devang.vyas at aol.in
>>
>>>
>>>> wrote:
>>>>
>>>>> Following is command line output.
>>>>>
>>>>> ifconfig -a >
>>>>> eth0 Link encap:Ethernet HWaddr 00:13:8F:A0:DA:6B
>>>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:1000
>>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>> Interrupt:20 Base address:0x6800
>>>>> eth1 Link encap:Ethernet HWaddr 00:05:5D:4A:C5:A7
>>>>> UP BROADCAST MULTICAST MTU:1500 Metric:1
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:1000
>>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>> Interrupt:20 Base address:0x4c00
>>>>> eth2 Link encap:Ethernet HWaddr 00:07:E9:0D:05:60
>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>> RX packets:20114 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:3153 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:411 txqueuelen:100
>>>>> RX bytes:9237394 (8.8 MiB) TX bytes:1743332 (1.6 MiB)
>>>>> lo Link encap:Local Loopback
>>>>> inet addr:127.0.0.1 Mask:255.0.0.0
>>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1
>>>>> RX packets:5853 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:5853 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:0
>>>>> RX bytes:2035111 (1.9 MiB) TX bytes:2035111 (1.9 MiB)
>>>>> vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
>>>>> BROADCAST MULTICAST MTU:1500 Metric:1
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:32
>>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>> xenbr0 Link encap:Ethernet HWaddr 00:13:8F:A0:DA:6B
>>>>> inet addr:192.168.4.100 Bcast:192.168.4.255 Mask:255.255.255.0
>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:0
>>>>> RX bytes:0 (0.0 b) TX bytes:252 (252.0 b)
>>>>> xenbr1 Link encap:Ethernet HWaddr 00:05:5D:4A:C5:A7
>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:0
>>>>> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>>>>> xenbr2 Link encap:Ethernet HWaddr 00:07:E9:0D:05:60
>>>>> inet addr:192.168.4.100 Bcast:192.168.4.255 Mask:255.255.255.0
>>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>> RX packets:5182 errors:0 dropped:0 overruns:0 frame:0
>>>>> TX packets:3155 errors:0 dropped:0 overruns:0 carrier:0
>>>>> collisions:0 txqueuelen:0
>>>>> RX bytes:928402 (906.6 KiB) TX bytes:1743416 (1.6 MiB)
>>>>> ==============
>>>>> xe pif-list >
>>>>> uuid ( RO) : 63e9a8e9-78c4-4c33-ab3a-a027e5144f9c
>>>>> device ( RO): eth1
>>>>> MAC ( RO): 00:05:5d:4a:c5:a7
>>>>> physical ( RO): true
>>>>> currently-attached ( RO): true
>>>>> MTU ( RO): 1500
>>>>> VLAN ( RO): -1
>>>>> bond-master-of ( RO):
>>>>> bond-slave-of ( RO): <not in database>
>>>>> management ( RO): false
>>>>> network-uuid ( RO): a33c04b1-75a7-c1c2-65e5-67e6c7f121af
>>>>> network-name-label ( RO): Pool-wide network associated with eth1
>>>>> host-uuid ( RO): 1f234100-744e-4981-a9da-56ae6ce1709e
>>>>> host-name-label ( RO): samxen100.itpl
>>>>> IP-configuration-mode ( RO): None
>>>>> IP ( RO):
>>>>> netmask ( RO):
>>>>> gateway ( RO):
>>>>> DNS ( RO):
>>>>> io_read_kbs ( RO): <expensive field>
>>>>> io_write_kbs ( RO): <expensive field>
>>>>> carrier ( RO): false
>>>>> vendor-id ( RO): 1186
>>>>> vendor-name ( RO): D-Link System Inc
>>>>> device-id ( RO): 1300
>>>>> device-name ( RO): RTL8139 Ethernet
>>>>> speed ( RO): 10 Mbit/s
>>>>> duplex ( RO): half
>>>>> disallow-unplug ( RW): false
>>>>> pci-bus-path ( RO): 0000:01:01.0
>>>>> other-config (MRW):
>>>>>
>>>>> uuid ( RO) : e752c086-8ade-5c2c-922e-21ba227682f9
>>>>> device ( RO): eth2
>>>>> MAC ( RO): 00:07:e9:0d:05:60
>>>>> physical ( RO): true
>>>>> currently-attached ( RO): true
>>>>> MTU ( RO): 1500
>>>>> VLAN ( RO): -1
>>>>> bond-master-of ( RO):
>>>>> bond-slave-of ( RO): <not in database>
>>>>> management ( RO): true
>>>>> network-uuid ( RO): 1fb375c1-c95b-c135-5238-c4098ac44a9e
>>>>> network-name-label ( RO): Pool-wide network associated with eth2
>>>>> host-uuid ( RO): 1f234100-744e-4981-a9da-56ae6ce1709e
>>>>> host-name-label ( RO): samxen100.itpl
>>>>> IP-configuration-mode ( RO): Static
>>>>> IP ( RO): 192.168.4.100
>>>>> netmask ( RO): 255.255.255.0
>>>>> gateway ( RO): 192.168.4.1
>>>>> DNS ( RO): 192.168.4.1
>>>>> io_read_kbs ( RO): <expensive field>
>>>>> io_write_kbs ( RO): <expensive field>
>>>>> carrier ( RO): true
>>>>> vendor-id ( RO): 8086
>>>>> vendor-name ( RO): Intel Corporation
>>>>> device-id ( RO): 100e
>>>>> device-name ( RO): 82540EM Gigabit Ethernet Controller
>>>>> speed ( RO): 100 Mbit/s
>>>>> duplex ( RO): half
>>>>> disallow-unplug ( RW): false
>>>>> pci-bus-path ( RO): 0000:01:02.0
>>>>> other-config (MRW):
>>>>>
>>>>> uuid ( RO) : 743760d4-5ee1-0760-a959-faca841f1bab
>>>>> device ( RO): eth0
>>>>> MAC ( RO): 00:13:8f:a0:da:6b
>>>>> physical ( RO): true
>>>>> currently-attached ( RO): true
>>>>> MTU ( RO): 1500
>>>>> VLAN ( RO): -1
>>>>> bond-master-of ( RO):
>>>>> bond-slave-of ( RO): <not in database>
>>>>> management ( RO): false
>>>>> network-uuid ( RO): 09edc29d-3b40-0906-5fac-f47032583cce
>>>>> network-name-label ( RO): Pool-wide network associated with eth0
>>>>> host-uuid ( RO): 1f234100-744e-4981-a9da-56ae6ce1709e
>>>>> host-name-label ( RO): samxen100.itpl
>>>>> IP-configuration-mode ( RO): Static
>>>>> IP ( RO): 192.168.4.100
>>>>> netmask ( RO): 255.255.255.0
>>>>> gateway ( RO): 192.168.4.1
>>>>> DNS ( RO): 192.168.4.1
>>>>> io_read_kbs ( RO): <expensive field>
>>>>> io_write_kbs ( RO): <expensive field>
>>>>> carrier ( RO): false
>>>>> vendor-id ( RO): 10ec
>>>>> vendor-name ( RO): Realtek Semiconductor Co., Ltd.
>>>>> device-id ( RO): 8139
>>>>> device-name ( RO): RTL-8139/8139C/8139C+
>>>>> speed ( RO): 10 Mbit/s
>>>>> duplex ( RO): half
>>>>> disallow-unplug ( RW): false
>>>>> pci-bus-path ( RO): 0000:01:05.0
>>>>> other-config (MRW): domain: itpl
>>>>>
>>>>> ==============
>>>>> xe network-list >
>>>>> uuid ( RO) : a33c04b1-75a7-c1c2-65e5-67e6c7f121af
>>>>> name-label ( RW): Pool-wide network associated with eth1
>>>>> name-description ( RW):
>>>>> VIF-uuids (SRO):
>>>>> PIF-uuids (SRO): 63e9a8e9-78c4-4c33-ab3a-a027e5144f9c
>>>>> bridge ( RO): xenbr1
>>>>> other-config (MRW): automatic: false
>>>>> blobs ( RO):
>>>>>
>>>>> uuid ( RO) : 1fb375c1-c95b-c135-5238-c4098ac44a9e
>>>>> name-label ( RW): Pool-wide network associated with eth2
>>>>> name-description ( RW):
>>>>> VIF-uuids (SRO): 4c23e89c-147f-e3b8-c2a2-6ea42ea5c080
>>>>> PIF-uuids (SRO): e752c086-8ade-5c2c-922e-21ba227682f9
>>>>> bridge ( RO): xenbr2
>>>>> other-config (MRW): automatic: false
>>>>> blobs ( RO):
>>>>>
>>>>> uuid ( RO) : 09edc29d-3b40-0906-5fac-f47032583cce
>>>>> name-label ( RW): Pool-wide network associated with eth0
>>>>> name-description ( RW):
>>>>> VIF-uuids (SRO):
>>>>> PIF-uuids (SRO): 743760d4-5ee1-0760-a959-faca841f1bab
>>>>> bridge ( RO): xenbr0
>>>>> other-config (MRW): automatic: false
>>>>> blobs ( RO):
>>>>>
>>>>> uuid ( RO) : 898cda3b-22c9-8c94-36ea-509bc3299b52
>>>>> name-label ( RW): Guest installer network
>>>>> name-description ( RW): Network on which guests will get assigned a
>>>> private local IP address
>>>>> VIF-uuids (SRO): e95ffc70-0432-89ee-4c80-7b38a01dce2c
>>>>> PIF-uuids (SRO):
>>>>> bridge ( RO): xapi0
>>>>> other-config (MRW): is_guest_installer_network: true; ip_begin:
>>>> 192.168.128.1; ip_end: 192.168.128.254; netmask: 255.255.255.0
>>>>> blobs ( RO):
>>>>>
>>>>> ==============
>>>>> xe vif-list >
>>>>> uuid ( RO) : e95ffc70-0432-89ee-4c80-7b38a01dce2c
>>>>> vm-uuid ( RO): 69641b3c-82e4-ee8f-5f54-8f651e5fc0d8
>>>>> vm-name-label ( RO): XenSource P2V Server
>>>>> allowed-operations (SRO): attach
>>>>> current-operations (SRO):
>>>>> device ( RO): 0
>>>>> MAC ( RO): ea:30:af:39:be:6d
>>>>> MAC-autogenerated ( RO): false
>>>>> MTU ( RO): 1500
>>>>> currently-attached ( RO): false
>>>>> qos_algorithm_type ( RW):
>>>>> qos_algorithm_params (MRW):
>>>>> qos_supported_algorithms (SRO):
>>>>> other-config (MRW):
>>>>> network-uuid ( RO): 898cda3b-22c9-8c94-36ea-509bc3299b52
>>>>> network-name-label ( RO): Guest installer network
>>>>> io_read_kbs ( RO): <expensive field>
>>>>> io_write_kbs ( RO): <expensive field>
>>>>>
>>>>> uuid ( RO) : 4c23e89c-147f-e3b8-c2a2-6ea42ea5c080
>>>>> vm-uuid ( RO): 56956c26-da9a-8177-0c58-78df18c157ad
>>>>> vm-name-label ( RO): XenServer DDK 5.5.0-25727p
>>>>> allowed-operations (SRO):
>>>>> current-operations (SRO): attach
>>>>> device ( RO): 0
>>>>> MAC ( RO): b6:4a:4f:46:d4:36
>>>>> MAC-autogenerated ( RO): true
>>>>> MTU ( RO): 0
>>>>> currently-attached ( RO): false
>>>>> qos_algorithm_type ( RW): ratelimit
>>>>> qos_algorithm_params (MRW): kbps:
>>>>> qos_supported_algorithms (SRO):
>>>>> other-config (MRW):
>>>>> network-uuid ( RO): 1fb375c1-c95b-c135-5238-c4098ac44a9e
>>>>> network-name-label ( RO): Pool-wide network associated with eth2
>>>>> io_read_kbs ( RO): <expensive field>
>>>>> io_write_kbs ( RO): <expensive field>
>>>>>
>>>>> ==============
>>>>>
>>>>> Thanks,
>>>>> DV
>>>>> -----Original Message-----
>>>>> From: Justin Pettit <
>>>>
>>>
>> jpettit at nicira.com
>>
>>>
>>>>>
>>>>> To:
>>>>
>>>
>> devang.vyas at aol.in
>>
>>>
>>>>
>>>>> Cc:
>>>>
>>>
>> discuss at openvswitch.org
>>
>>>
>>>>
>>>>> Sent: Mon, 15 Feb 2010 1:32 pm
>>>>> Subject: Re: [ovs-discuss] VM doesn't power on after open vswitch
>>> installation
>>>>>
>>>>> I've not seen that error before, and we run that version of XenServer
>>>>> internally. Doing a Google search for that error message (minus the
>>> "CentOS"
>>>>> parts) brought up a couple of suggestions of places to look. You may just
>>
>>>> want
>>>>> to do a quick sanity-check of those suggestions first. If that doesn't
>> get
>>>> you
>>>>> anywhere, can you run the following commands and post the results?
>>>>>
>>>>> xe pif-list params=all
>>>>> xe network-list params=all
>>>>> xe vif-list params=all
>>>>> ifconfig -a
>>>>>
>>>>> Are you using the spec file in the "xenserver" directory to build your own
>>
>>>> RPM?
>>>>> If not, are you still using the scripts located in that directory?
>>>>>
>>>>> --Justin
>>>>>
>>>>>
>>>>> On Feb 14, 2010, at 11:37 PM,
>>>>>
>>>>
>>>
>> devang.vyas at aol.in
>>
>>>
>>>>
>>>>> wrote:
>>>>>
>>>>>> After removing vswitch VM does come up properly.
>>>>>> Xen kernel version is 2.6.18-128.1.6.el5.xs5.5.0.505.1024xen.
>>>>>> Guest OS is Cent OS 5.0.
>>>>>>
>>>>>> Related to this issue
>>>>>> With Open vSwitch running on Xen Server, If I try to create new VM with
>>>> single
>>>>> interface, Add VM failed with following error.
>>>>>> Error: Creating 'CentOS 5.3 ' by cloning 'CentOS 5.3' - This VM cannot
>> be
>>>>> started, as its network interfaces could not be connected. One of the
>> NICs
>>> is
>>>>
>>>>> in use elsewhere.
>>>>>>
>>>>>> Thanks,
>>>>>> DV
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Justin Pettit <
>>>>>
>>>>
>>>
>> jpettit at nicira.com
>>
>>>
>>>>
>>>>>>
>>>>>> To:
>>>>>
>>>>
>>>
>> devang.vyas at aol.in
>>
>>>
>>>>
>>>>>
>>>>>> Cc:
>>>>>
>>>>
>>>
>> discuss at openvswitch.org
>>
>>>
>>>>
>>>>>
>>>>>> Sent: Mon, 15 Feb 2010 12:25 pm
>>>>>> Subject: Re: [ovs-discuss] VM doesn't power on after open vswitch
>>>> installation
>>>>>>
>>>>>> I've never seen anything like that. If you remove Open vSwitch, does it
>>
>>>> work
>>>>>> again?
>>>>>>
>>>>>> What hypervisor are you using? What guest OS are you using?
>>>>>>
>>>>>> --Justin
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Feb 14, 2010, at 10:50 PM,
>>>>>>
>>>>>
>>>>
>>>
>> devang.vyas at aol.in
>>
>>>
>>>>
>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have installed open vswitch version 0.99.1.
>>>>>>> After post installation reboot, VMs having network interface doesn't
>>> come
>>>> up
>>>>>
>>>>>> (power on). Once I delete VM network interface, it comes up
>> successfully.
>>>>>>> Is this issue related to open vswitch or am I missing any
>> configuration
>>>
>>>> for
>>>>>
>>>>>> VM before open vswitch installation.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> DV
>>>>>>> _______________________________________________
>>>>>>> discuss mailing list
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> discuss at openvswitch.org
>>
>>>
>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>>
>>> <ovs-vswitchd.log><ovs-brcompatd.log>
>>
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic