8000 Install on fedora ublue distributions · Issue #81 · zhaodice/qemu-anti-detection · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Install on fedora ublue distributions #81

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.

Sign up for GitHub

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

Jump to bottom
Open
Cm4nXD opened this issue Jun 4, 2024 · 2 comments
Open

Install on fedora ublue distributions #81

Cm4nXD opened this issue Jun 4, 2024 · 2 comments

Comments

@Cm4nXD
Copy link
Cm4nXD commented Jun 4, 2024

How would I go about using this patch with something like fedora bazzite?
@Samuil1337
Copy link
Contributor

I have never used Fedora based distributions, but the QEMU wiki says that these are the dependencies necessary to build it (obviously keep an installation of the QEMU package, so you don't miss any runtime dependencies):
dnf install git glib2-devel libfdt-devel pixman-devel zlib-devel bzip2 ninja-build python3

It also seems like your distro is atomic meaning that most of the (/) directory is read-only to users or could be replaced by an update, so installing qemu to /usr/local/bin (default of make install) might not work. I would try compiling it using just make in your home folder and changing the ownership (0:0) and permissions (755) for security reasons. Then I would change the emulator in your Libvirt domain XML to the build dir:

<domain>
  <!-- other code -->
  <devices>
    <emulator>/home/user/path/to/qemu/build/qemu-system-x86_64</emulator>
  </devices>
</domain>

@Cm4nXD
Copy link
Author
Cm4nXD commented Jun 15, 2024

So to anyone else who stumbles upon this, I found it easier to spin up a specific distrobox container based on the same version of fedora (non ublue atomic etc) that i used to compile it.

and then I had issues with the default libvirt group having permission to acess my users home directory, and rather then open up the permissions of my directory I simply threw it in a new directory made for this purpose in /home/

that allowed libvirt to execute the binary after i set ownership 0:0 and permissions 755

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Cm4nXD @Samuil1337
0