Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Searching for apex process... Init with qemu connector... Can't create qemu connector Init with kvm connector... Can't create kvm connector Quitting #37

Open
qingchan3366 opened this issue May 26, 2024 · 10 comments

Comments

@qingchan3366
Copy link

Searching for apex process...
Init with qemu connector...
Can't create qemu connector
Init with kvm connector...
Can't create kvm connector
Quitting

@albatror
Copy link

Look on build folder if you see the 3 lib (.so) for qemu, kvm and win32, if you dont see them, just put them manually in the build folder then restart.

@pplegends
Copy link

@albatror can i use your fork in single gpu passthrough?
what are you using for obfuscate Client.exe and Overlay.exe file?
thanks

@albatror
Copy link

yes you can use it, it not depending about 1 or 2 gpu and to obfuscate files yo can use THEMIDA(64) or VMprotect for example or any soft like this

@pplegends
Copy link

thank you so much, ill try it.

@Harvey518
Copy link

@albatror
hey,i put the 3lib(.so) in the build folder and it still show me this
Searching for apex process...
Init with qemu connector...
Can't create qemu connector
Init with kvm connector...
Can't create kvm connector
Quitting
How can i solve this?

@albatror
Copy link

hi, have you tried :
curl --proto '=https' --tlsv1.2 -sSf https://sh.memflow.io | sh

@Harvey518
Copy link

Harvey518 commented Sep 23, 2024

hi, have you tried : curl --proto '=https' --tlsv1.2 -sSf https://sh.memflow.io | sh

already use your fork and try this. Here is what I tried:

  • updated the libraries in the ‘memflow_lib’ folder from the memflow github
    I use memflow github stable branch
  • then built the cheat and solved the compilation errors
    build your fork and use the 'memflow_lib' in first step and build it successfully.
  • using the memflowup automated script (curl --proto ....) and use memflowup install the all connectors in development Channel.
    after finishing this i run Apex_dma and it failed again.

@albatror Can you give me your dc or something else? I have got stuck in this problem for almost a week and going to be mad.

@albatror
Copy link

I apologize for my mistake dude (i'm fucking dumb), i just reinstall everything to test it from nothing on my new computer and
just saw the diff between my local repo and the one on github.
I will update my repo to fix this soon (working on PDB/CR3 actually).
I invite you to :
Delete memflow_lib folder in adkv/apex_dma
Donwload repo from MisterY52, copy memflow_lib folder to adkv/apex_dma
Run build.sh and normally it will be good.
Tell me if it work for you.

@Feilink1
Copy link

Feilink1 commented Dec 16, 2024

Hi @albatror, I am having the same issue, I followed the instructions in your Readme section and copied MisterY52 memflow_lib folder to adkv/apex_dma, ran the install_memflow script then built apex_dma. It keeps giving me

Searching for apex process...
Init with qemu connector...
Can't create qemu connector
Init with kvm connector...
Can't create kvm connector
Quitting

Btw I had to change in the build.sh script memflow_ffi_win32 to memflow_ffi to make the build work. I need your help, thank you in advance. Kind regards

@albatror
Copy link

albatror commented Dec 18, 2024

Have you followed all steps ?

Download sources from there *.zip or git
Extract it
Install Cargo & Rust with the famous curl https://sh.rustup.rs/ -sSf | sh
Install memflow with the famous curl --proto '=https' --tlsv1.2 -sSf https://sh.memflow.io/ | sh
Compile with the build.sh to see if any errors, if errors, fix it/them then redo build.
When build is ok without errors, Download from https://github.com/albatror/memflow/blob/main/install_memflow.sh
Make the script executable, Edit it, Read and Save.
Run it. You will see if its OK in the console :) then you will see in /apex_dma/memflow_lib/ 2 new folders :
memflow-kvm
memflow-qemu
Go back to rebuild the complete sources.

hope it will help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants