All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Cc: Cristian Iorga <cristian.iorga-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH V3 2/2] connman-conf: configures connman in qemu machines
Date: Fri, 11 Jan 2013 13:22:39 +0100	[thread overview]
Message-ID: <lysj67ykmo.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1357901618-21786-3-git-send-email-cristian.iorga@intel.com> (Cristian Iorga's message of "Fri, 11 Jan 2013 12:53:38 +0200")

Cristian Iorga <cristian.iorga-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
writes:

> For qemu machines, connman should not configure virtual wired interfaces.

This is not a qemu-only problem but affects all platforms with nfs
rootfs, isn't it?

Setup whether to disable configuration of interface should be done
dynamically and based on e.g. whether rootfs is on nfs and/or if kernel
cmdline contains 'ip=...'.


> Wired interfaces (eth0) are assigned static IP addresses by the virtual
> machine manager (qemu). This packages places the eth0 interface in a
> list of blacklisted interfaces, forbiding connman administering wired
> interfaces for qemu machines.

Unfortunatly, this breaks DNS in the machine because DNS server information
are not retrieved from DHCP anymore :(



Enrico



  parent reply	other threads:[~2013-01-11 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 10:53 [PATCH V3 0/2] connman 1.10 upgrade and qemu networking fix Cristian Iorga
2013-01-11 10:53 ` [PATCH V3 1/2] connman: upgrade to 1.10 Cristian Iorga
2013-01-11 10:53 ` [PATCH V3 2/2] connman-conf: configures connman in qemu machines Cristian Iorga
2013-01-11 11:27   ` Martin Jansa
2013-01-11 12:01     ` Iorga, Cristian
2013-01-11 12:22   ` Enrico Scholz [this message]
2013-01-11 13:00     ` Iorga, Cristian

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=lysj67ykmo.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=cristian.iorga-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=openembedded-core@lists.openembedded.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.