From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com,
gorcunov@gmail.com
Subject: Re: [PATCH 2/2] kvm tools: Use host's resolv.conf within the guest
Date: Thu, 15 Sep 2011 09:00:19 +0300 [thread overview]
Message-ID: <1316066419.3743.5.camel@lappy> (raw)
In-Reply-To: <4E7190B4.1060306@cs.helsinki.fi>
On Thu, 2011-09-15 at 08:44 +0300, Pekka Enberg wrote:
> On 9/15/11 8:36 AM, Sasha Levin wrote:
> > On Thu, 2011-09-15 at 08:29 +0300, Pekka Enberg wrote:
> >> On Wed, Sep 14, 2011 at 7:28 PM, Sasha Levin<levinsasha928@gmail.com> wrote:
> >>> Since kernel IP autoconfiguration doesn't set up /etc/resolv.conf, we'll
> >>> use the one located within the host, since this was anyway what we simulated
> >>> within the DHCP offer packets.
> >>>
> >>> Signed-off-by: Sasha Levin<levinsasha928@gmail.com>
> >>
> >> Wouldn't a symlink to /host/etc/resolv.conf be more appropriate?
> >> Remember, we're supposed to only need to setup the shared rootfs once.
> >
> > It would mean the guest can screw up with the host's networking.
>
> How? You're not supposed to run the tool.
Hm? If you it to the host's resolv.conf, a guest can edit host's file,
no?
Might even be not on purpose... For example, simply running dhcpcd on
the guest.
--
Sasha.
next prev parent reply other threads:[~2011-09-15 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 16:28 [PATCH 1/2] kvm tools: Don't copy network autoconfiguration script Sasha Levin
2011-09-14 16:28 ` [PATCH 2/2] kvm tools: Use host's resolv.conf within the guest Sasha Levin
2011-09-15 5:29 ` Pekka Enberg
2011-09-15 5:36 ` Sasha Levin
2011-09-15 5:44 ` Pekka Enberg
2011-09-15 6:00 ` Sasha Levin [this message]
2011-09-15 6:04 ` Pekka Enberg
2011-09-15 6:04 ` Sasha Levin
2011-09-15 6:22 ` Pekka Enberg
2011-09-15 7:11 ` Sasha Levin
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=1316066419.3743.5.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.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