17.08.2024 15:33, bblinux wrote:
Here is a way I tried to replicate in a more isolated environment:
# mmdebstrap --variant minbase --include qemu-system-x86 unstable
rootfs-unstable
# chroot rootfs-unstable
(chroot)# qemu-system-x86_64 --version
QEMU emulator version 9.0.2 (Debian 1:9.0.2+ds-4)
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
(chroot)# qemu-system-x86_64 -netdev bridge,id=n1
- Locks up
It works (or fails) for me exactly as per your "stable" variant:
/tmp# mmdebstrap --variant minbase --include qemu-system-x86 unstable sid
I: automatically chosen mode: root
I: chroot architecture amd64 is equal to the host's architecture
...
I: success in 9.3555 seconds
/tmp# chroot sid
/# qemu-system-x86_64 -netdev bridge,id=n1
failed to parse default acl file `/etc/qemu/bridge.conf'
qemu-system-x86_64: -netdev bridge,id=n1: bridge helper failed
/# qemu-system-x86_64 -netdev tap,id=n1
qemu-system-x86_64: -netdev tap,id=n1: could not open /dev/net/tun: No such
file or directory
/#
exit
/tmp# cd sid
/tmp/sid# mount --bind /dev dev
/tmp/sid# chroot .
/# qemu-system-x86_64 -netdev tap,id=n1
W: /etc/qemu-ifup: not doing any bridge processing: neither ip nor brctl
utility not found
qemu-system-x86_64: warning: netdev n1 has no peer
VNC server running on 127.0.0.1:5900
^C
# mmdebstrap --variant minbase --include qemu-system-x86 stable rootfs-stable
# chroot rootfs-stable
(chroot)# qemu-system-x86_64 --version
QEMU emulator version 7.2.11 (Debian 1:7.2+dfsg-7+deb12u6)
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
(chroot)# qemu-system-x86_64 -netdev bridge,id=n1
qemu: module ui-ui-gtk not found, do you want to install
qemu-system-gui package?
qemu: module ui-ui-sdl not found, do you want to install
qemu-system-gui package?
failed to parse default acl file `/etc/qemu/bridge.conf'
qemu-system-x86_64: -netdev bridge,id=n1: bridge helper failed
- The error is expected
Yes, this is what I see for stable as well. And exactly the same happens
for unstable too.
There's one significant difference between our systems though: you run
Linux 6.10.3-amd64 while mine is 6.1.0-23-amd64. Lemme try 6.10.3 too..
..nope, with 6.10.3 it works exactly the same way. Works fine with bridge
or tap network.
Please run your hanging qemu under strace (strace -f) and see what it is
doing.
This is a very basic networking setup - maybe not bridge directly, but
tap is for *sure*, it is the most common setup used by many people. If
this problem were common, it would be reported very loudly already, by
multiple people. So far, it only affects your system(s). I'm just
thinking out loud, trying to collect what we know.
BTW, what's your CPU? It looks like I don't have machine with an Intel
CPU around anymore (where I can experiment with the kernel anyway).
Thanks,
/mjt
