From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: penberg@kernel.org, kvm@vger.kernel.org, mingo@elte.hu,
asias.hejun@gmail.com, gorcunov@gmail.com
Subject: Re: [PATCH] kvm tools: Improve init within a custom filesystem
Date: Wed, 24 Aug 2011 21:51:10 +0300 [thread overview]
Message-ID: <4E55481E.6040000@redhat.com> (raw)
In-Reply-To: <1314207675.3459.9.camel@lappy>
On 08/24/2011 08:41 PM, Sasha Levin wrote:
> On Wed, 2011-08-24 at 20:30 +0300, Avi Kivity wrote:
> > On 08/24/2011 07:19 PM, Sasha Levin wrote:
> > > This patch adds the following improvements:
> > >
> > > * Automatically start dhcpcd. Since we provide usermode netowrking
> > > we should make it fully transparent to the user.
> >
> > On my hosts, I have dhclient instead of dhcpd.
> >
>
> I was wondering if we should bring our own tiny dhcp client instead of
> assuming the host has one.
>
> Would it be better than assuming the host has it and then trying to
> figure out which one?
>
You don't really need a dhcp client, since you already have a
communication channel - the kernel command line. Read the IP address
and other info from there, and poke it into the interface.
There is also the ip= kernel parameter, but I don't know if it works
with a modular network driver.
I suggest something like "kvmtool.nic.$macaddr=$ip/$netmask
kvmtool.defaultroute=$gateway" - this is interface name agnostic.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-24 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 16:19 [PATCH] kvm tools: Improve init within a custom filesystem Sasha Levin
2011-08-24 17:30 ` Avi Kivity
2011-08-24 17:41 ` Sasha Levin
2011-08-24 18:17 ` Pekka Enberg
2011-08-24 18:51 ` Avi Kivity [this message]
2011-08-24 18:59 ` Pekka Enberg
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=4E55481E.6040000@redhat.com \
--to=avi@redhat.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.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.