Mathieu Tarral

Hi @ikelos, thanks for the feedback. I tried removing my volatility cache, didn't work. I tried running volatility with `-vvvv`, but I didn't have more debug infos I downloaded your...

@ikelos I created a Dockerfile for you to repro the bug; ~~~Dockerfile FROM ubuntu:20.04 RUN apt-get update && apt-get install -y git python3 python3-dev python3-venv RUN git clone https://github.com/volatilityfoundation/volatility3 RUN...

Thanks for the report, I haven't tested on Ubuntu 20.04. Usually this error means that GDB was expecting more registers, meaning that we sent only 32 bits and not 64...

Hi, > I've been looking for such capability for a while, and this project seems really close. You are looking for a guest-aware GDB stub. Yes, you are in the...

I just updated the README, adding a section about the state of VMI support in hypervisors today.

@pwnosaur Update: pyvmidbg now supports KVM (non-Xen) related: https://github.com/Wenzel/pyvmidbg/pull/40

It depends what you mean by QEMU: - full virtualization (QEMU/KVM) -> yes :heavy_check_mark: - binary translation (QEMU only) -> no :red_circle:

hi @Alibm73 , the vmidbg server is listening by default on `localhost`: `127.0.0.1`. The whole point of debugging from the hypervisor is that you don't need in guest vm tools...

How come you have no `$CONSTANTS` in your rekall profile ? Maybe because you are using a Volatility JSON profile, and i'm assuming a data structure that is only present...

I'm glad to see that `pyvmidbg` works for you, congrats ! > I know I'm very new to this, but if you don't mind I love to help you with...