Ask Your Question
3

cirros instance hang at boot time, console show"Starting up"

asked 2016-12-29 08:19:33 -0500

kramer gravatar image

updated 2016-12-29 23:31:26 -0500

I am using Mitaka openstack on CentOS7. I use cirros image to create a vm. The openstack server list command shows the instance is active

[root@controller rabbitmq]# openstack server list
+--------------------------------------+------+--------+-----------------------+
| ID                                   | Name | Status | Networks              |
+--------------------------------------+------+--------+-----------------------+
| ac7ae80e-52ed-4b68-b241-37a9eee9ab7d | c2   | ACTIVE | provider=************ |
+--------------------------------------+------+--------+-----------------------+

But when access the instance by vnc, it only shows Starting up ... and it hang there like forever.

I also try to use other image like CentOS7. But it also hang at boot time. This time the VNC console shows Probing edd. Also I find the file in /var/lib/nova/{instance id}/console.log. I guess this is the console output of the instance. It shows below content

  CentOS Linux (3.10.0-327.28.3.el7.x86_64) 7 (Core)                        
  CentOS Linux (0-rescue-56d65f493d8f854534fe792ecf014b83) 7 (Core)        














  Use the ^ and v keys to change the selection.                       
  Press 'e' to edit the selected item, or 'c' for a command prompt.   
  The selected entry will be started automatically in 0s.

I also checked the nova-compute.log on the corresponding compute node. Below are the output

2016-12-29 20:48:55.925 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Attempting claim: memory 64 MB, disk 1 GB, vcpus 1 CPU
2016-12-29 20:48:55.925 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Total memory: 16383 MB, used: 512.00 MB
2016-12-29 20:48:55.926 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] memory limit: 24574.50 MB, free: 24062.50 MB
2016-12-29 20:48:55.926 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Total disk: 49 GB, used: 0.00 GB
2016-12-29 20:48:55.926 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] disk limit: 49.00 GB, free: 49.00 GB
2016-12-29 20:48:55.927 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Total vcpu: 8 VCPU, used: 0.00 VCPU
2016-12-29 20:48:55.927 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] vcpu limit not specified, defaulting to unlimited
2016-12-29 20:48:55.944 2263 INFO nova.compute.claims : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Claim successful
2016-12-29 20:48:57.869 2263 WARNING nova.virt.osinfo : Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-12-29 20:48:57.950 2263 WARNING nova.virt.osinfo : Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-12-29 20:48:58.290 2263 WARNING nova.virt.osinfo : Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-12-29 20:48:58.295 2263 INFO nova.virt.libvirt.driver : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] Creating image
2016-12-29 20:49:00.174 2263 WARNING nova.virt.osinfo : Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2016-12-29 20:49:01.333 2263 INFO nova.compute.manager [-] [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] VM Started (Lifecycle Event)
2016-12-29 20:49:01.472 2263 INFO nova.compute.manager : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] VM Paused (Lifecycle Event)
2016-12-29 20:49:01.666 2263 INFO nova.compute.manager : [instance: ac7ae80e-52ed-4b68-b241-37a9eee9ab7d] During sync_power_state the instance has a pending task (spawning). Skip.
2016-12-29 20:49:06.025 2263 INFO nova.compute.manager : [instance ...
(more)
edit retag flag offensive close merge delete

Comments

What versions of Libvirt and QEMU are installed? What is the output of rpm -qi qemu-kvm and rpm -qi libvirt?

sgordon gravatar imagesgordon ( 2016-12-29 10:41:53 -0500 )edit

Hi Sgordon

I added those information at the end of my post. Can you help to check please?

kramer gravatar imagekramer ( 2016-12-29 20:42:42 -0500 )edit

Unfortunately those versions look correct, so there goes my theory... :)

sgordon gravatar imagesgordon ( 2016-12-30 10:25:06 -0500 )edit

I am also facing the same issue on vcenter and vmware fusion but when I have deployed on virtualbox it wen perfectly fine. these are the packages were usig packstack

qemu-kvm-ev-2.6.0-27.1.el7.x86_64 qemu-kvm-common-ev-2.6.0-27.1.el7.x86_64 libvirt-daemon-kvm-2.0.0-10.el7_3.2.x86_64

mkhan gravatar imagemkhan ( 2017-01-03 14:04:10 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-02-24 05:39:57 -0500

Shaik Saddam Hussain gravatar image

Hi,

Check parameter value of virt_type in /etc/nova/nova.conf file.

for better performance virt_type=kvm and restart all nova related services.

edit flag offensive delete link more

Comments

I think this is not the key point to solve this problem. It might move problem to another.

ekeyme gravatar imageekeyme ( 2018-04-10 21:14:01 -0500 )edit

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: 2016-12-29 08:19:33 -0500

Seen: 1,354 times

Last updated: Dec 29 '16