Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nova: VM stuck in "starting up" #49

Closed
AJNOURI opened this issue Dec 24, 2016 · 2 comments
Closed

Nova: VM stuck in "starting up" #49

AJNOURI opened this issue Dec 24, 2016 · 2 comments

Comments

@AJNOURI
Copy link
Owner

AJNOURI commented Dec 24, 2016

RDO All-In-One devstack (Newton) on Vmware workstation.

selection_658

and the most noticeable log:

for i in ls /var/log/nova/*.log; do tail $i ; echo ""; echo ">>> $i <<<" ;read -p "Press any key..."; done
.

..

/var/log/nova/nova-manage.log <<<
Press any key...
2016-12-24 10:32:58.397 4657 WARNING oslo_config.cfg [req-45d3cad4-d94a-4c80-8b34-c3b16736bb5b - - - - -] Option "rabbit_port" from group "oslo_messaging_rabbit" is deprecated for removal. Its value may be silently ignored in the future.
2016-12-24 10:32:58.397 4657 WARNING oslo_config.cfg [req-45d3cad4-d94a-4c80-8b34-c3b16736bb5b - - - - -] Option "rabbit_userid" from group "oslo_messaging_rabbit" is deprecated for removal. Its value may be silently ignored in the future.
2016-12-24 10:32:58.398 4657 WARNING oslo_config.cfg [req-45d3cad4-d94a-4c80-8b34-c3b16736bb5b - - - - -] Option "rabbit_password" from group "oslo_messaging_rabbit" is deprecated for removal. Its value may be silently ignored in the future.
2016-12-24 10:32:58.716 4657 INFO nova.console.websocketproxy [req-45d3cad4-d94a-4c80-8b34-c3b16736bb5b - - - - -] 7: connect info: {u'instance_uuid': u'aedaaed5-0ea3-4dee-ac29-c86beccea8ad', u'internal_access_path': None, u'last_activity_at': 1482571977.40909, u'console_type': u'novnc', u'host': u'rdo-newton', u'token': u'b6c743e8-8fa8-4c59-a841-81eaeba2c4fd', u'access_url': u'http://192.168.0.126:6080/vnc_auto.html?token=b6c743e8-8fa8-4c59-a841-81eaeba2c4fd', u'port': u'5900'}
2016-12-24 10:32:58.717 4657 INFO nova.console.websocketproxy [req-45d3cad4-d94a-4c80-8b34-c3b16736bb5b - - - - -] 7: connecting to: rdo-newton:5900
2016-12-24 10:33:01.016 4650 INFO nova.console.websocketproxy [-] 192.168.0.146: ignoring socket not ready
2016-12-24 10:33:01.047 4651 INFO nova.console.websocketproxy [-] 192.168.0.146: ignoring socket not ready
2016-12-24 10:33:01.102 4652 INFO nova.console.websocketproxy [-] 192.168.0.146: ignoring socket not ready
2016-12-24 10:33:01.267 4654 INFO nova.console.websocketproxy [-] 192.168.0.146: ignoring socket not ready
2016-12-24 10:33:01.295 4655 INFO nova.console.websocketproxy [-] 192.168.0.146: ignoring socket not ready

@AJNOURI
Copy link
Owner Author

AJNOURI commented Dec 24, 2016

On the nova host (same as controller):
egrep -c '(vmx|svm)' /proc/cpuinfo
1
So I changed in the file /etc/nova/nova.conf in the section [libvirt]

virt_type = qemu

to

virt_type = kvm

which helped move forward, now it is stuck in

"Booting from Hard Disk ..."
GRUB

#50

@AJNOURI AJNOURI closed this as completed Dec 24, 2016
@AJNOURI AJNOURI reopened this Feb 13, 2017
@AJNOURI
Copy link
Owner Author

AJNOURI commented Feb 13, 2017

/etc/nova/nova.conf
section [libvirt]
Changing cpu_mode from host-model to none
cpu_mode = none
and virt_type back to qemu
virt_type = qemu
solved the problem for newly created VMs.

@AJNOURI AJNOURI closed this as completed Feb 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant