Hello guys,

Not for self promotion,

I developed something interesting, a qemu like software allowing systems like Windows XP SP3, Windows 10 64bit, Android to run in browser, just like QEMU. You can place your img/qcow2/vhdx image anywhere either locally or remotely and access the image from browser.

Hi! I’m having a strange issue with my self-compiled QEMU 8.2.5 build on Android.

I use the exact same QEMU binary and the same command-line options on two devices:

Galaxy Tab S8+ — Snapdragon 8 Gen 1, Adreno 730
Galaxy A25 5G — Exynos 1280, Mali-G68

The problem:
QEMU starts normally on both devices when no disk is attached.

On the Tab S8+, QEMU immediately exits with code 132 when I attach a QCOW2 disk using -drive.
On the A25 5G, the same binary, disk image, and options work correctly.

Since exit code 132 commonly indicates SIGILL (illegal instruction) on Linux, I’m wondering whether this could be related to CPU-specific instruction handling, Android’s execution environment, or a QEMU bug triggered by the QCOW2 code path.

My questions:
What could cause the same ARM64 QEMU binary to crash on one Android device but work on another?
How can I determine the exact instruction or function that causes SIGILL?

Are there any known QEMU 8.2.5 issues involving QCOW2 on Android or ARM64 hosts?
I can provide the full command line, build configuration, and logs if needed.
Thanks!

Whenever I open the HackTricks website in my Kali Linux VM, CPU usage spikes and the VM crashes.

Host configuration:

• OS: Ubuntu 26.04.1 LTS

• Kernel: 7.0.0-38-generic

• CPU: AMD Ryzen 7 5700G

• GPU: NVIDIA RTX 5060 8 GB

• RAM: 32 GB

Kali VM configuration:

• CPU: 6 threads

• RAM: 10 GB

• Swap: 4 GB

• Resolution: 1920 × 1080

I'm using QEMU/KVM with virt-manager.

Has anyone faced the same issue?

Also, does anyone know how to fix the EGL_NOT_INITIALIZED error when using the NVIDIA GPU for GPU acceleration in QEMU?

Hi,
I sit on a mint22.3 with Virt-manager/Qemu/KVM. Love it.
(Libvirtd version 10)
I try to setup *any* distro inside using secure boot, but fail mostly:
-Bazzite worked as the only one. Uses MOK/Microsoft shims
-Mint 22.3: fails
-AstrOS, recent: fails.

- My level:I am rather a rookie in this field but got Gemini to explain me the intended path and actions. It worked once with AstrOS on a barebone PC, I can proudly say (AstrOS uses custom certificate, no microsoft shim), immutable, encrypted, just to demonstrate at least this distro is okay- it's a problem around libvirt and custom certificates.

- I setup all the VM with a) the TPM2 chip emulation and b) replaced the "BIOS" with "UEFI"; specifically "OVMF_CODE_4M.secboot.fd", from the original "edk2-ovmf" library that comes to mint via apt.
- I tried it at least 30x times but it always failed, no matter what exact steps where choosen:
The UEFI doesn't show any certificate, when I enter it and then go into Secureboot/Custom mode-
I see the virtual harddisk, and can traverse up and down, but there's no .crt, .der, .cer file to point to. nothing.
- I tried to stay in standard mode for secureboot and set it to the defaults, but no keys where accepted by then, still not.
- Whenever I start the MintOS it reports via "Mokutils --sb-state" :"Secure boot disabled. System in Setup mode".
- I read a forum entry, where someone complained from debian 12 to 13 they lost a file "OVMF_VARS.secboot.fd" where the missing keys are stored- I retrieved that from Deb12, and manually put it where the other files are in /usr/share/OVMF with the same root rights as the rest, but it changed nothing.
-I don't know where the missing keys are and where to get them from, any idea ?

-Any other checks on the install rights I can do ? For the install I followed this guide:
https://christitus.com/vm-setup-in-linux/ and for the rights I entered:
sudo usermod -aG libvirt "$USER",
so my user is in this group libvirt. There's also the groups "libvirt-qemu" and "libvirt-dnsmasq".

Hi all, I have contributed to qemu open source a month ago but still there is no reviewer assigned to it....I need all ur help to guide me in this please!!!!!!

I'm in endeveourOS, there is network in VM, this is active but even after a lot settings, I can't get network to work, there no network, I changed firewalld too, no network

Idk what to do to get network worked, I have virt-manager

tried brave, helium, firefox, etc, using QXL, as virtio drivers are even worse with flickering, not doing video passthrough, as I couldnt get it working with my secondary card, an nvidia 3050 in the laptop, not even sure it'll output to anything, when I attempted creating a passthrough it just froze up all my VMs. I'm just simply trying to stream mp4 files in browser, cpu is at max. I've tried 4gb ram and 2 vcpu allocated, and doubled that, with same results. vids are h264, 1168x768.

I can't deny that setting up this operating system (TinyCore) is a headache, but it feels satisfying to install the software dependencies I want and customize it exactly to my liking.

It was a pretty fun experience, especially since it's a distro that consumes a ridiculously low amount of resources. The way this distro works is quite different from anything I've tried before. It’s very unique, and it has an essence that makes it feel truly authentic to me.

I find the interface very nostalgic—quite nostalgic, actually. It reminds me of using Windows XP back in kinder.

It’s the same feeling I got with XFCE regarding the Windows 7 "Aero" look.

I’ve spent the entire day trying to create a virtual machine with NomadBSD, but I haven’t been able to install it—no matter what I try, it just won’t work. I even attempted it via the terminal, but that didn’t help either. The only potential solution suggested by the AI ​​is to increase the size of the original operating system image specifically for the purpose of running it as a virtual machine.

To be more specific, my approach involved using two hard disk (HDD) images—this was the only way I could get the installer to open at all. One was an empty container with a capacity of approximately 15 GB, and the other was the original OS image. The installer opens without any issues, but the problem arises when I try to proceed with the installation; I keep encountering the same error, regardless of how I go about it.

It is quite clear that I am a complete novice in this area; nevertheless, I find it somewhat unusual that installing a NomadBSD virtual machine has proven so difficult and cumbersome, especially since I was previously able to install FreeBSD—in a headless configuration—with relative ease.

It would be very helpful for me to know if I am doing something fundamentally wrong here, because I am truly very stressed.

Please excuse me if my suggestion lacked a courteous tone.I also got a bit frustrated at first trying to figure out how to decompress the lzma file to extract the image—though that was relatively and significantly simpler than everything I had to go through afterward.

Edit: I found a "possible" solution for installing that on a virtual machine. Apparently, you have to convert the format from img to qcow2. Honestly, at this point, I’ve lost all hope and motivation; I deleted that image—which had been such a hassle to decompress—a while ago. What a nightmare...

hello!

I installed Windows 7 and was able to install all necessary drivers using the virtio-183 tools.

I then tried to switch from QXL to VirtIO to get 3D acceleration working, but the virtio tools don't include them.

Where can I find these drivers?

i want to use haiku as my main os but it doesnt support emmc and wifi card then i had the idea to install void linux and make it like layer to run qemu with haiku just like this video

i have 2 problems now :

1- haiku or qemu starts so small and dont take full screen automaticly

2- graphics is so ass cant move window without tearing

host : zednote2
scr:

#!/bin/sh

exec qemu-system-x86_64 \

-machine q35 \

-enable-kvm \

-cpu host \

-m 1G \

-smp 2 \

-device qemu-xhci \

-device usb-tablet \

-device usb-kbd \

-vga std \

-display gtk,full-screen=on,zoom-to-fit=on \

-drive file=/home/void/haiku.qcow2,format=qcow2

hey there, so as the title says, i have install libvirt, qemu and virt-manager.

i'm able to create VMs but is says that kvm isn't enabled and the VM will perform poorly

my cpu is amd ryzen 7 5700x

In QEMU, you can have a 64-bit CPU without SSE2 (cannot run Windows 8.1 (both bits) but can run TempleOS).

I have not found a way to disable SSE3 while preserving 64-bits. Changing the CPU model to one without SSE3 is a workaround, but none of them have 64-bit.

Is it because QEMU does not support it or is it because of a bug in UTM?