Vibhu Prashar

Sure @rootfs Here is the screenshot of when 3 Kepler instances are deployed on OCP 4.14(VM) Kepler with `release-0.7.2` is deployed in `kepler-new` ns Kepler with `release-0.7.1` is deployed in...

@rootfs @marceloamaral Just wanted to know if the `latest` Kepler image addresses this issue?

@marceloamaral @sunya-ch @rootfs I could still see higher numbers reported by Kepler when `latest` release is deployed on the VM. Attached below is the comparison when Kepler with `latest`, `release-0.7.3`,...

Still could see a higher number reported by Kepler. Comparing `latest` `release-0.7.8` and `release-0.7.2` on VM 

Not sure about the GitHub action for Microshift but I have recently used Microshift for CI purposes and I use the default github-runners and run Microshift in a container as...

Attaching Kepler logs for reference: Kepler on BM: [kepler-bm.log](https://github.com/sustainable-computing-io/kepler/files/15218467/kepler-bm.log) Kepler on VM: [kepler.log](https://github.com/sustainable-computing-io/kepler/files/15218474/kepler.log)

cc: @rootfs

closing as the issue is addressed and fixed

reopening the issue as Kepler latest still reports the process name as incorrect:

``` ❯ pstree -p | grep qemu |-qemu-system-x86(110356)-+-{qemu-system-x86}(110367) | |-{qemu-system-x86}(110370) | |-{qemu-system-x86}(110371) | |-{qemu-system-x86}(110372) | |-{qemu-system-x86}(110373) | |-{qemu-system-x86}(110374) | |-{qemu-system-x86}(110375) | |-{qemu-system-x86}(110377) | `-{qemu-system-x86}(2178213) ```