[Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Hello friends,

 I am getting problem when I try to start a VM, it keeps ate Scheduling
task and doesn't start the VM. It is happining after I made a apt-get
update and apt-get upgrade.
 I really don't know what to do, anybody can help me, please?

Thank you.

Guilherme.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Ronivon Costa
Have you looked the compute.log file? You should really start from there. :D
Also, if you really expect some help, you must provide some information.
Search in the logs for clues, and if it can't help or you don't understand
what you see,  then send it along as well.
Roni.
 No dia 5 de Fev de 2013 11:59, Guilherme Russi 
luisguilherme...@gmail.com escreveu:

 Hello friends,

  I am getting problem when I try to start a VM, it keeps ate Scheduling
 task and doesn't start the VM. It is happining after I made a apt-get
 update and apt-get upgrade.
  I really don't know what to do, anybody can help me, please?

 Thank you.

 Guilherme.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Hello Roni, thank you for returning,

 I don't understand the logs yet, I'm working with that, but here is a
piece of my nova-compute.log:

2013-02-05 10:11:07 11592 DEBUG nova.utils [-] Got semaphore
compute_resources for method update_available_resource... inner
/usr/lib/python2.7/dist-packages/nova/utils.py:721
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free ram (MB): 7136 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:470
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free disk (GB): 88 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:471
2013-02-05 10:11:12 11592 DEBUG nova.compute.resource_tracker [-]
Hypervisor: free VCPUs: 4 _report_hypervisor_resource_view
/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py:476
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free ram
(MB): 7354
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free disk
(GB): 93
2013-02-05 10:11:12 11592 AUDIT nova.compute.resource_tracker [-] Free
VCPUS: 4
2013-02-05 10:11:12 11592 INFO nova.compute.resource_tracker [-]
Compute_service record updated for tiresias
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_rebooting_instances periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Skipping
ComputeManager._cleanup_running_deleted_instances, 4 ticks left until next
run periodic_tasks /usr/lib/python2.7/dist-packages/nova/manager.py:167
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._check_instance_build_time periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._heal_instance_info_cache periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._run_image_cache_manager_pass periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._reclaim_queued_deletes periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 DEBUG nova.compute.manager [-]
FLAGS.reclaim_instance_interval = 0, skipping... _reclaim_queued_deletes
/usr/lib/python2.7/dist-packages/nova/compute/manager.py:2790
2013-02-05 10:11:12 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._report_driver_status periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172
2013-02-05 10:11:12 11592 INFO nova.compute.manager [-] Updating host status
2013-02-05 10:11:12 11592 DEBUG nova.virt.libvirt.driver [-] Updating host
stats update_status
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py:3063
2013-02-05 10:11:18 11592 DEBUG nova.manager [-] Running periodic task
ComputeManager._poll_unconfirmed_resizes periodic_tasks
/usr/lib/python2.7/dist-packages/nova/manager.py:172

Regards.

Guilherme.


2013/2/5 Ronivon Costa ronivon.co...@gmail.com

 Have you looked the compute.log file? You should really start from there.
 :D
 Also, if you really expect some help, you must provide some information.
 Search in the logs for clues, and if it can't help or you don't understand
 what you see,  then send it along as well.
 Roni.
  No dia 5 de Fev de 2013 11:59, Guilherme Russi 
 luisguilherme...@gmail.com escreveu:

  Hello friends,

  I am getting problem when I try to start a VM, it keeps ate Scheduling
 task and doesn't start the VM. It is happining after I made a apt-get
 update and apt-get upgrade.
  I really don't know what to do, anybody can help me, please?

 Thank you.

 Guilherme.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Ronivon Costa
Your logs contain no useful information related to your problem. You should
send the piece of log that contains the information generated when you
launched
the vm.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Pranav
I believe that you have broken your configuration files. Please do make
sure that your nova confi files are proper. I had similar issue where in i
had to change the libvirt option to QEMU because some KVM issue and the
images started spawning.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
I found a solution, I guess, well, I droped the tables from quantum and
create a network range again, and it worked again. Now I'm trying to figure
out how to insert a floating IP to ssh and ping in my VMs. Do you have any
ideas? I can login in the VM, but when I type sudo ifconfig -a it has no IP.

Thank you all.

Guilherme.


2013/2/5 Pranav pps.pra...@gmail.com

 I believe that you have broken your configuration files. Please do make
 sure that your nova confi files are proper. I had similar issue where in i
 had to change the libvirt option to QEMU because some KVM issue and the
 images started spawning.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Problem starting a VM

2013-02-05 Thread Guilherme Russi
Guys, I'm trying to create the network to connect my VMs, but they don't
receive the IP, my network configs in the controller node is:

# eth1 - link external with the internet
address 10.3.77.51

# eth0 - link internal to connect the compute nodes
address 192.168.3.1

And in my compute note I have:


# eth1 - link external with the internet
address 10.3.77.52

# eth0 - link internal to connect to the cloud
address 192.168.3.2

What am I doing wrong?

Regards.

Guilherme.


2013/2/5 Guilherme Russi luisguilherme...@gmail.com

 I found a solution, I guess, well, I droped the tables from quantum and
 create a network range again, and it worked again. Now I'm trying to figure
 out how to insert a floating IP to ssh and ping in my VMs. Do you have any
 ideas? I can login in the VM, but when I type sudo ifconfig -a it has no IP.

 Thank you all.

 Guilherme.


 2013/2/5 Pranav pps.pra...@gmail.com

  I believe that you have broken your configuration files. Please do make
 sure that your nova confi files are proper. I had similar issue where in i
 had to change the libvirt option to QEMU because some KVM issue and the
 images started spawning.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp