New Question

roli's profile - activity

2017-11-02 19:31:04 +0300 received badge  Famous Question (source)
2017-07-07 04:27:19 +0300 received badge  Taxonomist
2017-06-09 13:25:13 +0300 received badge  Self-Learner (source)
2017-06-09 13:25:13 +0300 received badge  Teacher (source)
2017-05-29 14:02:28 +0300 received badge  Famous Question (source)
2017-05-03 20:04:01 +0300 received badge  Notable Question (source)
2017-04-13 13:10:23 +0300 received badge  Notable Question (source)
2017-04-07 14:00:33 +0300 received badge  Popular Question (source)
2017-03-29 14:10:27 +0300 received badge  Popular Question (source)
2017-03-29 14:10:27 +0300 received badge  Notable Question (source)
2017-03-20 16:14:56 +0300 answered a question Any experience from Hyper-V and Ocata?

Great! Let me know if we can help out with testing.

2017-03-20 16:00:25 +0300 asked a question Any experience from Hyper-V and Ocata?

Hello, Have anybody had the chance to get any experience of Hyper-V together with Ocata yet (Nova, Neutron-Ovs-Agent, Cinder)? Are there any pitfalls to be aware of? Will the Newton-versions of Cloudbase binary components work or would we be better off trying to compile components from scratch based on what's available on ?

Best regards Roger

2017-03-20 14:57:01 +0300 received badge  Famous Question (source)
2017-03-06 19:04:30 +0300 commented question VXLAN port not open in Hyper-V

It currently looks like this

2017-03-06 13:30:35 +0300 commented question VXLAN port not open in Hyper-V

Do you know why the neutron-ovs-agent does not add the "normal" flow automatically? Is it possible to configure something to make it do so? Each time the ovs-vswitchd service is restarted I currently have to add it again manually...

2017-03-06 13:28:58 +0300 commented question VXLAN port not open in Hyper-V

Thanks! When enabling the br-ex virtual interface in Windows and setting the VXLAN IP on that interface it works after recabling the interface physically to the "tunnel switch" and also adding the normal flow via `ovs-ofctl add-flow br-ex actions=normal`.

2017-03-06 13:28:58 +0300 received badge  Commentator
2017-03-02 16:07:53 +0300 received badge  Notable Question (source)
2017-02-28 19:09:07 +0300 commented question VXLAN port not open in Hyper-V

OK, hope that is the problem. I will try to change it when I'm on site on monday and let you know.

2017-02-28 11:35:33 +0300 commented question VXLAN port not open in Hyper-V

As you will see I try to use my Management interface ( as the source of my VXLAN-tunnels. That's the way our working Linux-computes are set up. The Management interface is not the interface that is VMswitch enabled and connected to br-ex (the VMswitch enabled interface is Tenant).

2017-02-28 11:29:51 +0300 commented question VXLAN port not open in Hyper-V

and flows after the flow was added for br-ex The Hyper-V VM now runs on internal IP (external and MAC FA:16:3E:54:CC:E7.

2017-02-28 11:22:10 +0300 commented question VXLAN port not open in Hyper-V
2017-02-27 19:51:15 +0300 commented question VXLAN port not open in Hyper-V

The Hyper-V host is new and has not been working in the OpenStack environment earlier. It's the first time we try to get HyperV into the system so we probably has made some basic mistake setting it up.

2017-02-27 19:46:50 +0300 commented question VXLAN port not open in Hyper-V

The Linux hypervisors work well with the controllers, instances launched on them can be reached from other VMs and from outside without any problems. Do you know why I get ICMP port unreachable messages from the HyperV host for all incoming VXLAN traffic?

2017-02-27 19:42:56 +0300 received badge  Popular Question (source)
2017-02-27 19:42:56 +0300 received badge  Enthusiast
2017-02-26 19:00:44 +0300 commented question VXLAN port not open in Hyper-V

I also tried adding the normal flow to br-ex. I no longer get any drops there. I will try to redo the installation according to the url provided, when I'm back in office and let you know the results.

2017-02-26 18:59:01 +0300 commented question VXLAN port not open in Hyper-V

Thanks for your quick response. I tried removing vxlan_group = and bridge_mappings = physnet1:br-ex. But still it will not open a UDP/4789 listening port for VXLAN. I suppose that will be needed?! Any idea what could be the cause of this?

2017-02-26 18:40:24 +0300 received badge  Popular Question (source)
2017-02-26 11:42:31 +0300 received badge  Editor (source)
2017-02-24 15:17:26 +0300 asked a question VXLAN port not open in Hyper-V


I'm trying to get instances in a Windows Server 2016 Datacenter based Hyper-V compute node to communicate with instances on other hypervisors using Open vSwitch and neutron-ovs-agent over VXLAN. My other hypervisors run CentOS/KVM. Instances on the Linux machines can communicate just fine, but I don't get the ones running in Hyper-V to communicate with the world outside the hypervisor.

The setup runs two controller nodes ( and with a shared VIP with the L3-agent running the router on .21. In addition I have two separate hypervisors installed, one KVM ( and one Hyper-V (

The Hyper-V host runs 3 VMs, one CirrOS ( and two Windows Server (one with and one trying to use DHCP).

I have created a Hyper-V VMswitch named "external" and enabled the Open vSwitch extension. The VMswitch is connected to a physical interface named "Tenant" (without IP). I have also manually created a Open vSwitch bridge named "br-ex" and connected the "Tenant" port above to it. The hypervisor also has a Management interface with IP (i.e. with connectivity to the other Openstack nodes, this is the interface that should be used for the VXLAN traffic.

The VMs on Hyper-V can ping themselves and other VMs on the same Hyper-V host. They can not access the router, DHCP-server on the controller node or VMs on other hypervisors.

I think the problem has something to do with that Open vSwitch does not open a listening socket for VXLAN (udp/4789), i.e. according to netstat -na | find "4789". I also can see outgoing flood traffic from br-tun to each VXLAN port according to ovs-ofctl dump-flows br-tun but I don't see this traffic in wireshark or at the incoming br-tun VXLAN port on the other hypervisors, my guess is that this is outgoing ARP requests that for some reason are not sent out on the physical interface.

If I try to connect to an instance on the Hyper-V host from the outside ( I see the incoming TCP SYN on the Hyper-V host (but not on the VM).

Frame 1195965: 128 bytes on wire (1024 bits), 128 bytes captured (1024 bits) on interface 0
Ethernet II, Src: HewlettP_70:57:80 (ac:16:2d:70:57:80), Dst: HewlettP_70:a9:d0 (ac:16:2d:70:a9:d0)
Internet Protocol Version 4, Src:, Dst:
User Datagram Protocol, Src Port: 44982, Dst Port: 4789
Virtual eXtensible Local Area Network
Ethernet II, Src: fa:16:3e:e2:06:b1 (fa:16:3e:e2:06:b1), Dst: fa:16:3e:9e:f7:c6 (fa:16:3e:9e:f7:c6)
Internet Protocol Version 4, Src:, Dst:
Transmission Control Protocol, Src Port: 53839, Dst Port: 22, Seq: 0, Len: 0

I.e ... (more)

2017-02-23 20:58:29 +0300 commented answer Invalid image format 'vhdx'

Thank you so much! That was easy when you knew it. Works just fine when you use openstack image create --file Windows-Server-2016-Standard.vhdx --container-format bare --disk-format vhd --public Windows-Server-2016-Standard-vhdx_as_vhd

2017-02-23 18:36:56 +0300 asked a question Invalid image format 'vhdx'

Hi, I'm trying to get Nova on Hyper-V to work with vhdx Glance images. The images works well when started on Linux KVM, but on Hyper-V I get the following error in nova.log.

2017-02-21 16:38:18.236 7124 ERROR nova.compute.manager [instance: ca6e66e5-aba3-43c9-8150-9beca16e0d91] nova.exception.InvalidImageFormat: Invalid image format 'vhdx'

I can boot other images in VHD format fine on the same hypervisor. We run Newton release (via Kolla) and use the nova Windows components from Any idea what could be the cause of this? As far as I understand it vhdx should be supported.

My nova.conf looks like this:

mkisofs_cmd=C:\Program Files\Cloudbase Solutions\OpenStack\Nova\bin\mkisofs.exe
debug = False
transport_url = rabbit://openstack:password@,openstack:password@

policy_file=C:\Program Files\Cloudbase Solutions\OpenStack\Nova\etc\policy.json


debug = False

qemu_img_cmd=C:\Program Files\Cloudbase Solutions\OpenStack\Nova\bin\qemu-img.exe


url =

username = neutron
password = password
auth_url =
2017-01-24 19:10:29 +0300 asked a question Open vSwitch on Nanoserver

Do you have any binary packaging of Open vSwitch (preferably 2.6.1) that can be installed on Nanoserver as a compute host, i.e. with Hyper-V? In other words something like your zipped binaries for Nova, Cinder etc.

If not, would it be possible to take the binaries from another Windows installation where your MSI has been installed and move them to the Nanoserver. If so what other steps would be required rather than register the two services for ovsdb and ovswitchd? For example how do I register the Hyper-V Virtual Switch Extension so that it becomes possible to enable?