Comment 12 for bug 1201938

I had previously reproduced this with a ppa build from an hourly upstream snapshot. I reported this upstream at https://www.redhat.com/archives/libvir-list/2013-July/msg01751.html

Today I can't reproduce this even in stock saucy.

libvirt hasn't been updated in the archive in the meantime. Could this have been a bug in one of the dependencies? Or am I missing a step? I have 2 vms running while virt-manager is running (locally) displaying guest and host cpu times.

Also was unable to reproduce this on a fedora 19 rackspace image.