[opensuse-factory] Qemu 4.1. and TW
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image. This my command line: qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0 Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?) Suggestions? --- Frans. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 12 Nov 2019 01:58:57 PM CST, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
Hi I have my br0 and tap0 configured in YaST, then I use; switch=br0 tapdev=tap0 ip link set $tapdev master $switch wicked ifup $tapdev In my case I don't worry about a down script... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20191110 | GNOME Shell 3.34.1 | 5.3.8-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 3 days 14:21, 2 users, load average: 0.69, 1.09, 1.41 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12-11-2019 14:06, Malcolm wrote:
On Tue 12 Nov 2019 01:58:57 PM CST, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
Hi I have my br0 and tap0 configured in YaST, then I use;
switch=br0 tapdev=tap0 ip link set $tapdev master $switch wicked ifup $tapdev
In my case I don't worry about a down script...
Great, but my command line works under 15.1 and results in no network under the past summer versions of TW. I don't use Yast to setup virtual machines and as you see, I have tap0 and br0 too. So, what is different from your command line? --- Frans. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 12 Nov 2019 03:00:27 PM CST, Frans de Boer wrote:
On 12-11-2019 14:06, Malcolm wrote:
On Tue 12 Nov 2019 01:58:57 PM CST, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
Hi I have my br0 and tap0 configured in YaST, then I use;
switch=br0 tapdev=tap0 ip link set $tapdev master $switch wicked ifup $tapdev
In my case I don't worry about a down script...
Great, but my command line works under 15.1 and results in no network under the past summer versions of TW.
I don't use Yast to setup virtual machines and as you see, I have tap0 and br0 too. So, what is different from your command line?
--- Frans.
Hi Firewall maybe? I don't run it on the desktop machine. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20191110 | GNOME Shell 3.34.1 | 5.3.8-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 3 days 15:56, 2 users, load average: 2.59, 2.35, 1.54 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12-11-2019 15:40, Malcolm wrote:
On Tue 12 Nov 2019 03:00:27 PM CST, Frans de Boer wrote:
On 12-11-2019 14:06, Malcolm wrote:
On Tue 12 Nov 2019 01:58:57 PM CST, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
Hi I have my br0 and tap0 configured in YaST, then I use;
switch=br0 tapdev=tap0 ip link set $tapdev master $switch wicked ifup $tapdev
In my case I don't worry about a down script...
Great, but my command line works under 15.1 and results in no network under the past summer versions of TW.
I don't use Yast to setup virtual machines and as you see, I have tap0 and br0 too. So, what is different from your command line?
--- Frans.
Hi Firewall maybe? I don't run it on the desktop machine.
Nope, have tried that too. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue 12 Nov 2019 09:28:31 PM CST, Frans de Boer wrote: <snip>
So, what is different from your command line? <snip> Hi I use UEFI, gpu passthrough and manually start the tap0 device...
qemu-system-x86_64 \ -m 4G \ -cpu host,kvm=off \ -smp 4,sockets=1,cores=2,threads=2 \ -rtc clock=host,base=utc \ -serial none \ -parallel none \ -vga none \ -nographic \ -usb \ -device usb-host,vendorid=0x05af,productid=0x0808 \ -device vfio-pci,host=03:00.0 \ -device vfio-pci,host=03:00.1 \ -drive id=disk0,if=virtio,cache=none,format=raw,file=/var/lib/libvirt/images/os151passthru.raw \ -drive if=pflash,format=raw,file=/usr/share/qemu/ovmf-x86_64-opensuse-4m-code.bin \ -machine type=pc-q35-4.0,accel=kvm,kernel_irqchip=on \ -nic tap,ifname=tap0,script=no,downscript=no -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20191111 | GNOME Shell 3.34.1 | 5.3.9-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 0:04, 2 users, load average: 4.39, 3.30, 1.45 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, This really is a support question please use the support list instead opensuse-support@opensuse.org On 11/12/19 11:28 PM, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback
configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 12-11-2019 21:50, Simon Lees wrote:
Hi,
This really is a support question please use the support list instead opensuse-support@opensuse.org
On 11/12/19 11:28 PM, Frans de Boer wrote:
I can't get Qemu 4.1.0 to make a network connection using Win 10 as a client under TW. Qemu 3.1.1.1 works fine under TW. The 4.1 under under 15.1 works also. All with the same image.
This my command line:
qemu-system-x86_64 -snapshot -name telewerken -cpu phenom -smp cores=2,threads=1,sockets=1 -enable-kvm -machine type=q35,accel=kvm -m 3072 -soundhw hda -net nic,model=virtio-net-pci,macaddr=52:54:63:1f:a0:00 -net tap,ifname=tap0,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -display gtk -rtc clock=host,base=localtime -boot order=c -usb -device usb-tablet -drive file=./telewerken.raw,format=raw,index=0,media=disk,if=virtio,cache=writeback
configuring qemu network with bridge for tap0 qemu-ifdown: Removing tap0 from Bridge br0 + sudo /sbin/tunctl -d tap0
Works already several years under TW,, 15.1 and pevious versions. It stopped working since the end of the summer when switching to kernel 5.1+(?)
Suggestions?
--- Frans.
As it turns out, it was the firewall after all. It was not the change in kernel an update at the beginning of October.
Long story short, see the snipped I got from someone - not sure if I can mention his name: [opensuse] tumbleweed update - firewalld blocking qemu-guests from 05.10.2019 there was a different between the forwarding of the network at the host-system updated tumbleweed from: 20190607 -> 20191002 before it was working, after not. you need after update: (will be autogenerated if you follow the link below) /etc/firewalld/direct.xml <?xml version="1.0" encoding="utf-8"?> <direct> <passthrough ipv="ipv4">-I FORWARD -i br0 -j ACCEPT</passthrough> <passthrough ipv="ipv4">-O FORWARD -i br0 -j ACCEPT</passthrough> </direct> this file was not needed before: https://superuser.com/questions/990855/configure-firewalld-to-allow-bridged-... (by the way, maybe you need something similar also for ipv6) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2019-11-13 at 21:13 +0100, Frans de Boer wrote:
/etc/firewalld/direct.xml
<?xml version="1.0" encoding="utf-8"?> <direct> <passthrough ipv="ipv4">-I FORWARD -i br0 -j ACCEPT</passthrough> <passthrough ipv="ipv4">-O FORWARD -i br0 -j ACCEPT</passthrough> </direct>
"iptables -O" ? Seeing this for the first time. I believe you could do this in a more firewalld-ish manner, without resorting to direct rules which should be last resort thing when you use firewalld. firewalld supports both masquerading and port forwarding. Look at the firewalld man page. Martin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
participants (4)
-
Frans de Boer -
Malcolm -
Martin Wilck -
Simon Lees