Ask Your Question

Suspend Opation not working in Icehouse

asked 2014-09-16 00:18:55 -0500

Deeptanshu gravatar image

updated 2014-09-16 12:50:26 -0500

mpetason gravatar image


I have installed the Icehouse version of openstack and all the components are working fine except suspend option. I am getting the below error while resuming the instance. It is not resuming and showing the shutdown state. Please suggest the solution.


2014-09-16 10:27:15.145 21357 INFO nova.compute.resource_tracker [-] Compute_service record 
updated for compute:compute.compute

2014-09-16 10:27:39.574 21357 AUDIT nova.compute.manager [req-84e1b9b0-1835-46f1-a06d-19b63d50e14e 8976b4316afc4da2a8e2f473d9864f27 21ef44195eb049a88444450404401238] 
[instance: a57745bf-61b0-48c1-87a9-2f5e89026112] Resuming

2014-09-16 10:27:41.064 21357 ERROR nova.virt.libvirt.driver [req-84e1b9b0-1835-46f1-a06d-19b63d50e14e 8976b4316afc4da2a8e2f473d9864f27 21ef44195eb049a88444450404401238] An error occurred while trying to launch a defined domain with xml: <domain type='kvm'>



  <memory unit='KiB'>2097152</memory>

  <currentMemory unit='KiB'>2097152</currentMemory>

  <vcpu placement='static'>1</vcpu>

  <sysinfo type='smbios'>


      <entry name='manufacturer'>OpenStack Foundation</entry>

      <entry name='product'>OpenStack Nova</entry>

      <entry name='version'>2014.1</entry>

      <entry name='serial'>58384454-544e-0025-904b-0025904b1160</entry>

      <entry name='uuid'>a57745bf-61b0-48c1-87a9-2f5e89026112</entry>




    <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>

    <boot dev='hd'/>

    <smbios mode='sysinfo'/>






  <cpu mode='host-passthrough'>


  <clock offset='utc'>

    <timer name='pit' tickpolicy='delay'/>

    <timer name='rtc' tickpolicy='catchup'/>

    <timer name='hpet' present='no'/>







    <disk type='block' device='disk'>

      <driver name='qemu' type='raw' cache='none'/>

      <source dev='/dev/disk/by-path/

      <target dev='vda' bus='virtio'/>


      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>


    <controller type='usb' index='0'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>


    <controller type='pci' index='0' model='pci-root'/>

    <interface type='bridge'>

      <mac address='fa:16:3e:b9:61:43'/>

      <source bridge='qbr372d7ae4-d4'/>

      <target dev='tap372d7ae4-d4'/>

      <model type='virtio'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>


    <serial type='file'>

      <source path='/var/lib/nova/instances/a57745bf-61b0-48c1-87a9-2f5e89026112/console.log'/>

      <target port='0'/>


    <serial type='pty'>

      <target port='1'/>


    <console type='file'>

      <source path='/var/lib/nova/instances/a57745bf-61b0-48c1-87a9-2f5e89026112/console.log'/>

      <target type='serial' port='0'/>


    <input type='tablet' bus='usb'/>

    <input type='mouse' bus='ps2'/>

    <input type='keyboard' bus='ps2'/>

    <graphics type='vnc' port='-1' autoport='yes' listen='' keymap='en-us'>

      <listen type='address' address=''/>



      <model type='cirrus' vram='9216' heads='1'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>


    <memballoon model='virtio'>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>




2014-09-16 10:27:41.327 21357 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: internal error: cannot load AppArmor profile 'libvirt-a57745bf-61b0-48c1-87a9-2f5e89026112'

2014-09-16 10:27:41.327 21357 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):

2014-09-16 10:27:41.327 21357 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/", line 133, in _dispatch_and_reply ...
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2014-09-16 02:03:35 -0500

semyazz gravatar image

updated 2014-09-16 02:09:45 -0500

You got the answer in your last ERROR message. It's because of the AppArmor. Turn it off or tune it to your needs and it should work like a charm. I had a similar issue some time ago. To be sure check AppArmor's logs (it should be in syslog afair)

It should be related to:

Ignore it's about spawning, there are many different errors when AppArmor blocks something (XML profile in your case).

edit flag offensive delete link more

answered 2014-09-17 05:15:38 -0500

Deeptanshu gravatar image


I have done all the require changes as suggested. Still have the same issue. I am getting few logs in syslog listed below. Kindly suggested any clue. I have completely disable the AppArmon with the help of below option.

sudo /etc/init.d/apparmor stop

sudo update-rc.d -f apparmor remove

Sep 16 11:26:07 compute kernel: [3598546.598304] type=1400 audit(1410846967.679:120): apparmor="STATUS" operation="profile_load" parent=9095 profile="unconfined" name="libvirt-55a75460-c9ba-4671-927c-3fbbaf60c489" pid=9096 comm="apparmor_parser"

edit flag offensive delete link more

answered 2014-09-16 01:20:32 -0500

try using this command from command line nova resume INSTANCE_NAME or look at this for a detailed explanation to your problem.

edit flag offensive delete link more



Not working!

Don't know where exactly issue is. Pause option is working fine.

Deeptanshu gravatar imageDeeptanshu ( 2014-09-16 01:52:46 -0500 )edit

have you followed the link that i mentioned in the answer

Syed Awais Ali gravatar imageSyed Awais Ali ( 2014-09-16 01:54:44 -0500 )edit

I briefly checked that link and I don't know why guy in that thread discourage to use SUSPEND. I've encountered only few problems with that, and one was related to AppArmor settings. (Ubuntu/Debian Icehouse Openstack). Error is quite clear here - AppArmor's profile cannot be loaded.

semyazz gravatar imagesemyazz ( 2014-09-16 02:13:58 -0500 )edit

The second bug during Suspend was related to Public network. It's somehow connected to admins and if the user who is going to suspend an instance isn't an admin and the instance has IP in public network (not floating), it's also not possible to suspend such instance. However, I think it was fixed.

semyazz gravatar imagesemyazz ( 2014-09-16 02:16:04 -0500 )edit

Please , post nova list for particular tenant.

dbaxps gravatar imagedbaxps ( 2014-09-17 06:08:08 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-09-16 00:18:55 -0500

Seen: 585 times

Last updated: Sep 17 '14