Cannot start/migrate VM after libvirt update

Solution In Progress - Updated -

Issue

  • Cannot start or migrate VM. Libvirt shows the error below:
libvirtError: internal error got wrong number of vCPU pids from QEMU monitor. got 5, wanted 6
  • While trying to migrate/start a VM to a host with libvirt-0.10.2-29.el6_5.7 it will fail with the following message in the vdsm.log file
Thread-1635507::ERROR::2014-05-07 14:38:42,667::vm::338::vm.Vm::(run) 
vmId=`f09ca659-941f-4743-bcaa-7b1fc19465c8`::Failed to migrate
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 324, in run
    self._startUnderlyingMigration()
  File "/usr/share/vdsm/vm.py", line 406, in _startUnderlyingMigration
    None, maxBandwidth)
  File "/usr/share/vdsm/vm.py", line 845, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 76, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1178, in migrateToURI2
    if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self)
libvirtError: internal error got wrong number of vCPU pids from QEMU monitor. got X, wanted X+Y

Environment

  • Red Hat Enterprise Linux 6 or Red Hat Enterprise Virtualization 3.x.
  • libvirt version 0.10.2-29.el6_5.7 or later.
  • qemu-kvm or qemu-kvm-rhev version 0.12.1.2-2.415.el6_5.8 or earlier.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.