Comment 6 for bug 1916344

Different problem here I think John. If you run the following you should the user mode networking that involves Slirp and has the problem.

```
 qemu-system-i386 -m 700 -hda <Windows XP HD file> -net user -net nic
```

It's worth noting however that the problem most regularly manifest itself when a remote server delivers content and THEN closes the TCP socket straight away. When this happens, the return from the Mac's poll() system call seems to tickle Slirp's TCP urgent code, which results in the guest breaking up the received payload, mistakenly believing some of it to be "urgent". (I've no clue if Windows XP supports something SO_OOBINLINE that might alleviate the problem...)

If you use HTTP/1.1, you might not see this if the HTTP client is using a persistent connection, because the server will not close immediately after transmitting. Not sure what podman does in the opening comment above, and not sure what IE's default mode of operation is either.

If you're looking for a fix, there is Chris's patch in https://bugs.launchpad.net/qemu/+bug/1914117