From: Avi Kivity <avi@qumranet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
kvm@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Work around dhclient brokenness
Date: Mon, 18 Aug 2008 15:15:17 +0300 [thread overview]
Message-ID: <48A967D5.80004@qumranet.com> (raw)
In-Reply-To: <20080818114425.GA20351@gondor.apana.org.au>
Herbert Xu wrote:
> On Mon, Aug 18, 2008 at 02:40:55PM +0300, Avi Kivity wrote:
>
>> Isn't that turned on automatically for real hardware? And what's to
>> prevent a broken dhclient together with the (presumably) hacked up
>> initscripts that call ethtool?
>>
>
> Well the idea is that only a fixed guest would even know about
> enabling this.
>
I can think of problems with hotplugged virtio devices, but yes, this
may be better.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-18 12:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 19:47 [PATCH] Work around dhclient brokenness Anthony Liguori
2008-08-18 10:56 ` Avi Kivity
2008-08-18 11:01 ` Herbert Xu
2008-08-18 11:06 ` Avi Kivity
2008-08-18 11:34 ` Herbert Xu
2008-08-18 11:40 ` Avi Kivity
2008-08-18 11:44 ` Herbert Xu
2008-08-18 12:15 ` Avi Kivity [this message]
2008-08-19 0:45 ` Rusty Russell
2008-08-19 3:17 ` Chris Wedgwood
2008-08-19 4:41 ` Rusty Russell
2008-08-19 5:13 ` Chris Wedgwood
2008-08-19 5:17 ` Herbert Xu
2008-08-19 5:28 ` Chris Wedgwood
2008-08-19 9:10 ` Rusty Russell
2008-08-19 15:05 ` Chris Wedgwood
2008-08-25 4:01 ` Rusty Russell
2008-08-19 9:08 ` Rusty Russell
2008-08-19 9:56 ` Herbert Xu
2008-08-19 11:36 ` Rusty Russell
2008-08-19 23:35 ` Anthony Liguori
2008-08-19 9:12 ` Avi Kivity
2008-08-19 13:42 ` Anthony Liguori
2008-08-19 13:50 ` Avi Kivity
2008-08-19 13:54 ` Anthony Liguori
2008-08-19 14:00 ` Avi Kivity
2008-08-24 8:39 ` Herbert Xu
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=48A967D5.80004@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=rusty@rustcorp.com.au \
/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.