centos7.1 上部署kilo， nova问题
在centos7.1上部署kilo，将所有的部件部署在了一台VMWare上， 启动VM失败。1、nova serivce-list 正常
2、neutron agent-list 正常
3、 /etc/var/nova/nova-compute.log 中，报如下错误：
2015-09-28 16:11:41.185 3522 ERROR nova.compute.manager Instance failed to spawn
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager Traceback (most recent call last):
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2442, in _build_resources
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager yield resources
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2314, in _build_and_run_instance
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager block_device_info=block_device_info)
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2351, in spawn
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager write_to_disk=True)
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4172, in _get_guest_xml
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager context)
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4043, in _get_guest_config
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager flavor, virt_type)
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 374, in get_config
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager _("Unexpected vif_type=%s") % vif_type)
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager NovaException: Unexpected vif_type=binding_failed
2015-09-28 16:11:41.185 3522 TRACE nova.compute.manager
4、通过nova host-describe 查看主机资源，也是充足的。
5、上网查了很多，给出的是ovs的问题。但无法解决。
请各位有知道的指点，谢谢！
从日志看虚拟网卡有问题。绑定失败了。类型是kvm,还是quem,这个是否配置正确 hyj 发表于 2015-9-28 17:47
从日志看虚拟网卡有问题。绑定失败了。类型是kvm,还是quem,这个是否配置正确
在/etc/nova/nova.conf中，virt_type配置kvm和quem都尝试过，报同样的问题。
系统级别的错误，不懂 hyj 发表于 2015-9-28 17:47
从日志看虚拟网卡有问题。绑定失败了。类型是kvm,还是quem,这个是否配置正确
在neutron日志文件/etc/neutron/server.log中，报出如下错误：
015-09-29 11:07:16.243 1214 INFO neutron.wsgi 192.168.50.131 - - "GET /v2.0/networks.json?id=891e0735-5f5e-4554-8598-d6201c6cbf80 HTTP/1.1" 200 590 0.041949
2015-09-29 11:07:16.338 1214 INFO neutron.callbacks.manager Notify callbacks for port, after_create
2015-09-29 11:07:16.339 1214 INFO neutron.callbacks.manager Calling callback neutron.db.l3_dvrscheduler_db._notify_l3_agent_new_port
2015-09-29 11:07:16.348 1214 ERROR neutron.plugins.ml2.managers Failed to bind port 688f42e0-c49d-475f-a516-04599f890983 on host kcompute
2015-09-29 11:07:16.348 1214 ERROR neutron.plugins.ml2.managers Failed to bind port 688f42e0-c49d-475f-a516-04599f890983 on host kcompute
2015-09-29 11:07:16.402 1214 INFO neutron.wsgi 192.168.50.131 - - "POST /v2.0/ports.json HTTP/1.1" 201 826 0.155425
2015-09-29 11:07:16.428 1214 INFO neutron.wsgi 192.168.50.131 - - "GET /v2.0/ports.json?tenant_id=d5f6e351c34243e4b41488875f07381c&device_id=57703869-3225-41ad-804c-d3226524fa3d HTTP/1.1" 200 824 0.023265
2015-09-29 11:07:16.436 1214 INFO neutron.wsgi 192.168.50.131 - - "GET /v2.0/floatingips.json?fixed_ip_address=192.168.0.29&port_id=688f42e0-c49d-475f-a516-04599f890983 HTTP/1.1" 200 232 0.004732
2015-09-29 11:07:16.449 1214 INFO neutron.wsgi 192.168.50.131 - - "GET /v2.0/subnets.json?id=c31c255e-df1f-43ca-a5a8-48c75ec995bd HTTP/1.1" 200 677 0.010278
2015-09-29 11:07:16.470 1214 INFO neutron.wsgi 192.168.50.131 - - "GET /v2.0/ports.json?network_id=891e0735-5f5e-4554-8598-d6201c6cbf80&device_owner=network%3Adhcp HTTP/1.1" 200 865 0.018702
2015-09-29 11:07:21.174 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?tenant_id=d5f6e351c34243e4b41488875f07381c&device_id=d16d4ed0-a833-444c-933b-885268446e17 HTTP/1.1" 200 824 0.018904
2015-09-29 11:07:21.197 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/networks.json?id=891e0735-5f5e-4554-8598-d6201c6cbf80 HTTP/1.1" 200 590 0.020040
2015-09-29 11:07:21.204 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/floatingips.json?fixed_ip_address=192.168.0.27&port_id=890baf7c-fd71-4be1-946d-6819c81def94 HTTP/1.1" 200 232 0.004612
2015-09-29 11:07:21.216 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/subnets.json?id=c31c255e-df1f-43ca-a5a8-48c75ec995bd HTTP/1.1" 200 677 0.009715
2015-09-29 11:07:21.240 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?network_id=891e0735-5f5e-4554-8598-d6201c6cbf80&device_owner=network%3Adhcp HTTP/1.1" 200 865 0.021287
2015-09-29 11:07:22.811 1214 INFO neutron.wsgi [-] (1214) accepted ('192.168.50.131', 50202)
2015-09-29 11:07:22.813 1214 INFO neutron.wsgi [-] 192.168.50.131 - - "GET /v2.0/extensions.json HTTP/1.1" 200 4333 0.001204
2015-09-29 11:07:27.727 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?tenant_id=d5f6e351c34243e4b41488875f07381c&device_id=57703869-3225-41ad-804c-d3226524fa3d HTTP/1.1" 200 824 0.018543
2015-09-29 11:07:27.792 1214 INFO neutron.callbacks.manager Notify callbacks for port, after_update
2015-09-29 11:07:27.792 1214 INFO neutron.callbacks.manager Calling callback neutron.db.l3_dvrscheduler_db._notify_l3_agent_new_port
2015-09-29 11:07:27.812 1214 ERROR neutron.plugins.ml2.managers Failed to bind port 688f42e0-c49d-475f-a516-04599f890983 on host knetwork
2015-09-29 11:07:27.812 1214 ERROR neutron.plugins.ml2.managers Failed to bind port 688f42e0-c49d-475f-a516-04599f890983 on host knetwork
2015-09-29 11:07:27.820 1214 WARNING neutron.plugins.ml2.plugin In _notify_port_updated(), no bound segment for port 688f42e0-c49d-475f-a516-04599f890983 on network 891e0735-5f5e-4554-8598-d6201c6cbf80
2015-09-29 11:07:27.851 1214 INFO neutron.wsgi 192.168.50.132 - - "PUT /v2.0/ports/688f42e0-c49d-475f-a516-04599f890983.json HTTP/1.1" 200 821 0.121511
2015-09-29 11:07:27.873 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?tenant_id=d5f6e351c34243e4b41488875f07381c&device_id=57703869-3225-41ad-804c-d3226524fa3d HTTP/1.1" 200 824 0.018922
2015-09-29 11:07:27.894 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/networks.json?id=891e0735-5f5e-4554-8598-d6201c6cbf80 HTTP/1.1" 200 590 0.017866
2015-09-29 11:07:27.901 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/floatingips.json?fixed_ip_address=192.168.0.29&port_id=688f42e0-c49d-475f-a516-04599f890983 HTTP/1.1" 200 232 0.004397
2015-09-29 11:07:27.913 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/subnets.json?id=c31c255e-df1f-43ca-a5a8-48c75ec995bd HTTP/1.1" 200 677 0.009490
2015-09-29 11:07:27.933 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?network_id=891e0735-5f5e-4554-8598-d6201c6cbf80&device_owner=network%3Adhcp HTTP/1.1" 200 865 0.017569
2015-09-29 11:07:33.142 1214 INFO neutron.wsgi [-] (1214) accepted ('192.168.50.131', 50224)
2015-09-29 11:07:33.144 1214 INFO neutron.wsgi [-] 192.168.50.131 - - "GET /v2.0/extensions.json HTTP/1.1" 200 4333 0.001156
2015-09-29 11:07:45.885 1214 INFO neutron.wsgi [-] (1214) accepted ('192.168.50.131', 50255)
2015-09-29 11:07:45.886 1214 INFO neutron.wsgi [-] 192.168.50.131 - - "GET /v2.0/extensions.json HTTP/1.1" 200 4333 0.001099
2015-09-29 11:08:22.197 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?tenant_id=d5f6e351c34243e4b41488875f07381c&device_id=11511cc3-fcef-4a47-b4b7-060c821dd265 HTTP/1.1" 200 824 0.020235
2015-09-29 11:08:22.222 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/networks.json?id=891e0735-5f5e-4554-8598-d6201c6cbf80 HTTP/1.1" 200 590 0.022252
2015-09-29 11:08:22.229 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/floatingips.json?fixed_ip_address=192.168.0.28&port_id=57e6e419-1b1c-426d-a11f-d0f78c36a7bd HTTP/1.1" 200 232 0.004355
2015-09-29 11:08:22.241 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/subnets.json?id=c31c255e-df1f-43ca-a5a8-48c75ec995bd HTTP/1.1" 200 677 0.009437
2015-09-29 11:08:22.261 1214 INFO neutron.wsgi 192.168.50.132 - - "GET /v2.0/ports.json?network_id=891e0735-5f5e-4554-8598-d6201c6cbf80&device_owner=network%3Adhcp HTTP/1.1" 200 865 0.017879
绑定端口失败。
doscho 发表于 2015-9-29 11:14
在neutron日志文件/etc/neutron/server.log中，报出如下错误：
015-09-29 11:07:16.243 1214 INFO neu ...
核实下ml2的配置
ERROR neutron.plugins.ml2.managers
推荐参考
centos7.1 上部署kilo， nova问题
http://www.aboutyun.com/forum.php?mod=viewthread&tid=15406
页:
[1]