From: Laurent Vivier <laurent@vivier.eu>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org, agraf@suse.de
Subject: [Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support
Date: Sat, 30 Jan 2016 23:26:57 +0100 [thread overview]
Message-ID: <1454192820-5095-1-git-send-email-laurent@vivier.eu> (raw)
Since commit:
e36800c linux-user: add signalfd/signalfd4 syscalls
It is now possible to register handlers to a file descriptor
to translate a data stream transiting by this file descriptor.
We can now decode netlink information coming from the guest
and inject a translated one into the host, and vice-versa.
This series is an "RFC" because it works (we can boot a
container using systemd and use iproute tools) but some
problems remain.
Some results (x86_64 host) with some guests:
* ppc: it can boot a debian 8.2/8.3 (Jessie) LXC container
and networking works fine (dhcp and "apt-get upgrade").
"ip link" generates some traces in the kernel log:
"netlink: 8 bytes leftover after parsing attributes in process `ip'."
* ppc64: it can boot a fedora 21 LXC container.
Some issues with dhclient and "dnf update"
(-> Invalid instruction, can be caused by a memory corruption done
by netlink calls).
"ip link" generates some traces in the kernel log:
"netlink: 8 bytes leftover after parsing attributes in process `ip'."
* ppc64le: Debian 8.3 (Jessie) works fine.
* sh4: container doesn't work but 'ip' in a chroot works well.
* arm: Raspbian 8.3 (Jessie) works fine.
* s390x: container Debian 8.1 boots well, but "apt-get" hangs on
networking (name resolution?).
"ip link" generates some traces in the kernel log:
"netlink: 8 bytes leftover after parsing attributes in process `ip'."
Laurent Vivier (3):
linux-user: add rtnetlink(7) support
linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT
linux-user: add netlink audit
linux-user/syscall.c | 537 ++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 531 insertions(+), 6 deletions(-)
--
2.5.0
next reply other threads:[~2016-01-30 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 22:26 Laurent Vivier [this message]
2016-01-30 22:26 ` [Qemu-devel] [PATCH RFC 1/3] linux-user: add rtnetlink(7) support Laurent Vivier
2016-05-13 16:40 ` Peter Maydell
2016-05-14 9:37 ` Laurent Vivier
2016-05-14 10:13 ` Peter Maydell
2016-01-30 22:26 ` [Qemu-devel] [PATCH RFC 2/3] linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT Laurent Vivier
2016-05-13 16:42 ` Peter Maydell
2016-01-30 22:27 ` [Qemu-devel] [PATCH RFC 3/3] linux-user: add netlink audit Laurent Vivier
2016-05-13 16:48 ` Peter Maydell
2016-02-07 10:24 ` [Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support Laurent Vivier
2016-02-07 13:10 ` Peter Maydell
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=1454192820-5095-1-git-send-email-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).