qemu-anti-detection icon indicating copy to clipboard operation
qemu-anti-detection copied to clipboard

Published 20 hours ago • verified publisher icon zhaodice

cant install qemu 8.2

Open onionmansz opened this issue 10 months ago • 15 comments

can only upgrade to qemu 6.2 when i run kvm --version

onionmansz avatar Apr 01 '24 02:04 onionmansz

I don't know why you can only install low qemu version but you can try upgrade kernel or os version (or see what changs in my patch, make the low qemu version patch.)

zhaodice avatar Apr 01 '24 11:04 zhaodice

@zhaodice how to know patch applied properly?

onionmansz avatar Apr 13 '24 02:04 onionmansz

image

onionmansz avatar Apr 13 '24 04:04 onionmansz

I guess your kvm version doesn't support qemu? your system version may too old

zhaodice avatar Apr 13 '24 18:04 zhaodice

@zhaodice it's kvm version 6.2.0 and qemu 8.2.2.... and Ubuntu 22.04.4 LTS

onionmansz avatar Apr 13 '24 19:04 onionmansz

try qemu-system-x86_64, what's print?

zhaodice avatar Apr 14 '24 14:04 zhaodice

@zhaodice terminal doesnt print anything when typing that, and virtual machiner same thing

onionmansz avatar Apr 14 '24 14:04 onionmansz

@zhaodice terminal doesnt print anything when typing that, and virtual machiner same thing

I think your qemu doesn't install corrently. could you show step by setp from your compile and installing operation?

zhaodice avatar Apr 14 '24 14:04 zhaodice

@zhaodice do you want remote desktop info?

onionmansz avatar Apr 14 '24 14:04 onionmansz

@onionmansz, you won't get any output to the terminal, if the patch applied properly. Make sure your system is up-to-date. Make sure that you have an official installation of QEMU from your package manager, because that ensures that all runtime dependencies are installed. Did you blacklist the KVM modules or compiled a custom kernel without them? Otherwise I can only redirect you to the instructions in the README. I updated them just a few weeks ago and on the same Ubuntu version I think, so they should still be correct.

Samuil1337 avatar Apr 14 '24 17:04 Samuil1337

@Samuil1337 -- I did do an official installation, and did not blacklist anything, or compile a custom kernel. Happy to share the RDP for further investigation. Would be greatly appreciated.

onionmansz avatar Apr 14 '24 17:04 onionmansz

@zhaodice do you want remote desktop info?

I want you information with your input command&output from your operation to follow my project. It will help me to locate which step is error

zhaodice avatar Apr 15 '24 07:04 zhaodice

Ok @zhaodice what do you want me to run input and output? Just form the readme steps?

onionmansz avatar Apr 15 '24 12:04 onionmansz

Ok @zhaodice what do you want me to run input and output? Just form the readme steps?

yes, more is better.

zhaodice avatar Apr 15 '24 15:04 zhaodice

I encountered the same problem and found a solution.

The issue is that apparmor doesn't allow libvirtd to access /usr/local/bin by default, where the patched binaries are located.

This can be fixed by modifying /etc/apparmor.d/usr.sbin.libvirtd and adding /usr/local/bin/* PUx, after /usr/bin/* PUx,

After rebooting this should then be resolved.

0xfarcall avatar May 07 '24 12:05 0xfarcall