From: Avi Kivity <avi@qumranet.com>
To: cristi.magherusan@net.utcluj.ro
Cc: kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: trivial DNS issues
Date: Mon, 01 Sep 2008 15:37:21 +0300 [thread overview]
Message-ID: <48BBE201.60703@qumranet.com> (raw)
In-Reply-To: <1220272261.19757.11.camel@localhost>
Cristi Magherusan wrote:
> On Mon, 2008-09-01 at 14:14 +0300, Avi Kivity wrote:
>
>> Cristi Magherusan wrote:
>>
>>> Those who have installed a local DNS server may need that stuff, but we
>>> can check every entries of resolv.conf and see if we can connect to
>>> their DNS server, and use in our VM the first one that could be reached.
>>>
>>>
>>>
>> The network maybe down when the VM is started, or the dns server may be
>> down, or ...
>> Maybe we should forward the host's dns servers to the guest, replacing
>> 127.0.0.1 by 10.0.2.2.
>>
> Then we should forward them all, but the localhost one should be tested
> and skipped if unavailable.
>
Why? A local application will have exactly the same problems with a
broken dns server on localhost, as a virtual machine with that address
forwarded. And if the the dns server is later fixed, both the local
application and the guest will recover.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: cristi.magherusan@net.utcluj.ro
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: trivial DNS issues
Date: Mon, 01 Sep 2008 15:37:21 +0300 [thread overview]
Message-ID: <48BBE201.60703@qumranet.com> (raw)
In-Reply-To: <1220272261.19757.11.camel@localhost>
Cristi Magherusan wrote:
> On Mon, 2008-09-01 at 14:14 +0300, Avi Kivity wrote:
>
>> Cristi Magherusan wrote:
>>
>>> Those who have installed a local DNS server may need that stuff, but we
>>> can check every entries of resolv.conf and see if we can connect to
>>> their DNS server, and use in our VM the first one that could be reached.
>>>
>>>
>>>
>> The network maybe down when the VM is started, or the dns server may be
>> down, or ...
>> Maybe we should forward the host's dns servers to the guest, replacing
>> 127.0.0.1 by 10.0.2.2.
>>
> Then we should forward them all, but the localhost one should be tested
> and skipped if unavailable.
>
Why? A local application will have exactly the same problems with a
broken dns server on localhost, as a virtual machine with that address
forwarded. And if the the dns server is later fixed, both the local
application and the guest will recover.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-09-01 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 9:57 trivial DNS issues Cristi Magherusan
2008-09-01 10:29 ` Avi Kivity
2008-09-01 10:29 ` [Qemu-devel] " Avi Kivity
2008-09-01 10:57 ` Cristi Magherusan
2008-09-01 10:57 ` [Qemu-devel] " Cristi Magherusan
2008-09-01 11:14 ` Avi Kivity
2008-09-01 11:14 ` [Qemu-devel] " Avi Kivity
2008-09-01 12:31 ` Cristi Magherusan
2008-09-01 12:31 ` [Qemu-devel] " Cristi Magherusan
2008-09-01 12:37 ` Avi Kivity [this message]
2008-09-01 12:37 ` Avi Kivity
2008-09-01 14:35 ` Cristi Magherusan
2008-09-01 14:35 ` [Qemu-devel] " Cristi Magherusan
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=48BBE201.60703@qumranet.com \
--to=avi@qumranet.com \
--cc=cristi.magherusan@net.utcluj.ro \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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.