[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support
From: |
Laurent Vivier |
Subject: |
[Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support |
Date: |
Sat, 30 Jan 2016 23:26:57 +0100 |
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
- [Qemu-devel] [PATCH RFC 0/3] linux-user: netlink support,
Laurent Vivier <=