Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
Hi Kevin, If you are using KVM as hyper visor and if your compute node having any issues with kvm acceleration, it can lead to the below problem - So ou can try changing the virt_type to qemu from kvm in /etc/nova/nova- compute.conf . After restarting the nova compute service - try to launch the vm again. Regards, Guna __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I ran into similar behavior once, and it turned out I was running out
of space on the system. This blog post helped me track down the
problem:
http://porkrind.org/missives/libvirt-based-qemu-vm-pausing-by-itself/
Not sure whether it's relevant to your situation, but it's something
to check.
- -Ben
On 12/31/2014 09:41 AM, Paul Michali (pcm) wrote:
Not sure if I’m going crazy or what. I’m using DevStack and, after
stacking I tried booting a Cirros 3.2, 3.3, and Ubuntu cloud 14.04
image. Each time, the image ends up in PAUSED power state:
ubuntu@juno:/opt/stack/neutron$ nova show peter
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
| | OS-EXT-SRV-ATTR:host | juno
| | OS-EXT-SRV-ATTR:hypervisor_hostname | juno
| | OS-EXT-SRV-ATTR:instance_name| instance-0001
| | OS-EXT-STS:power_state | 3
| | OS-EXT-STS:task_state| -
| | OS-EXT-STS:vm_state | active
| | OS-SRV-USG:launched_at |
2014-12-31T15:15:33.00 | |
OS-SRV-USG:terminated_at | -
| | accessIPv4 |
| | accessIPv6 |
| | config_drive |
| | created | 2014-12-31T15:15:24Z
| | flavor | m1.tiny (1)
| | hostId |
5b0c48250ccc0ac3fca8a821e29e4b154ec0b101f9cc0a0b27071a3f | |
id |
ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 | |
image| cirros-0.3.3-x86_64-uec
(797e4dee-8c03-497f-8dac-a44b9351dfa3) | | key_name
| - |
| metadata | {}
| | name | peter
| | os-extended-volumes:volumes_attached | []
| | private network | 10.0.0.4
| | progress | 0
| | security_groups | default
| | status | ACTIVE
| | tenant_id|
7afb5bc1d88d462c8d57178437d3c277 | |
updated | 2014-12-31T15:15:34Z
| | user_id |
4ff18bdbeb4d436ea4ff1bcd29e269a9 |
+--++
ubuntu@juno:/opt/stack/neutron$ nova list
+--+---+++-+--+
| ID | Name | Status | Task State |
Power State | Networks |
+--+---+++-+--+
| ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 | peter | ACTIVE | - |
Paused | private=10.0.0.4 |
I don’t see this with Kilo latest images. Any idea what I may be
doing wrong, or if there is an issue (I didn’t see anything on
Google search)?
IMAGE_ID=`nova image-list | grep 'cloudimg-amd64 ' | cut -d' ' -f
2` PRIVATE_NET=`neutron net-list | grep 'private ' | cut -f 2 -d'
‘`
nova boot peter --flavor 3 --image $IMAGE_ID --user-data
~/devstack/user_data.txt --nic net-id=$PRIVATE_NET nova boot
--flavor 1 --image cirros-0.3.3-x86_64-uec --nic
net-id=$PRIVATE_NET paul
Thanks.
PCM (Paul Michali)
MAIL …..…. p...@cisco.com IRC ……..… pc_m (irc.freenode.com) TW
………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A
96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
___ OpenStack-dev
mailing list OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBAgAGBQJUpryOAAoJEDehGd0Fy7uqVQgH/3EmJBE2Z8DMQqCqhHFLat5b
H34R2sXz0ODP+X6nu9MykXjTk7O/zDW9aSgW8nNRa7pbyZm+R0AOTpqcc3P1T6uE
zZ6LqL+d8GEVaC4BNIrnCO3Ip3hDmhr+HQcAZa0LYdgxF4/Oc9merycTy5UDzwbZ
hcUwULr4OdnJqdkcnp1XfqfEKsRWi7varkj6nnuB46dOJBeH8Tmr/9NTBo+veglK
kpmKISuH+TyWpjZekmkRpPq97vEQ1pxBeJcqHfhF5x5q14CleN51JKg8J7xckcmO
XS9rrQtHjMxIB86b6oAAfKlTGhz9FsZ7c1C3QmCxco3NqCtFtCoXsFoYhiLoyIo=
=4AwW
-END PGP SIGNATURE-
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
These VMs that are running devstack are 50GB disk, so there is plenty of disk space. I don’t have cinder set up with this devstack setup. I looked in the log for the instance and in the failing case the same message was displayed (with different MAC and uuid), and then on the next line, I see this error, register dump. KVM: entry failed, hardware error 0x0 EAX= EBX= ECX= EDX=0663 ESI= EDI= EBP= ESP= EIP=e05b EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=85 00 87 00 89 00 8b 00 00 00 86 00 88 00 8a 00 8c 00 00 90 2e 66 83 3e a4 65 00 0f 85 53 f2 31 c0 8e d0 66 bc 00 70 00 00 66 ba 4f 3c 0f 00 e9 b1 f0 Can anyone glen anything from this? In the libvirtd.log, I see: 2015-01-02 15:48:21.257+: 20711: info : libvirt version: 1.2.2 2015-01-02 15:48:21.257+: 20711: error : virNetSocketReadWire:1454 : End of file while reading data: Input/output error Not much info (for me :). PCM (Paul Michali) MAIL …..…. p...@cisco.commailto:p...@cisco.com IRC ……..… pc_m (irc.freenode.comhttp://irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Jan 2, 2015, at 10:41 AM, James Downs e...@egon.ccmailto:e...@egon.cc wrote: On Jan 2, 2015, at 4:53 AM, Paul Michali (pcm) p...@cisco.commailto:p...@cisco.com wrote: I don’t see what the difference is between a working and non-working setup. :( One other time I’ve seen this happen is if the compute node is low (or out) of disk space. If there’s connectivity problems with a cinder device, this would be a similar situation. As Kevin suggested, I’d also start looking into any logs KVM/libvirt might be generating. Cheers, -j ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
On Jan 2, 2015, at 4:53 AM, Paul Michali (pcm) p...@cisco.com wrote: I don’t see what the difference is between a working and non-working setup. :( One other time I’ve seen this happen is if the compute node is low (or out) of disk space. If there’s connectivity problems with a cinder device, this would be a similar situation. As Kevin suggested, I’d also start looking into any logs KVM/libvirt might be generating. Cheers, -j ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
Ah, doesn't seem to be a Neutron issue then since the 'network-vif-plugged' event is showing up and it's attempting to resume. The red flag looks like that Instance is paused unexpectedly. Ignore.. If you grep the nova code base for that, it brings up a note linking to bug 1097806.[1] The VM is paused when Nova didn't expect it to be. Do you have any other tools running that might be affecting kvm? 1. https://bugs.launchpad.net/nova/+bug/1097806 On Thu, Jan 1, 2015 at 8:09 AM, Paul Michali (pcm) p...@cisco.com wrote: Hi Kevin, No exceptions/tracebacks/errors in Neutron at all. In the Nova logs, it seems to create the instance, pause, and then resume, but it looks like maybe it is not resuming? 2015-01-01 14:44:30.716 3516 DEBUG nova.openstack.common.processutils [-] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 -- --if-exists del-port qvoded0d35f-20 -- add-port br-int qvoded0d35\ f-20 -- set Interface qvoded0d35f-20 external-ids:iface-id=ded0d35f-204f-4ca8-a85b-85decb53d9fe external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:81:ab:12 external-ids:vm-uuid=c32ac737-1788-4420-b200-2a107d5ad335 exec\ ute /opt/stack/nova/nova/openstack/common/processutils.py:161 2015-01-01 14:44:30.786 3516 DEBUG nova.openstack.common.processutils [-] Result was 0 execute /opt/stack/nova/nova/openstack/common/processutils.py:195 2015-01-01 14:44:31.542 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Started emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.543 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Started (Lifecycle Event) 2015-01-01 14:44:31.584 DEBUG nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Started; current vm_sta\ te: building, current task_state: spawning, current DB power_state: 0, VM power_state: 1 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.629 INFO nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:31.630 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Paused emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.630 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Paused (Lifecycle Event) 2015-01-01 14:44:31.670 3516 DEBUG nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Paused; current vm_state: building, current task_state: spawning, c\ urrent DB power_state: 0, VM power_state: 3 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.714 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:38.293 DEBUG nova.compute.manager [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Received event network-vif-plugged-ded0d35f-204f-4ca8-a85b-85decb53d9fe externa\ l_instance_event /opt/stack/nova/nova/compute/manager.py:6180 2015-01-01 14:44:38.293 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Created new semaphore c32ac737-1788-4420-b200-2a107d5ad335-events internal_lock /opt/stack/nova/nova/openstack/comm\ on/lockutils.py:206 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Acquired semaphore c32ac737-1788-4420-b200-2a107d5ad335-events lock /opt/stack/nova/nova/openstack/common/lockutils\ .py:229 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Got semaphore / lock _pop_event inner /opt/stack/nova/nova/openstack/common/lockutils.py:271 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Releasing semaphore c32ac737-1788-4420-b200-2a107d5ad335-events lock /opt/stack/nova/nova/openstack/common/lockutil\ s.py:238 2015-01-01 14:44:38.295 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Semaphore / lock released _pop_event inner /opt/stack/nova/nova/openstack/common/lockutils.py:275 2015-01-01 14:44:38.295 DEBUG nova.compute.manager [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Processing event network-vif-plugged-ded0d35f-204f-4ca8-a85b-85decb53d9fe
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
No other tools. Running a stock Ubuntu 14.04 server, installed devstack, created local.conf, stacked, and tried to create a VM. I’ve since seen this on another VM I have running with Kilo code, so it is not specifically a Juno issue. I don’t see what the difference is between a working and non-working setup. :( On all instances, virsh -v shows 1.2.2. Baffled. PCM (Paul Michali) MAIL …..…. p...@cisco.com IRC ……..… pc_m (irc.freenode.com) TW ………... @pmichali GPG Key … 4525ECC253E31A83 Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83 On Jan 2, 2015, at 4:48 AM, Kevin Benton blak...@gmail.com wrote: Ah, doesn't seem to be a Neutron issue then since the 'network-vif-plugged' event is showing up and it's attempting to resume. The red flag looks like that Instance is paused unexpectedly. Ignore.. If you grep the nova code base for that, it brings up a note linking to bug 1097806.[1] The VM is paused when Nova didn't expect it to be. Do you have any other tools running that might be affecting kvm? 1. https://bugs.launchpad.net/nova/+bug/1097806 On Thu, Jan 1, 2015 at 8:09 AM, Paul Michali (pcm) p...@cisco.com wrote: Hi Kevin, No exceptions/tracebacks/errors in Neutron at all. In the Nova logs, it seems to create the instance, pause, and then resume, but it looks like maybe it is not resuming? 2015-01-01 14:44:30.716 3516 DEBUG nova.openstack.common.processutils [-] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 -- --if-exists del-port qvoded0d35f-20 -- add-port br-int qvoded0d35\ f-20 -- set Interface qvoded0d35f-20 external-ids:iface-id=ded0d35f-204f-4ca8-a85b-85decb53d9fe external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:81:ab:12 external-ids:vm-uuid=c32ac737-1788-4420-b200-2a107d5ad335 exec\ ute /opt/stack/nova/nova/openstack/common/processutils.py:161 2015-01-01 14:44:30.786 3516 DEBUG nova.openstack.common.processutils [-] Result was 0 execute /opt/stack/nova/nova/openstack/common/processutils.py:195 2015-01-01 14:44:31.542 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Started emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.543 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Started (Lifecycle Event) 2015-01-01 14:44:31.584 DEBUG nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Started; current vm_sta\ te: building, current task_state: spawning, current DB power_state: 0, VM power_state: 1 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.629 INFO nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:31.630 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Paused emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.630 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Paused (Lifecycle Event) 2015-01-01 14:44:31.670 3516 DEBUG nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Paused; current vm_state: building, current task_state: spawning, c\ urrent DB power_state: 0, VM power_state: 3 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.714 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:38.293 DEBUG nova.compute.manager [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Received event network-vif-plugged-ded0d35f-204f-4ca8-a85b-85decb53d9fe externa\ l_instance_event /opt/stack/nova/nova/compute/manager.py:6180 2015-01-01 14:44:38.293 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Created new semaphore c32ac737-1788-4420-b200-2a107d5ad335-events internal_lock /opt/stack/nova/nova/openstack/comm\ on/lockutils.py:206 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Acquired semaphore c32ac737-1788-4420-b200-2a107d5ad335-events lock /opt/stack/nova/nova/openstack/common/lockutils\ .py:229 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Got semaphore / lock _pop_event inner /opt/stack/nova/nova/openstack/common/lockutils.py:271 2015-01-01 14:44:38.294 DEBUG
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
I checked and the disk has plenty of space:
Filesystem Size Used Avail Use% Mounted on
/dev/vda150G 6.2G 41G 14% /
none4.0K 0 4.0K 0% /sys/fs/cgroup
udev3.9G 12K 3.9G 1% /dev
tmpfs 799M 408K 799M 1% /run
none5.0M 0 5.0M 0% /run/lock
none3.9G 0 3.9G 0% /run/shm
none100M 0 100M 0% /run/user
One google search mentioned checking user is in libvirtd group (it is). I have
8GB ram with 600+ MB available, when Devstack is running.
I didn’t Cinder was running, but I see cinder-api and cinder-volume processes
running in top. These are running on the bare metal config that does work.
This is a Ubuntu 14.04 image for the host (cloud image).
It seems I either get the problem where the VM is in paused state, or it
doesn’t even start up and is in the BUILDING/SPAWNED state forever.
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pc_m (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On Jan 2, 2015, at 10:43 AM, Ben Nemec openst...@nemebean.com wrote:
Signed PGP part
I ran into similar behavior once, and it turned out I was running out
of space on the system. This blog post helped me track down the
problem:
http://porkrind.org/missives/libvirt-based-qemu-vm-pausing-by-itself/
Not sure whether it's relevant to your situation, but it's something
to check.
-Ben
On 12/31/2014 09:41 AM, Paul Michali (pcm) wrote:
Not sure if I’m going crazy or what. I’m using DevStack and, after
stacking I tried booting a Cirros 3.2, 3.3, and Ubuntu cloud 14.04
image. Each time, the image ends up in PAUSED power state:
ubuntu@juno:/opt/stack/neutron$ nova show peter
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
| | OS-EXT-SRV-ATTR:host | juno
| | OS-EXT-SRV-ATTR:hypervisor_hostname | juno
| | OS-EXT-SRV-ATTR:instance_name| instance-0001
| | OS-EXT-STS:power_state | 3
| | OS-EXT-STS:task_state| -
| | OS-EXT-STS:vm_state | active
| | OS-SRV-USG:launched_at |
2014-12-31T15:15:33.00 | |
OS-SRV-USG:terminated_at | -
| | accessIPv4 |
| | accessIPv6 |
| | config_drive |
| | created | 2014-12-31T15:15:24Z
| | flavor | m1.tiny (1)
| | hostId |
5b0c48250ccc0ac3fca8a821e29e4b154ec0b101f9cc0a0b27071a3f | |
id |
ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 | |
image| cirros-0.3.3-x86_64-uec
(797e4dee-8c03-497f-8dac-a44b9351dfa3) | | key_name
| - |
| metadata | {}
| | name | peter
| | os-extended-volumes:volumes_attached | []
| | private network | 10.0.0.4
| | progress | 0
| | security_groups | default
| | status | ACTIVE
| | tenant_id|
7afb5bc1d88d462c8d57178437d3c277 | |
updated | 2014-12-31T15:15:34Z
| | user_id |
4ff18bdbeb4d436ea4ff1bcd29e269a9 |
+--++
ubuntu@juno:/opt/stack/neutron$ nova list
+--+---+++-+--+
| ID | Name | Status | Task State |
Power State | Networks |
+--+---+++-+--+
| ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 | peter | ACTIVE | - |
Paused | private=10.0.0.4 |
I don’t see this with Kilo latest images. Any idea what I may be
doing wrong, or if there is an issue (I didn’t see anything on
Google search)?
IMAGE_ID=`nova image-list | grep 'cloudimg-amd64 ' | cut -d' ' -f
2` PRIVATE_NET=`neutron net-list | grep 'private ' | cut -f 2 -d'
‘`
nova boot peter --flavor 3 --image $IMAGE_ID --user-data
~/devstack/user_data.txt
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
Hi Kevin, No exceptions/tracebacks/errors in Neutron at all. In the Nova logs, it seems to create the instance, pause, and then resume, but it looks like maybe it is not resuming? 2015-01-01 14:44:30.716 3516 DEBUG nova.openstack.common.processutils [-] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 -- --if-exists del-port qvoded0d35f-20 -- add-port br-int qvoded0d35\ f-20 -- set Interface qvoded0d35f-20 external-ids:iface-id=ded0d35f-204f-4ca8-a85b-85decb53d9fe external-ids:iface-status=active external-ids:attached-mac=fa:16:3e:81:ab:12 external-ids:vm-uuid=c32ac737-1788-4420-b200-2a107d5ad335 exec\ ute /opt/stack/nova/nova/openstack/common/processutils.py:161 2015-01-01 14:44:30.786 3516 DEBUG nova.openstack.common.processutils [-] Result was 0 execute /opt/stack/nova/nova/openstack/common/processutils.py:195 2015-01-01 14:44:31.542 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Started emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.543 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Started (Lifecycle Event) 2015-01-01 14:44:31.584 DEBUG nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Started; current vm_sta\ te: building, current task_state: spawning, current DB power_state: 0, VM power_state: 1 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.629 INFO nova.compute.manager [req-77c13ae6-ccf9-48ee-881a-8bb7f04ee4bc None None] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:31.630 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123471.54, c32ac737-1788-4420-b200-2a107d5ad335 = Paused emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:31.630 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] VM Paused (Lifecycle Event) 2015-01-01 14:44:31.670 3516 DEBUG nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Synchronizing instance power state after lifecycle event Paused; current vm_state: building, current task_state: spawning, c\ urrent DB power_state: 0, VM power_state: 3 handle_lifecycle_event /opt/stack/nova/nova/compute/manager.py:1105 2015-01-01 14:44:31.714 3516 INFO nova.compute.manager [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] During sync_power_state the instance has a pending task (spawning). Skip. 2015-01-01 14:44:38.293 DEBUG nova.compute.manager [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Received event network-vif-plugged-ded0d35f-204f-4ca8-a85b-85decb53d9fe externa\ l_instance_event /opt/stack/nova/nova/compute/manager.py:6180 2015-01-01 14:44:38.293 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Created new semaphore c32ac737-1788-4420-b200-2a107d5ad335-events internal_lock /opt/stack/nova/nova/openstack/comm\ on/lockutils.py:206 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Acquired semaphore c32ac737-1788-4420-b200-2a107d5ad335-events lock /opt/stack/nova/nova/openstack/common/lockutils\ .py:229 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Got semaphore / lock _pop_event inner /opt/stack/nova/nova/openstack/common/lockutils.py:271 2015-01-01 14:44:38.294 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Releasing semaphore c32ac737-1788-4420-b200-2a107d5ad335-events lock /opt/stack/nova/nova/openstack/common/lockutil\ s.py:238 2015-01-01 14:44:38.295 DEBUG nova.openstack.common.lockutils [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] Semaphore / lock released _pop_event inner /opt/stack/nova/nova/openstack/common/lockutils.py:275 2015-01-01 14:44:38.295 DEBUG nova.compute.manager [req-0dc50994-e997-41b5-99f2-0a0333f1ea11 nova service] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Processing event network-vif-plugged-ded0d35f-204f-4ca8-a85b-85decb53d9fe _proc\ ess_instance_event /opt/stack/nova/nova/compute/manager.py:6166 2015-01-01 14:44:38.309 3516 DEBUG nova.virt.libvirt.driver [-] [instance: c32ac737-1788-4420-b200-2a107d5ad335] Instance is running spawn /opt/stack/nova/nova/virt/libvirt/driver.py:2622 2015-01-01 14:44:38.310 3516 DEBUG nova.virt.driver [-] Emitting event LifecycleEvent: 1420123478.31, c32ac737-1788-4420-b200-2a107d5ad335 = Resumed emit_event /opt/stack/nova/nova/virt/driver.py:1298 2015-01-01 14:44:38.311 3516 INFO nova.compute.manager [-] [instance:
Re: [openstack-dev] [nova] boot images in power state PAUSED for stable/juno
Any exceptions on the Neutron side? It might not be notifying nova
that the network is ready.
On Wed, Dec 31, 2014 at 8:41 AM, Paul Michali (pcm) p...@cisco.com wrote:
Not sure if I’m going crazy or what. I’m using DevStack and, after stacking
I tried booting a Cirros 3.2, 3.3, and Ubuntu cloud 14.04 image. Each time,
the image ends up in PAUSED power state:
ubuntu@juno:/opt/stack/neutron$ nova show peter
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | juno
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | juno
|
| OS-EXT-SRV-ATTR:instance_name| instance-0001
|
| OS-EXT-STS:power_state | 3
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2014-12-31T15:15:33.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2014-12-31T15:15:24Z
|
| flavor | m1.tiny (1)
|
| hostId |
5b0c48250ccc0ac3fca8a821e29e4b154ec0b101f9cc0a0b27071a3f |
| id |
ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 |
| image| cirros-0.3.3-x86_64-uec
(797e4dee-8c03-497f-8dac-a44b9351dfa3) |
| key_name | -
|
| metadata | {}
|
| name | peter
|
| os-extended-volumes:volumes_attached | []
|
| private network | 10.0.0.4
|
| progress | 0
|
| security_groups | default
|
| status | ACTIVE
|
| tenant_id| 7afb5bc1d88d462c8d57178437d3c277
|
| updated | 2014-12-31T15:15:34Z
|
| user_id | 4ff18bdbeb4d436ea4ff1bcd29e269a9
|
+--++
ubuntu@juno:/opt/stack/neutron$ nova list
+--+---+++-+--+
| ID | Name | Status | Task State | Power
State | Networks |
+--+---+++-+--+
| ec5c8d70-ae80-4cc3-a5bb-b68019170dd6 | peter | ACTIVE | - |
Paused | private=10.0.0.4 |
I don’t see this with Kilo latest images. Any idea what I may be doing
wrong, or if there is an issue (I didn’t see anything on Google search)?
IMAGE_ID=`nova image-list | grep 'cloudimg-amd64 ' | cut -d' ' -f 2`
PRIVATE_NET=`neutron net-list | grep 'private ' | cut -f 2 -d' ‘`
nova boot peter --flavor 3 --image $IMAGE_ID --user-data
~/devstack/user_data.txt --nic net-id=$PRIVATE_NET
nova boot --flavor 1 --image cirros-0.3.3-x86_64-uec --nic
net-id=$PRIVATE_NET paul
Thanks.
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pc_m (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Kevin Benton
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
