-
Notifications
You must be signed in to change notification settings - Fork 25
gdb.io.open: Cannot connect to host #44
Comments
hi @Alibm73 , the vmidbg server is listening by default on so you don't need the guest IP address, or for the guest to have a network card at all. You want to connnect so Also, remember to run |
@Wenzel
|
How come you have no Maybe because you are using a Volatility JSON profile, and i'm assuming a data structure that is only present in Rekall JSON profiles ? 🤔 Can you paste the profile in a Gist please ? |
@Wenzel I didn't know it doesn't work with volatility, My first profile was made with volatility and then converted to JSON profile. P.S: I know I'm very new to this, but if you don't mind I love to help you with implementing the |
I'm glad to see that
The software breakpoints are already implemented in pyvmidbg at this point. |
@Wenzel yea, that was a mistake from my part. what i really meant was i would like to help you (specially learn from you) on future developments, IF that is ok with you. I really don't know how can I really help you 😄 but i would definitely try 💪
there are no symbols, I should create pdb for ntoskrnl.exe, right?? currently My rekall profile is for ntkr nlmp.pdb |
would be glad to have some help building the future of
oba loads a binary, not rekall symbols. |
Hi @Wenzel
I tried to connect to the gdbserver but it doesn't work.
even my firewalls are off and still it's not connecting.
I don't know if it makes any difference but I'm connecting to my quest vm with vncviewer:
note: instead of
gvncviewer 192.168.1.9::5900
I can usegvncviewer localhost
tooAt last this is my vm config, I changed the number of vcpu and max cpus to 1 as it was in the limitation section:
And this is the Error:
The text was updated successfully, but these errors were encountered: