Re: [libvirt-users] What does cpu_time returned by virDomainGetCPUStats mean?

On 04/16/2012 09:15 PM, Zhihua Che wrote: That's a forceful shutdown - it removes the virtual power cord, and always works, but may leave your disks in a state that requires fsck to recover. shutdown requires the guest to understand an ACPI power request (not all guests do), or to have a guest agent installed (even fewer guests have qemu_ga installed, as it is still quite new). But when it does work, it is nicer, because it lets the guest shut down gracefully. 6 seconds active use attributed to cpu0, 5 seconds on cpu1 5 seconds on each cpu. Yes, the values reset for you, and your testing happened to time the guest with about the same amount of usage time between your two starts and queries. You'll notice much more impressive numbers if you let the guest run for 10 minutes, then query, then restart, then query right away. They are merely kernel counters of how many nanoseconds of processor time has been attributed to the cgroup owning the qemu process since the cgroup was created. A qemu process is created each time you boot the guest from scratch, and 'virsh destroy' followed by 'virsh start' is indeed sufficient to start the guest from scratch. Technically, a cgroup can own multiple pids, so distinct pids is not always a guarantee of distinct cpuacct numbers. However, libvirt does indeed create a new cgroup for each qemu pid, so in this instance, yes, a different qemu pid should mean that the numbers started from scratch. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org