All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Sasha Levin <levinsasha928@gmail.com>
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 08:44:20 +0300	[thread overview]
Message-ID: <4E7190B4.1060306@cs.helsinki.fi> (raw)
In-Reply-To: <1316065006.3743.0.camel@lappy>

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.

			Pekka

  reply	other threads:[~2011-09-15  5:44 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 [this message]
2011-09-15  6:00         ` Sasha Levin
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=4E7190B4.1060306@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    /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.