New Question

Open vSwitch Extension is not running on any switch

asked 2016-06-22 16:46:10 +0200

JohnF gravatar image
PS C:\Users\Administrator> ovs-vsctl.exe add-br br-port3
ovs-vsctl:  Error detected while setting up 'br-port3'.  See ovs-vswitchd log for details.

From the ovs-vswitchd log:

2016-06-22T13:27:04.187Z|00030|wmi|WARN|Open vSwitch Extension is not running on any switch
2016-06-22T13:27:04.188Z|00031|wmi|WARN|Could not find HRESULT description for: 0.
2016-06-22T13:27:04.188Z|00032|dpif_netlink|ERR|Could not create wmi internal port with name:br-port3
2016-06-22T13:27:04.188Z|00033|bridge|INFO|bridge br-port3: using datapath ID 00009a9ef2a50240
2016-06-22T13:27:04.188Z|00034|connmgr|INFO|br-port3: added service controller "punix:C:\ProgramData\openvswitch\/br-port3.mgmt"

However, I do have the vSwitch configured with it:

PS C:\Users\Administrator> get-VMSwitchExtension -VMSwitchName vSwitch -Name "Open vSwitch Extension"

Id                  : 583CC151-73EC-4A6A-8B47-578297AD7623
Name                : Open vSwitch Extension
Vendor              : Open vSwitch
Version             :
ExtensionType       : Forwarding
ParentExtensionId   :
ParentExtensionName :
SwitchId            : 9224fc44-b9eb-49cf-b1f8-e5a6c57893e7
SwitchName          : vSwitch
Enabled             : True
Running             : True
ComputerName        : WIN-HQHVLTQ4OLK
Key                 :
IsDeleted           : False

So what am I doing incorrectly? I'm following the blog post from

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2016-06-22 17:02:09 +0200

aserdean gravatar image

updated 2016-07-14 04:18:03 +0200

Please stop the service ovs-vswitchd. Clear the log file and then start the service ovs-vswitchd again.

We have an issue during reboots that is addressed but not published under release yet.

UPDATE:Please try the installer it should fix the problem. We will update the stable installer soon.

Thanks, Alin.

edit flag offensive delete link more



Same issue after restarting the agent

JohnF gravatar imageJohnF ( 2016-06-22 17:06:36 +0200 )edit

I updated my previous answer. Could issue the above and try a reboot?

aserdean gravatar imageaserdean ( 2016-06-22 17:23:19 +0200 )edit

Set-Content : A positional parameter cannot be found that accepts argument 'start/strcustom/6066F867-7CA1-4418-85FD-36E3F9C0600C/VmmsWmiEventProvider'. At line:1 char:1 + sc triggerinfo ovs-vswitchd start/strcustom/6066F867-7CA1-4418-85FD-36E3F9C0600C ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JohnF gravatar imageJohnF ( 2016-06-22 18:04:04 +0200 )edit

+ CategoryInfo : InvalidArgument: (:) [Set-Content], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetContentCommand

JohnF gravatar imageJohnF ( 2016-06-22 18:04:15 +0200 )edit

Regular CMD call not from powershell.

aserdean gravatar imageaserdean ( 2016-06-22 18:45:24 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2016-06-22 16:46:10 +0200

Seen: 313 times

Last updated: Jul 14 '16