[Qemu-devel] [Bug 1843073] [NEW] Network loose connection for long time under light load guest winxp64 with virtio on i5-8350U
Public bug reported: I have issue with qemu and winxp guest on i5-8350U. First of all, if i run same vm with same config on i5 9660k i do not see such issue. Both pc have ubuntu 19.04 x86_64. Guest is winxp64, tried: 1) stable guest drivers, latest drivers 2) all virtio, only network r18169, bridge to host eth0, just default virbr0. 3) qemu from ubuntu 19.04, and tried latest libvirt and qeumu compiled from sources. 4) tried zram as block device I need really lightweight win to run only one app, so win7 and win10 is not an option. winxp 93921ab3-222a-4e5f-89c4-36703fc65cb4 http://libosinfo.org/xmlns/libvirt/domain/1.0";> http://microsoft.com/win/xp"/> 8388608 8388608 4 hvm destroy restart destroy /usr/local/bin/qemu-system-x86_64 ** Affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1843073 Title: Network loose connection for long time under light load guest winxp64 with virtio on i5-8350U Status in QEMU: New Bug description: I have issue with qemu and winxp guest on i5-8350U. First of all, if i run same vm with same config on i5 9660k i do not see such issue. Both pc have ubuntu 19.04 x86_64. Guest is winxp64, tried: 1) stable guest drivers, latest drivers 2) all virtio, only network r18169, bridge to host eth0, just default virbr0. 3) qemu from ubuntu 19.04, and tried latest libvirt and qeumu compiled from sources. 4) tried zram as block device I need really lightweight win to run only one app, so win7 and win10 is not an option. winxp 93921ab3-222a-4e5f-89c4-36703fc65cb4 http://libosinfo.org/xmlns/libvirt/domain/1.0";> http://microsoft.com/win/xp"/> 8388608 8388608 4 hvm destroy restart destroy /usr/local/bin/qemu-system-x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1843073/+subscriptions
[Qemu-devel] [Bug 1843073] Re: Network loose connection for long time under light load guest winxp64 with virtio on i5-8350U
Ping at the load moment: ping 192.168.152.25 PING 192.168.152.25 (192.168.152.25) 56(84) bytes of data. 64 bytes from 192.168.152.25: icmp_seq=1 ttl=128 time=0.300 ms 64 bytes from 192.168.152.25: icmp_seq=2 ttl=128 time=0.495 ms 64 bytes from 192.168.152.25: icmp_seq=3 ttl=128 time=0.442 ms 64 bytes from 192.168.152.25: icmp_seq=4 ttl=128 time=0.520 ms 64 bytes from 192.168.152.25: icmp_seq=5 ttl=128 time=0.558 ms 64 bytes from 192.168.152.25: icmp_seq=6 ttl=128 time=0.623 ms 64 bytes from 192.168.152.25: icmp_seq=7 ttl=128 time=0.668 ms 64 bytes from 192.168.152.25: icmp_seq=8 ttl=128 time=0.574 ms 64 bytes from 192.168.152.25: icmp_seq=9 ttl=128 time=0.390 ms 64 bytes from 192.168.152.25: icmp_seq=10 ttl=128 time=363 ms >From 192.168.152.1 icmp_seq=29 Destination Host Unreachable >From 192.168.152.1 icmp_seq=30 Destination Host Unreachable >From 192.168.152.1 icmp_seq=31 Destination Host Unreachable >From 192.168.152.1 icmp_seq=32 Destination Host Unreachable >From 192.168.152.1 icmp_seq=33 Destination Host Unreachable >From 192.168.152.1 icmp_seq=34 Destination Host Unreachable >From 192.168.152.1 icmp_seq=36 Destination Host Unreachable >From 192.168.152.1 icmp_seq=39 Destination Host Unreachable >From 192.168.152.1 icmp_seq=40 Destination Host Unreachable 64 bytes from 192.168.152.25: icmp_seq=11 ttl=128 time=33151 ms 64 bytes from 192.168.152.25: icmp_seq=12 ttl=128 time=32137 ms >From 192.168.152.1 icmp_seq=41 Destination Host Unreachable >From 192.168.152.1 icmp_seq=42 Destination Host Unreachable >From 192.168.152.1 icmp_seq=43 Destination Host Unreachable >From 192.168.152.1 icmp_seq=44 Destination Host Unreachable >From 192.168.152.1 icmp_seq=45 Destination Host Unreachable >From 192.168.152.1 icmp_seq=46 Destination Host Unreachable >From 192.168.152.1 icmp_seq=47 Destination Host Unreachable >From 192.168.152.1 icmp_seq=48 Destination Host Unreachable >From 192.168.152.1 icmp_seq=49 Destination Host Unreachable >From 192.168.152.1 icmp_seq=50 Destination Host Unreachable 64 bytes from 192.168.152.25: icmp_seq=13 ttl=128 time=39259 ms 64 bytes from 192.168.152.25: icmp_seq=14 ttl=128 time=38235 ms 64 bytes from 192.168.152.25: icmp_seq=15 ttl=128 time=37211 ms 64 bytes from 192.168.152.25: icmp_seq=16 ttl=128 time=36187 ms 64 bytes from 192.168.152.25: icmp_seq=17 ttl=128 time=35163 ms 64 bytes from 192.168.152.25: icmp_seq=18 ttl=128 time=34139 ms 64 bytes from 192.168.152.25: icmp_seq=19 ttl=128 time=33115 ms 64 bytes from 192.168.152.25: icmp_seq=20 ttl=128 time=32091 ms 64 bytes from 192.168.152.25: icmp_seq=21 ttl=128 time=31068 ms 64 bytes from 192.168.152.25: icmp_seq=22 ttl=128 time=30044 ms 64 bytes from 192.168.152.25: icmp_seq=23 ttl=128 time=29020 ms 64 bytes from 192.168.152.25: icmp_seq=24 ttl=128 time=27996 ms 64 bytes from 192.168.152.25: icmp_seq=25 ttl=128 time=26968 ms 64 bytes from 192.168.152.25: icmp_seq=26 ttl=128 time=25948 ms 64 bytes from 192.168.152.25: icmp_seq=27 ttl=128 time=24924 ms 64 bytes from 192.168.152.25: icmp_seq=28 ttl=128 time=23900 ms 64 bytes from 192.168.152.25: icmp_seq=51 ttl=128 time=412 ms 64 bytes from 192.168.152.25: icmp_seq=52 ttl=128 time=0.167 ms 64 bytes from 192.168.152.25: icmp_seq=53 ttl=128 time=0.559 ms 64 bytes from 192.168.152.25: icmp_seq=54 ttl=128 time=0.656 ms -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1843073 Title: Network loose connection for long time under light load guest winxp64 with virtio on i5-8350U Status in QEMU: New Bug description: I have issue with qemu and winxp guest on i5-8350U. First of all, if i run same vm with same config on i5 9660k i do not see such issue. Both pc have ubuntu 19.04 x86_64. Guest is winxp64, tried: 1) stable guest drivers, latest drivers 2) all virtio, only network r18169, bridge to host eth0, just default virbr0. 3) qemu from ubuntu 19.04, and tried latest libvirt and qeumu compiled from sources. 4) tried zram as block device I need really lightweight win to run only one app, so win7 and win10 is not an option. winxp 93921ab3-222a-4e5f-89c4-36703fc65cb4 http://libosinfo.org/xmlns/libvirt/domain/1.0";> http://microsoft.com/win/xp"/> 8388608 8388608 4 hvm destroy restart destroy /usr/local/bin/qemu-system-x86_64
