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 10:11:54 +0300 [thread overview]
Message-ID: <1316070714.3743.9.camel@lappy> (raw)
In-Reply-To: <4E7199C0.4000701@cs.helsinki.fi>
On Thu, 2011-09-15 at 09:22 +0300, Pekka Enberg wrote:
> On 9/15/11 9:04 AM, Sasha Levin wrote:
> > On Thu, 2011-09-15 at 09:04 +0300, Pekka Enberg wrote:
> >> On Thu, Sep 15, 2011 at 9:00 AM, Sasha Levin<levinsasha928@gmail.com> wrote:
> >>> 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.
> >>
> >> How is that going to happen if you're not running kvmtool as root?
> >
> > In that case, dhcpcd in the guest will simply break because it can't
> > modify resolv.conf, no?
>
> Yes. Why is that a problem? You're not supposed to launch a dhcp client
> when using shared rootfs because kvmtool takes care of that for you.
Why? Testing a brand new dhcp client for example :)
We can't block the user from editing guest configuration files...
--
Sasha.
prev parent reply other threads:[~2011-09-15 7:12 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
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 [this message]
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=1316070714.3743.9.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 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.