Ask Your Question
0

Cannot launch VM in multi-node deployment

asked 2012-12-14 08:19:33 -0500

xionglingfeng gravatar image

I followed the instruction here: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst (https://github.com/mseknibilel/OpenSt...) to have my OpenStack installed in my three servers(controller, quantum and compute).

Internal network: 10.2.0.0/24 External network: 10.1.0.0/24 controller node: 10.1.0.6, 10.2.0.6 quantum node: 10.1.0.8, 10.2.0.8 compute node: 10.1.0.10, 10.2.0.10

Nearly all configurations are as same as it said in the above guide. I only delete these lines: compute_driver=libvirt.LibvirtDriver libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver or the compute node will complain there is no such classes available.

However, when I tried to launch a VM, it failed to ERROR status. In controller node, I got this

bear@os-controller2:~$ nova show test +------------------------+----------------------------------------------------------------------------------+ | Property | Value | +------------------------+----------------------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | error | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2012-12-14T08:05:09Z | | fault | {u'message': u'libvirtError', u'code': 500, u'created': u'2012-12-14T08:05:16Z'} | | flavor | m1.tiny (1) | | hostId | e42e71bf530be67997df4e937ada01342353237873bd2a0c130914ee | | id | f2ba2f45-b198-4636-9ca7-84a8c3fd33b9 | | image | cirros-0.3.0-x86_64-disk (729141f8-3068-4000-90de-555c47b054ed) | | key_name | vmtest | | metadata | {} | | name | test | | net1 network | 50.50.1.3 | | security_groups | [{u'name': u'dev'}] | | status | ERROR | | tenant_id | 21c2bc5a366648898b941d7568a5a05c | | updated | 2012-12-14T08:05:16Z | | user_id | b38f4e54f97747fda7bee397eae8f9c5 | +------------------------+----------------------------------------------------------------------------------+

And in compute node, I found:

2012-12-14 16:00:50 INFO nova.openstack.common.rpc.common [-] Reconnecting to AMQP server on 10.2.0.6:5672 2012-12-14 16:00:50 INFO nova.openstack.common.rpc.common [-] Connected to AMQP server on 10.2.0.6:5672 2012-12-14 16:01:20 INFO nova.compute.manager [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Updating bandwidth usage cache 2012-12-14 16:01:21 AUDIT nova.compute.resource_tracker [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Free ram (MB): -29 2012-12-14 16:01:21 AUDIT nova.compute.resource_tracker [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Free disk (GB): 97 2012-12-14 16:01:21 AUDIT nova.compute.resource_tracker [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Free VCPUS: 0 2012-12-14 16:01:21 INFO nova.compute.resource_tracker [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Compute_service record updated for os-compute 2012-12-14 16:01:22 INFO nova.compute.manager [req-f1e4e7ef-5719-43d7-8e61-78b4cb3ea29d None None] Updating host status 2012-12-14 16:02:24 INFO nova.openstack.common.rpc.common [-] Connected to AMQP server on 10.2.0.6:5672 2012-12-14 16:02:25 AUDIT nova.compute.resource_tracker [-] Free ram (MB): -29 2012-12-14 16:02:25 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 97 2012-12-14 16:02:25 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0 2012-12-14 16:02:25 INFO nova.compute.resource_tracker [-] Compute_service record updated for os-compute 2012-12-14 16:03:28 AUDIT nova.compute.resource_tracker [-] Free ram (MB): -29 2012-12-14 16:03:28 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 97 2012-12-14 16:03:28 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 0 2012-12-14 16:03:28 INFO nova.compute.resource_tracker [-] Compute_service record updated for os-compute 2012-12-14 16:03:29 INFO nova.compute.manager [-] Updating host status 2012-12-14 16:04:08 AUDIT nova.compute.manager [req-c98bf1d2-2032-4650-9b33-68ca713f0af6 b38f4e54f97747fda7bee397eae8f9c5 21c2bc5a366648898b941d7568a5a05c] [instance: 0ad16b0b-b140-492a-819a-8f571383e39f] Terminating instance 2012-12-14 16:04:09 INFO nova.virt.libvirt.driver ... (more)

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2012-12-20 13:24:37 -0500

aji-zqfan gravatar image

if you don't want to use novnc try to disable all novnc settings (comment it by leading # in nova.conf) and restart nova service (nova-api and nova-compute) i'm not sure if this will help, but wrong setting of novnc wii cause vir domain error (in my case, only novnc will cause this error)

good luck

edit flag offensive delete link more
0

answered 2012-12-24 06:07:06 -0500

xionglingfeng gravatar image

Thanks zqfan, that solved my question.

edit flag offensive delete link more
0

answered 2012-12-24 06:09:01 -0500

xionglingfeng gravatar image

I'm sorry but zqfan's answer is not the solution. The problem is I write incorrect nova.conf

edit flag offensive delete link more

Your Answer

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

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-12-14 08:19:33 -0500

Seen: 22 times

Last updated: Dec 24 '12