Revision history [back]

Hello,

It would help a lot if logs were also included, specifically the C:\OpenStack\Logs\nova-compute.log and C:\OpenStack\Logs\neutron-hyperv-agent.log files, as too little information is given by just the horizon error message.

Keep in mind that Hyper-V doesn't support VXLAN networks. Are your networks using VXLAN by any chance?

My other guess is that the instance failed to spawn because the neutron port couldn't be bound to the Hyper-V host. This happens if you didn't configure your Neutron controller to also use the Hyper-V ML2 mechanism driver.

For this, you will have to edit the file /etc/neutron/plugins/ml2/ml2_conf.ini and have the configuration option in the [ml2] section:

mechanism_drivers = openvswitch,hyperv

Any other mechanism drivers can be added to that list, but it is important that those 2 are there. After the file was edited, the neutron-server service will have to be restarted. Then, you can try spawning a new instance.

Best regards,

Claudiu Belu

Hello,

It would help a lot if logs were also included, specifically the C:\OpenStack\Logs\nova-compute.log and C:\OpenStack\Logs\neutron-hyperv-agent.log files, as too little information is given by just the horizon error message.

Keep in mind that Neutron Hyper-V Agent doesn't support VXLAN networks. Are your networks using VXLAN by any chance?chance? If you do have VXLAN networks and desire to use them, you should use Windows OVS + neutron-ovs-agent. https://cloudbase.it/openvswitch/

My other guess is that the instance failed to spawn because the neutron port couldn't be bound to the Hyper-V host. This happens if you didn't configure your Neutron controller to also use the Hyper-V ML2 mechanism driver.

For this, you will have to edit the file /etc/neutron/plugins/ml2/ml2_conf.ini and have the configuration option in the [ml2] section:

mechanism_drivers = openvswitch,hyperv

Any other mechanism drivers can be added to that list, but it is important that those 2 are there. After the file was edited, the neutron-server service will have to be restarted. Then, you can try spawning a new instance.

Best regards,

Claudiu Belu