Description of problem:
virt-manager does not update guest state properly after shutdown, machines show as running after they were shut down (and have shut down)
Version-Release number of selected component (if applicable):
gracefully shutdown a machine and wait for it to show as shut-off
Steps to Reproduce:
1. shutdown machine gracefully
3. check status
shows as running
should show as shut-off
root@susi-0:~/virt-manager# git bisect good
743dddf1b917fa1b6d26d645a13edfdc6ae98a36 is the first bad commit
Author: Cole Robinson <firstname.lastname@example.org>
Date: Sun Apr 10 18:26:40 2011 -0400
connection: Refactor _update_vms to be more like other polling
:040000 040000 40d9c0c9beb8eec31ff7010f57259ad67b225495 138658995a29d2791d3aad3f5f6eeba80a91c24c M src
2011-08-24 23:39:07,773 (engine:1048): Shutting down vm 'winxp1_susi1'.
2011-08-24 23:39:53,286 (domain:1514): Error reading disk stats for 'winxp1_susi1' dev 'hda': internal error Failed to read any block statistics for domain 52
2011-08-24 23:39:53,286 (domain:1515): Adding hda to skip list.
2011-08-24 23:39:53,286 (domain:1480): Error reading net stats for 'winxp1_susi1' dev 'vif52.0': internal error /proc/net/dev: Interface not found
2011-08-24 23:39:53,287 (domain:1481): Adding vif52.0 to skip list.
Created attachment 519939 [details]
what it looks like
Okay, I reproduced this issue and it looks like either a libvirt or xen bug that is exposed by that change in virt-manager. What we are doing should work from an API user perspective so one of those other packages is doing something wrong.
Duping to a bug where I provided a simple reproducer
*** This bug has been marked as a duplicate of bug 746007 ***