Your message dated Wed, 27 Nov 2013 23:32:09 +0400
with message-id <[email protected]>
and subject line Re: Bug#654867: qemu-user-static: "Unsupported syscall" spew
has caused the Debian Bug report #654867,
regarding qemu-user-static: "Unsupported syscall" spew
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
654867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654867
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-user-static
Version: 1.0+dfsg-1
Severity: important
Tags: upstream

I am trying to run qemu to emulate an ARM chroot environment.

qemu spews messages like

        qemu: Unsupported syscall: 341

to stderr. This makes qemu unuseable for any sort of interactive code.
Even running "apt-get dist-upgrade" in that chroot is near-impossible.

Printing this sort of message should be controlled by a flag (or an
environment variable), and default to off. It's only of interest to
people who want to improve qemu, not users.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

qemu-user-static depends on no packages.

Versions of packages qemu-user-static recommends:
ii  binfmt-support  2.0.8

Versions of packages qemu-user-static suggests:
ii  sudo  1.8.3p1-2

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 1.5.0+dfsg-1

I just took another look at this bugreport - at least on my amd64 system,
qemu 1.5.0 is able to run basic commands (including a few mentioned in
this bugreport) without any hassle, it just works.

So I'm closing this bugreport now.  I understand that there are syscalls
still which aren't implemented, and qemu will always be behind kernel
here, which invents new syscals in almost every release.  But at least
basic commands works, and that's what this bug was about.

Thanks,

/mjt

--- End Message ---

Reply via email to