From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, slash@ac.auone-net.jp
Subject: Re: [Bugme-new] [Bug 29252] New: IPv6 doesn't work in a kvm guest.
Date: Thu, 17 Feb 2011 14:32:37 -0800 (PST) [thread overview]
Message-ID: <20110217.143237.245412709.davem@davemloft.net> (raw)
In-Reply-To: <20110217142517.b9919481.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Thu, 17 Feb 2011 14:25:17 -0800
>> https://bugzilla.kernel.org/show_bug.cgi?id=29252
...
>> apt-get and ping6 don't work in a kvm guest. It appears that neighbor discovery
>> is not working. I'm using tap, virtio-net and vhost. I did bisect and results
>> is
>>
>> d80bc0fd262ef840ed4e82593ad6416fa1ba3fc4 is the first bad commit
>> commit d80bc0fd262ef840ed4e82593ad6416fa1ba3fc4
>> Author: David S. Miller <davem@davemloft.net>
>> Date: Mon Jan 24 16:01:58 2011 -0800
>>
>> ipv6: Always clone offlink routes.
>>
>> Do not handle PMTU vs. route lookup creation any differently
>> wrt. offlink routes, always clone them.
>>
>> Reported-by: PK <runningdoglackey@yahoo.com>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>
>> :040000 040000
>> c4a34e9e36bd8cc81e898738f2d4344f6647d472f0fcd4b093ec22784798f3951203391f4567b278
>> M net
>>
>> reverting this commit for guest kernel fixes the probrem.
Thanks for the report, I'll look into this.
next prev parent reply other threads:[~2011-02-17 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29252-10286@https.bugzilla.kernel.org/>
2011-02-17 22:25 ` [Bugme-new] [Bug 29252] New: IPv6 doesn't work in a kvm guest Andrew Morton
2011-02-17 22:32 ` David Miller [this message]
2011-03-09 23:58 ` David Miller
2011-03-10 3:20 ` David Miller
2011-03-10 4:04 ` David Miller
2011-03-11 19:44 ` Ernst Sjöstrand
2011-03-11 20:15 ` David Miller
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=20110217.143237.245412709.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=slash@ac.auone-net.jp \
/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;
as well as URLs for NNTP newsgroup(s).