From: Launchpad Bug Tracker <1656927@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1656927] Re: Network (TCP) access regression
Date: Wed, 11 Mar 2020 04:17:26 -0000 [thread overview]
Message-ID: <158390024619.22252.11528267192607324862.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20170116193627.27340.49782.malonedeb@chaenomeles.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1656927
Title:
Network (TCP) access regression
Status in QEMU:
Expired
Bug description:
Starting a VM with
/usr/bin/qemu-system-x86_64 -machine pc-i440fx-1.7,accel=kvm -usb -usbdevice tablet -usbdevice keyboard -enable-kvm -cpu core2duo -smp 2 -drive file=winp
ro.qcow,index=0,media=disk,format=qcow2 -m 4096 -vga vmware -vnc :3 -k en-us -device rtl8139,netdev=nic1 -netdev user,id=nic1,smb=/data/vps/files/,hostfw
d=tcp::10053-:10053,hostfwd=tcp::3387-:3389 -rtc base=utc,clock=host -daemonize
in 2.5.1, all works fine
in any version after 2.5.1.1, the network terminate TCP connections
after a certain period .
To reproduce, starts an app that use always connected TCP sockets (I
am using Metatrader 4), let it run a an hour, the app does not realize
the TCP is out of order but the TCP connection is closed by QEMU
in 2.5.1.x, Metatrader works perfectly
Thank you for your help
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1656927/+subscriptions
prev parent reply other threads:[~2020-03-11 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:36 [Qemu-devel] [Bug 1656927] [NEW] Network (TCP) access regression Joan Moreau
2020-01-10 9:38 ` [Bug 1656927] " Thomas Huth
2020-03-11 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=158390024619.22252.11528267192607324862.malone@loganberry.canonical.com \
--to=1656927@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.