libvirt: xen: hypervisor driver fills log with internal errors after shutdown

[Stefan Bader]

This happens most notably when using virt-manager and leaving the console window open after shutdown. The problem is that the unified driver always calls out to several sub-drivers in sequence. After an instance is shut down, the open console window seems to do a query on the number of vcpus about every second.
The unified driver first calls to the hypervisor sub-driver which cannot find the domain id after shutdown (as it does not exist anymore). This is not really fatal and after returning -1, the unified driver passes the request on to the xend sub-driver which does succeed. So the logger internal error does not mean anything.

[Stefan Bader (smb)]

This change would prevent the flood of messages. I know this is a rather debatable change. Though I like to have rather no alarm error logged when there is nothing wrong.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libvirt - 0.9.8-2ubuntu15

---------------
libvirt (0.9.8-2ubuntu15) precise; urgency=low

  [ Stefan Bader ]
  * Use domain/status to check for inactive domains in the xend sub-
    driver. (LP: #929626)
  * Prevent the hypervisor sub-driver from logging an internal error
    just because it cannot find a certain domain when looking for
    the number of vcpus. (LP: #963006)
 -- Stefan Bader <email address hidden> Fri, 23 Mar 2012 11:38:24 +0100