this problem is supposed to be fixed in the next qemu release, which might or might not be anytime soon.
in the meantime, and since 2 weeks, i can’t launch my VM with GPu passthrough, and i can’t find any older version of qemu on the tumbleweed repos that would allow me to do a downgrade.
i’m just stuck since 2 weeks with no way of running my VM.
i’ve been extremely disapointed by tumbleweed recently,
i’ve encountered a ton of problems since months, from visual glitches solved by mesa updates (taking a few days to get fixed), to a broken breeze dark theme (happening since ~May and still not fixed)
sorry for the rant but this had to be said.
if anyone has a solution for this problem, please let me know
yeah, i’ve tried removing the problematic arguments, but whenever i start the VM with virsh or virt-manager, the args come back and the error appears, some people mentionned that workaround that you’ve mentionned but it’s no longer working
@kyral it’s an option as always to downgrade, you could use tumbleweed-cli, or just pick a snapshot from history https://download.opensuse.org/history/ and rollback the relevant packages. I only have the gpu passthrough as a test, not critical for me, so can live without the need.
well as far as the history goes, the only qemu package i found, is aready part of the broken builds, i tried downgrading from there but it doesn’t fix the issue, this problem appeared on qemu 9.0
well i’ve tried the latest qemu 9.0.2 that fixes the deprecated topo error, (from the Virtualization Staging repo)
the error no longer happens, but i’m still getting this weird error when i try to run the vm with virsh:
qemu-system-x86_64: GLib: ../glib/gmem.c:177: failed to allocate 18446744065192157996 bytes
it tries to allocate 1,84467E+07 terabytes, which makes absolutely no sense