Greg Troxel wrote:
Jeff Rizzo<r...@tastylime.net> writes:
I just noticed that a host of mine running as a Xen guest is not
getting (or maybe just sending) ipv6 packets correctly. It's running
pretty much the same as some physical hosts, and the only difference I
can see is the Xen (and vioif) aspect.
Are you using a bridge for xvifN.0 on the dom0?
Try using ping6 to the link-local (fe80::) addresses. Remember to use
%ifname as it appears in ifconfig (other end's address, your ifname).
Try running tcpdump in promiscuous mode on both ends. That can hide
some mcast programming/filtering bugs to help diagnosis.
First, ping the ll address of the xvif from the domU, and vice versa.
The tone I imagined in your email seems to suggest that you know why this is
happening.
I am seeing this exact problem on my Xen setup, it's a NetBSD 7.1 dom0 with
7.1 domU:s using xvif linked to the real wm with a bridge. The domUs sometimes
become completely unresponsive on ipv6, but then recover. ipv4 seems
completely unaffected.
Sometimes the dom0 is also unresponsive on v6.
It seems to happen as the domUs are idle, with little to no traffic, because
one of the VMs host my (v6) irc session and it has stayed up for 30+ days.
Staffan
