Am Samstag, 19. Oktober 2019, 23:00:06 CEST schrieb Frans de Boer:
LS,
I tried to use Qemu 4.1. under Tumbleweed, but the client does not get an IP address. Compiled it myself, same result.
Tried to compile Qemu 3.1 series, but all failed during compile with the message: (loadable library and perl binaries are mismatched (got handshake key 0xde00080, needed 0xce00080)
Compiling and using the 3.1.x and 4.1 version under Opensuse 15.1 is no problem. Except when using 4.1 and wanting to use spice where there is only a very old version available under 15.1.
So, the problem must be in the Tumbleweed distribution, which somehow blocks Qemu 4.1 networking or disallows compiling Qemu 3.1 series.
Suggestions?
No solution to your problem, but libvirt of TW 20191014 is doing just fine here, including networking: libvirt-daemon-driver-qemu-5.7.0-1.1.x86_64 qemu-4.1.0-1.1.x86_64 qemu-block-curl-4.1.0-1.1.x86_64 qemu-block-rbd-4.1.0-1.1.x86_64 qemu-ipxe-1.0.0+-1.1.noarch qemu-ksm-4.1.0-1.1.x86_64 qemu-kvm-4.1.0-1.1.x86_64 qemu-linux-user-4.1.0-1.1.x86_64 qemu-ovmf-x86_64-201908-1.1.noarch qemu-seabios-1.12.1-1.1.noarch qemu-sgabios-8-1.1.noarch qemu-tools-4.1.0-1.1.x86_64 qemu-ui-curses-4.1.0-1.1.x86_64 qemu-ui-gtk-4.1.0-1.1.x86_64 qemu-ui-sdl-4.1.0-1.1.x86_64 qemu-vgabios-1.12.1-1.1.noarch qemu-x86-4.1.0-1.1.x86_64 Here's the part of nic config from a typical qemu run: -netdev tap,fd=38,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:xx:xx:xx,bus=pci.0,addr=0x3 and the network config: <network connections="1"> <name>default</name> <uuid>ef7f738c-86fe-43df-a1b6-xxxxxxxxxxxx</uuid> <forward mode="nat"> <nat> <port start="1024" end="65535"/> </nat> </forward> <bridge name="virbr0" stp="on" delay="0"/> <mac address="52:54:00:xx:xx:xx"/> <ip address="192.168.122.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.122.2" end="192.168.122.254"/> </dhcp> </ip> </network> Using it with 15.0 JeOS and Tails here, and really happy to be able to configure everything via GUI. ;-) Since you compile yourself, you're in for many issues, that stem from manual installations, but it's most definitely a configuration issue (that might be related to libvirt's evolution). You might consider trying virt-manager after a full clean-up. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org