On Wed, Jan 24, 2018 at 10:56:26AM -0500, Geneviève Bastien wrote: > On 2018-01-23 12:21 PM, Stefan Hajnoczi wrote: > > On Fri, Jan 19, 2018 at 03:03:25PM -0500, Genevieve Bastien wrote: > >> I'm tracing kvm guests and their host and an issue we have is to > >> identify which host process corresponds to which guest trace so we can > >> follow the state of the virtual cpu on the host. > > There are uevents for the VM lifecycle that include the PID. Please see > > Linux commit 286de8f6ac9202f1c9012784639156c6ec386eb8 & > > fdeaf7e3eb37c6dbc4b4ac97dbe1945d239eb788. > > > > Did you check if these are appropriate for your use case? > Thanks for the hint, I didn't know about those. But the uevents are only > for the host right? There is no specific value in debugfs for guest. I'm not sure I understand the question. Uevent are emitted on the host. Given the PID field, it should be possible to correlate them to a specific guest (e.g. by looking at information from the user or VM management tools, or simply by looking at /proc/$PID/cmdline for the QEMU -name argument that can be used to identify guests on the host side). Stefan
Attachment:
signature.asc
Description: PGP signature
