qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Quintern <tobias.quintern@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1619896] Re: Unsupported ancillary data: 0/8
Date: Sat, 03 Sep 2016 12:15:01 -0000	[thread overview]
Message-ID: <20160903121501.26293.3825.malone@gac.canonical.com> (raw)
In-Reply-To: 20160903112421.26727.12298.malonedeb@gac.canonical.com

Kindly note that the issue does not occur with TeamSpeak 3 Server
3.0.12.4 (x86)

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1619896

Title:
  Unsupported ancillary data: 0/8

Status in QEMU:
  New

Bug description:
  Hello,

  I have the following issue when launching the Teamspeak Server x86
  binary on an arm host.

  Host:
   Linux 4.6.2 (vanilla)
   Ubuntu 14.04.5 LTS
   HW: Cubietruck board, armv7l

  
  Used SW: Release archive qemu-2.7.0.tar.bz2 and git commit 1dc33ed90bf1fe1c2014dffa0d9e863c520d953a
  Configure options:
    ../configure --target-list=i386-linux-user 
  I attached the output of the configure script as configure.log

  Testcase:

  1. Download and extract TeamSpeak 3 Server 3.0.13.3 (x86)
    Souce: http://dl.4players.de/ts/releases/3.0.13.3/teamspeak3-server_linux_x86-3.0.13.3.tar.bz2

  2. Modifiy ts3server_minimal_runscript.sh for ease of use
    - ./ts3server $@
    + /usr/local/bin/qemu-i386 ./ts3server $@

  3. Execute ./ts3server_minimal_runscript.sh

  Wait for 6 Minutes until teamspeak server started. QEMU saturates the
  cpu while Teamspeak is precomputing a puzzle. (Whatever that means)

  After that Teamspeak settles with the following output:
    2016-09-03 10:50:59.555582|INFO    |Query         |   |listening on 0.0.0.0:10011, :::10011

  The Qemu process is now idling with ~2% cpu load. This is actually the
  first time for me that QEMU is able to successfully launch the
  Teamspeak server. Kudos!

  4. Connect client 1

  TS Clients can connect, but the following line is printed pretty often:
    Unsupported ancillary data: 0/8

  The line seems to come from qemu (linux-user/syscall.c)

  
  5. Connect client 2
  When a second client is connected the audio transmission is successful for a few seconds, but the server drops the connection after that and refuses to take new connections.

  Please let me know, if you need more information. I'll gladly provide
  strace or valgrind logs.

  Best regards,
  Tobias

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1619896/+subscriptions

  parent reply	other threads:[~2016-09-03 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03 11:24 [Qemu-devel] [Bug 1619896] [NEW] Unsupported ancillary data: 0/8 Tobias Quintern
2016-09-03 11:25 ` [Qemu-devel] [Bug 1619896] " Tobias Quintern
2016-09-03 12:15 ` Tobias Quintern [this message]
2018-03-15 17:23 ` Peter Maydell
2020-11-05 13:28 ` [Bug 1619896] Re: linux-user missing cmsg IP_PKTINFO support ("Unsupported ancillary data: 0/8") Peter Maydell
2020-11-09 11:27 ` Gabriele
2020-11-09 11:46 ` Gabriele
2021-05-04  8:05 ` Thomas Huth

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=20160903121501.26293.3825.malone@gac.canonical.com \
    --to=tobias.quintern@gmail.com \
    --cc=1619896@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).