All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Adeos <adeos-main@gna.org>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Adeos-main] Reworking ipipe timer subsystem,
Date: Tue, 03 Apr 2012 20:39:16 +0200	[thread overview]
Message-ID: <4F7B43D4.9070800@domain.hid> (raw)
In-Reply-To: <4F7B429C.8020009@domain.hid>

On 2012-04-03 20:34, Gilles Chanteperdrix wrote:
> On 04/03/2012 08:26 PM, Jan Kiszka wrote:
>> On 2012-04-03 20:17, Gilles Chanteperdrix wrote:
>>> Ok, I get it, I need -net nic -net user. The first is for the nic in the
>>> guest, the second configures by what means the physical network will be
>>> emulated. I would have liked the qemu guest to appear on my LAN, but
>>> that will do.
>>
>> That requires a bridge on the host and a tap device backend. Upcoming
>> qemu-1.1 will even have a helper daemon to create those tap devices with
>> raised privileges and allow unprivileged QEMU instances to use them.
> 
> ... Or you can put the interface in promiscuous mode and send raw
> ethernet packets using the emulated NIC mac address. No bridge, no tap
> device, no helper daemon required.

...but still root privileges, otherwise you are unable to send/receive
arbitrary frames over the interface.

> 
> In any case with -net user, I can not use the virtual network to mount
> the rootfs using NFS, so, it still does not work.

That could be a bug. You happen to talk to the maintainer of this ugly
subsystem (sigh...), and as such I would be glad if you could take a
dump with "-net user -net nic -net dump" of the failing interaction
between guest and host. Output will be in qemu-vlan0.pcap in your
working directory.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2012-04-03 18:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 19:43 [Adeos-main] Reworking ipipe timer subsystem, Gilles Chanteperdrix
2012-02-20 16:46 ` Philippe Gerum
2012-02-24 12:28   ` Gilles Chanteperdrix
2012-02-24 14:40     ` Philippe Gerum
2012-04-02 15:39       ` Gilles Chanteperdrix
2012-04-02 15:54         ` Jan Kiszka
2012-04-02 16:08           ` Gilles Chanteperdrix
2012-04-02 16:18             ` Jan Kiszka
2012-04-02 16:21               ` Gilles Chanteperdrix
2012-04-02 20:41           ` Gilles Chanteperdrix
2012-04-02 20:56             ` Jan Kiszka
2012-04-02 20:59               ` Jan Kiszka
2012-04-02 21:55                 ` Gilles Chanteperdrix
2012-04-02 21:58                   ` Jan Kiszka
2012-04-03  7:54                     ` Gilles Chanteperdrix
2012-04-03  7:59                       ` Jan Kiszka
2012-04-03 11:06                         ` Gilles Chanteperdrix
2012-04-03 17:38                           ` Jan Kiszka
2012-04-03 18:17                             ` Gilles Chanteperdrix
2012-04-03 18:26                               ` Jan Kiszka
2012-04-03 18:34                                 ` Gilles Chanteperdrix
2012-04-03 18:39                                   ` Jan Kiszka [this message]
2012-04-03 19:05                                     ` Gilles Chanteperdrix

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=4F7B43D4.9070800@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=rpm@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.