Hi Paolo, >Why would that be useful? Again, the mapping of the UUID is _not_ to a >PID, it is to a cgroup. There is no concept of a VM PID; you could >legitimately have I/O in a separate process than say the QEMU process, and >that I/O >process could legitimately reside in a separate blkcg than QEMU. >Agreed . >When I run ps -aef | grep <VMname > we got a pid. >ps -aef | grep mmkvm1 root 3627 1 0 04:20 ? 00:00:34 /usr/libexec/qemu-kvm -name testmmkvm1 -S >And I was talking about at the below one PIDS(3627) .And with the help of >these PIDS I was able to reach blkcg. >Correct me if iam going in a wrong direction. Also cross checked the same with the below comand cat /proc/3627/cgroup 10:hugetlb:/ 9:devices:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 8:cpuset:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope/emulator 7:blkio:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 6:freezer:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 5:perf_event:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 4:memory:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 3:net_cls:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope 2:cpu,cpuacct:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope/emulator 1:name=systemd:/machine.slice/machine-qemu\x2d7\x2dtestmmkvm1.scope Regards, Muneendra.
