{"action":"created","issue":{"url":"https://api.github.com/repos/coreemu/core/issues/172","repository_url":"https://api.github.com/repos/coreemu/core","labels_url":"https://api.github.com/repos/coreemu/core/issues/172/labels{/name}","comments_url":"https://api.github.com/repos/coreemu/core/issues/172/comments","events_url":"https://api.github.com/repos/coreemu/core/issues/172/events","html_url":"https://github.com/coreemu/core/issues/172","id":338627081,"node_id":"MDU6SXNzdWUzMzg2MjcwODE=","number":172,"title":"OVS mode and control network","user":{"login":"andreas-ibm","id":18004999,"node_id":"MDQ6VXNlcjE4MDA0OTk5","avatar_url":"https://avatars2.githubusercontent.com/u/18004999?v=4","gravatar_id":"","url":"https://api.github.com/users/andreas-ibm","html_url":"https://github.com/andreas-ibm","followers_url":"https://api.github.com/users/andreas-ibm/followers","following_url":"https://api.github.com/users/andreas-ibm/following{/other_user}","gists_url":"https://api.github.com/users/andreas-ibm/gists{/gist_id}","starred_url":"https://api.github.com/users/andreas-ibm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andreas-ibm/subscriptions","organizations_url":"https://api.github.com/users/andreas-ibm/orgs","repos_url":"https://api.github.com/users/andreas-ibm/repos","events_url":"https://api.github.com/users/andreas-ibm/events{/privacy}","received_events_url":"https://api.github.com/users/andreas-ibm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-07-05T15:39:18Z","updated_at":"2018-07-09T12:49:24Z","closed_at":null,"author_association":"NONE","body":"Started CORE in OVS mode and am having a little trouble with the control bridge.\r\nHere's the imn (cunningly disguised as a .txt):\r\n[small-ovs-external-ONOS.txt](https://github.com/coreemu/core/files/2167227/small-ovs-external-ONOS.txt)\r\nWhen I start it the control network is unattached, and these errors on the host if I query the vswitch:\r\n```\r\n     Bridge control\r\n        Port \"veth1.99.2e\"\r\n            Interface \"veth1.99.2e\"\r\n                error: \"could not open network device veth1.99.2e (No such device)\"\r\n        Port \"veth3.99.2e\"\r\n            Interface \"veth3.99.2e\"\r\n                error: \"could not open network device veth3.99.2e (No such device)\"\r\n        Port \"veth7.99.2e\"\r\n            Interface \"veth7.99.2e\"\r\n                error: \"could not open network device veth7.99.2e (No such device)\"\r\n        Port \"veth6.99.2e\"\r\n            Interface \"veth6.99.2e\"\r\n                error: \"could not open network device veth6.99.2e (No such device)\"\r\n        Port \"veth9.99.2e\"\r\n            Interface \"veth9.99.2e\"\r\n                error: \"could not open network device veth9.99.2e (No such device)\"\r\n        Port \"veth2.99.2e\"\r\n            Interface \"veth2.99.2e\"\r\n                error: \"could not open network device veth2.99.2e (No such device)\"\r\n        Port \"veth4.99.2e\"\r\n            Interface \"veth4.99.2e\"\r\n                error: \"could not open network device veth4.99.2e (No such device)\"\r\n        Port \"veth8.99.2e\"\r\n            Interface \"veth8.99.2e\"\r\n                error: \"could not open network device veth8.99.2e (No such device)\"\r\n        Port control\r\n            Interface control\r\n                type: internal\r\n        Port \"veth5.99.2e\"\r\n            Interface \"veth5.99.2e\"\r\n                error: \"could not open network device veth5.99.2e (No such device)\"\r\n```\r\nI can see there's a set of veth interfaces that aren't attached to ovs:\r\n```\r\n512: b.33918.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n517: b.7538.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n522: b.509.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n527: b.56698.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n532: b.25620.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n538: veth1.99.6@if537: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n540: veth2.99.6@if539: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n542: veth3.99.6@if541: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n544: veth4.99.6@if543: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n546: veth5.99.6@if545: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n291: b.ctrl0net.33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n548: veth6.99.6@if547: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n550: veth7.99.6@if549: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n552: veth8.99.6@if551: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n554: veth9.99.6@if553: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000\r\n444: control: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n446: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000\r\n492: b.61247.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n497: b.15611.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n502: b.52884.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n507: b.62954.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000\r\n```\r\nand if I add them:\r\n```bash\r\n$ovs-vsctl add-port control veth1.99.6\r\n$ovs-vsctl add-port control veth2.99.6\r\n$ovs-vsctl add-port control veth3.99.6\r\n$ovs-vsctl add-port control veth4.99.6\r\n$ovs-vsctl add-port control veth5.99.6\r\n$ovs-vsctl add-port control veth6.99.6\r\n$ovs-vsctl add-port control veth7.99.6\r\n$ovs-vsctl add-port control veth8.99.6\r\n$ovs-vsctl add-port control veth9.99.6\r\n```\r\nthen the guests can talk to the host again.\r\n\r\nI'll start digging into source, is there a particular place to look to fix this?"},"comment":{"url":"https://api.github.com/repos/coreemu/core/issues/comments/403467251","html_url":"https://github.com/coreemu/core/issues/172#issuecomment-403467251","issue_url":"https://api.github.com/repos/coreemu/core/issues/172","id":403467251,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMzQ2NzI1MQ==","user":{"login":"andreas-ibm","id":18004999,"node_id":"MDQ6VXNlcjE4MDA0OTk5","avatar_url":"https://avatars2.githubusercontent.com/u/18004999?v=4","gravatar_id":"","url":"https://api.github.com/users/andreas-ibm","html_url":"https://github.com/andreas-ibm","followers_url":"https://api.github.com/users/andreas-ibm/followers","following_url":"https://api.github.com/users/andreas-ibm/following{/other_user}","gists_url":"https://api.github.com/users/andreas-ibm/gists{/gist_id}","starred_url":"https://api.github.com/users/andreas-ibm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andreas-ibm/subscriptions","organizations_url":"https://api.github.com/users/andreas-ibm/orgs","repos_url":"https://api.github.com/users/andreas-ibm/repos","events_url":"https://api.github.com/users/andreas-ibm/events{/privacy}","received_events_url":"https://api.github.com/users/andreas-ibm/received_events","type":"User","site_admin":false},"created_at":"2018-07-09T12:49:24Z","updated_at":"2018-07-09T12:49:24Z","author_association":"NONE","body":"I *think* I see what you mean about the OVS service, the reason I'm using the OVS service still even though CORE is in OVS mode, is that it lets me customise the OVS config (in this case to use my currently experimental ONOS service).\r\n\r\nI *was* happy to use LinuxBridge for the remainder of my bridging needs, but due to LinuxBridge getting in a sulk and refusing to bridge anything apart from ARP I took the step to switch to OVS."}}
{"actor":{"display_login":"andreas-ibm"}}