libvirt domain launch "Cannot find 'pm-is-supported' in path" error

Bug #1297512 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Unassigned
devstack
Fix Released
Undecided
Davanum Srinivas (DIMS)

Bug Description

Seen here:

http://logs.openstack.org/29/82829/1/check/check-tempest-dsvm-full/67c8984/logs/screen-n-cpu.txt.gz

2014-03-25 14:27:02.318 ERROR nova.virt.libvirt.driver [req-b485d6b2-cf63-468f-ae09-0c6ba31274db SecurityGroupsTestJSON-1020006517 SecurityGroupsTestJSON-1157433096] An error occurred while trying to launch a defined domain with xml: <domain type='qemu'>
  <name>instance-00000032</name>
  <uuid>c3baa6cf-9127-4a69-af9a-58dbba0824cc</uuid>
  <memory>65536</memory>
  <currentMemory>65536</currentMemory>
  <vcpu>1</vcpu>
  <sysinfo type='smbios'>
    <system>
      <entry name='manufacturer'>OpenStack Foundation</entry>
      <entry name='product'>OpenStack Nova</entry>
      <entry name='version'>2014.1</entry>
      <entry name='serial'>44361562-54ff-5e7f-6c5b-ba157fe8645a</entry>
      <entry name='uuid'>c3baa6cf-9127-4a69-af9a-58dbba0824cc</entry>
    </system>
  </sysinfo>
  <os>
    <type arch='x86_64' machine='pc-1.0'>hvm</type>
    <kernel>/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/kernel</kernel>
    <initrd>/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/ramdisk</initrd>
    <cmdline>root=/dev/vda console=tty0 console=ttyS0</cmdline>
    <boot dev='hd'/>
    <smbios mode='sysinfo'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk.config'/>
      <target dev='hdd' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='1' unit='1'/>
    </disk>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='fa:16:3e:9e:b7:1c'/>
      <source bridge='br100'/>
      <model type='virtio'/>
      <driver name='qemu'/>
      <filterref filter='nova-instance-instance-00000032-fa163e9eb71c'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='file'>
      <source path='/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/console.log'/>
      <target port='0'/>
    </serial>
    <serial type='pty'>
      <target port='1'/>
    </serial>
    <console type='file'>
      <source path='/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/console.log'/>
      <target type='serial' port='0'/>
    </console>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Then:

2014-03-25 14:27:05.135 ERROR nova.compute.manager [req-b485d6b2-cf63-468f-ae09-0c6ba31274db SecurityGroupsTestJSON-1020006517 SecurityGroupsTestJSON-1157433096] [instance: c3baa6cf-9127-4a69-af9a-58dbba0824cc] Cannot reboot instance: internal error Process exited while reading console log output: char device redirected to /dev/pts/2
qemu-system-x86_64: -drive file=/opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /opt/stack/data/nova/instances/c3baa6cf-9127-4a69-af9a-58dbba0824cc/disk: Invalid argument

Looking in the libvirtd log:
http://logs.openstack.org/29/82829/1/check/check-tempest-dsvm-full/67c8984/logs/libvirtd.txt.gz
2014-03-25 14:54:56.792+0000: 12413: warning : qemuCapsInit:856 : Failed to get host power management capabilities
2014-03-25 14:54:56.936+0000: 10184: error : virExecWithHook:327 : Cannot find 'pm-is-supported' in path: No such file or directory
2014-03-25 14:54:56.936+0000: 10184: warning : qemuCapsInit:856 : Failed to get host power management capabilities
2014-03-25 14:54:57.004+0000: 12413: error : virExecWithHook:327 : Cannot find 'pm-is-supported' in path: No such file or directory
2014-03-25 14:54:57.004+0000: 12413: warning : qemuCapsInit:856 : Failed to get host power management capabilities

Tags: libvirt
Tracy Jones (tjones-i)
tags: added: libvirt
Changed in devstack:
assignee: nobody → Davanum Srinivas (DIMS) (dims-v)
status: New → In Progress
Solly Ross (sross-7)
Changed in nova:
status: New → Confirmed
status: Confirmed → In Progress
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

Reviewed: https://review.openstack.org/84276
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=878376aabbeb958d950fc97c51d9c553ef2c6cbd
Submitter: Jenkins
Branch: master

commit 878376aabbeb958d950fc97c51d9c553ef2c6cbd
Author: Davanum Srinivas <email address hidden>
Date: Mon Mar 31 19:14:57 2014 -0400

    Avoid pm-is-supported spam in logs

    Per the libvirt team, the only way to stop the spam in
    libvirtd logs is to install pm-utils package. Details are in:

    https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/994476

    Closes-Bug: #1274772
    Closes-Bug: #1297512

    Change-Id: Ia2f7a388470dcd8a3e2c12cf2980beccd65af94c

Changed in devstack:
status: In Progress → Fix Released
Tracy Jones (tjones-i)
Changed in nova:
status: In Progress → New
status: New → Triaged
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.