libvmi process-list error

[helpingKVM-VMI]

I was able to successfully run the kvm-vmi test program. Therefore, I tried to run vmi-process-list by introducing libvmi at the end of the sentence. But I can't start it.

I have completed the process exactly as shown in the image.
Probably go to the rest of the LibVMI docs, but this might be an error because you're doing something different from what the author thought.

Enable GDB access to your KVM VM.This is done by adding'-s' to the VM creation line or, by modifying the VM XML definition used by libvirt as follows:

Change:

to: Add:

qemu:commandline
<qemu:arg value='-s'/>
</qemu:commandline>
under the level of the XML.

I believe this is what I do, but if not, please let me know. Thank you.

[Wenzel]

Hi,

the libvmi documentation about KVM should not be used, as it reference the legacy kvm driver.
you don't need that -s command line for GDB access.

your vmi-process-list binary should take an extra kvmi socket as parameter, just like the kvmi test

[helpingKVM-VMI]

@Wenzel
Hello.
I deleted the -s command because it is unnecessary.

I tried to execute as follows with reference to the person who raised the problem before, but I am getting an error like the image.

I don't know what the cause is.
Can you tell me Thank you.

[Wenzel]

I don't know either.
You need to enable libvmi debug output

[helpingKVM-VMI]

@Wenzel
I think this problem is the closest one from past errors.
libvmi example process-list error #44
At this time, I am changing the program to increase the waiting time at the end, but do you have any idea which file is being changed?

[helpingKVM-VMI]

Also, I would like to see the error content with debugging enabled, but it does not display properly because of the bad way.
We apologize for the inconvenience, but please show us.
Thank you.

[Wenzel]

Also, I would like to see the error content with debugging enabled, but it does not display properly because of the bad way.
I don't understand what you mean.

Toggle the debug output by rebuilding libvmi:
cmake -DVMI_DEBUG=__VMI_DEBUG_ALL ..

[helpingKVM-VMI]

@Wenzel
I ran the command that you told me to enable debugging.

After that, I did vmi-process-list, but it seems that the debug result is not displayed like the image.

Please let me know if you still have something to do.
Thank you.

[Wenzel]

You don't need to run cmake as sudo.

Did you rebuild and reinstall libvmi ?

[helpingKVM-VMI]

Yes.
I am trying the process in the first image again and see if I can debug it.

After this, I am trying to start the program by typing the debug command that you taught me.
However, debug processing is not performed as in the previous time, and only the error content is displayed. Is there anything else I need to do after doing a sudo make install?

[Wenzel]

Mayne you enabled the ENV_DEBUG option, and the debugging will only be triggered by exposing LUBVMI_DEBUG=1