Hi, have you inspected /var/log/libvirt/qemu/instance-xxxxxxxx.log files? Such problem can be connected with your hypervisor. Especially if you use nested kvm virtualization on your host machine.
On Mon, Jun 9, 2014 at 2:06 PM, Deepak Shetty <dpkshe...@gmail.com> wrote: > (Hit send by mistake.. continuing below) > > > On Mon, Jun 9, 2014 at 3:32 PM, Deepak Shetty <dpkshe...@gmail.com> wrote: > >> Hi All, >> The last time I sent this issue, I didn't had the right tags in the >> subject so sending with the right tags, in the hope that the right folks >> might help provide some clues. >> >> I am usign latest devstack on F20 and I see VMs stuck in 'spawning' state. >> No errors in n-sch, n-cpu and I checked other n-* screen logs too, no >> errors whatsoever >> >> There is enuf memory and disk space available for the tiny and small >> flavour VMs I am trying to run >> >> > 2014-06-09 09:57:19.935 AUDIT nova.compute.resource_tracker [-] Free ram > (MB): 1905 > 2014-06-09 09:57:19.935 AUDIT nova.compute.resource_tracker [-] Free disk > (GB): 46 > 2014-06-09 09:57:19.936 AUDIT nova.compute.resource_tracker [-] Free > VCPUS: 1 > 2014-06-09 09:57:19.936 AUDIT nova.compute.resource_tracker [-] PCI stats: > [] > > The only thing that i see other than INFO/DEbug is the below > 2014-06-09 09:57:42.700 WARNING nova.compute.manager [-] Found 3 in the > database and 0 on the hypervisor. > > What does that mean ? Does that say that Nova sees 3 VMs in its DB but a > query to the hyp (via libvirt I assume) returns none ? > > Interestingly I can see the qemu process for my VM that nova says is stuck > in Spawning state and virsh list also lists' it > But i don't see the libvirt.xml for this stuck VM (from nova's > perspective) in the /opt/stack/data/nova/instances/<uuid> folder. > > I was trying to figure what this means ? Where is nova stuck ? Screen logs > just doesn't point to anything useful to debug further. > > From the n-cpu logs i see the "Creating image" info log from > nova.virt.libvirt and thats the last > I don't see the info log "Creating isntance" from nova.virt.. so it looks > like its stuck somewhere between creating image and spawning instance.. but > virsh list and qemu process says otherwise > > Looking for some debug hints here > > thanx, > deepak > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
