On Thu, Jul 14, 2016 at 16:35:37 +0200, Viktor Mihajlovski wrote: > Currently, the virVcpuInfo returned by virDomainGetVcpus() will always > report a state of VIR_VCPU_RUNNING for each defined domain vcpu even if > the vcpu is currently in the halted state. > > As the monitor interface is in fact reporting the accurate state, it is > rather easy to transport this information with the existing API. > > This is done by > - adding a new state of VIR_VCPU_HALTED > - adding a monitor function to pass back the halted state for the vcpus > - adding a new field to the private domain vcpu object reflecting the > halted state for the vcpu > - modifying the driver code to report the vcpu state based on the halted > indicator > - extending virsh vcpuinfo to also display the halted state > > The vcpu state is however not recorded in the internal XML format, since > the state can change asynchronously (without notification). I'm going to pick this up in my work-in-progress series of adding vCPU hot(un)plug using the new APIs in qemu and I'll let you know about the issues once I see how well it integrates since it is touching the same places. Peter -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list