|
On 08/29/2012 03:26 PM, Wen Congyang
wrote:
Thanks a lot, I use managedsave and check domjobinfo success!At 08/29/2012 02:40 PM, Li, Chun Wen Wrote:Hi, all I test virsh comand "domjobinfo" on x86-i386 and PPC64 host. But Both get nothing. # virsh version Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 1.1.50 # virsh list Id Name State ---------------------------------------------------- 21 f16-ppc-qcow2 running 22 f16-blkiotune running 23 f16-device-attach running # virsh domjobinfo 21 Job type: None But I have run two jobs on domain 21 [root@localhost ~]# jobs [1]- Stopped top [2]+ Stopped vi install.log I searched the domjobinfo patch gave by Daniel P. Berrange, he said " This series introduces 2 new APIs to allow long running jobs to be monitored and cancelled. " Dose domjobinfo only monitor some special jobs in guest? Or does I miss something?The job is not in the guest. It is a job that operates the guest on the host side and may take long time, for example: dump, save, migrate. # virsh managedsave 27 --bypass-cache & [1] 57314 # virsh domjobinfo 27 Job type: Unbounded Time elapsed: 2601 ms Data processed: 161.611 MiB Data remaining: 312.422 MiB Data total: 1.000 GiB Memory processed: 161.611 MiB Memory remaining: 312.422 MiB Memory total: 1.000 GiB Thanks Wen CongyangThanks & Regards Kimi Li _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users |
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
