On Fri, Jun 29, 2012 at 04:18:26PM +0200, Hans van Kranenburg wrote:
> On 06/29/2012 04:06 PM, Hans van Kranenburg wrote:
> >Package: xen-hypervisor-4.0-amd64
> >Version: 4.0.1-5.2
>
> Whoops, accidentally mailed ovs-discuss again, when submitting the
> issue to debian, please ignore, sorry.
>
>
On 06/29/2012 04:06 PM, Hans van Kranenburg wrote:
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-5.2
Whoops, accidentally mailed ovs-discuss again, when submitting the issue
to debian, please ignore, sorry.
Anyway, after asking on IRC, I was advised to also report the issue at
debian, be
Package: xen-hypervisor-4.0-amd64
Version: 4.0.1-5.2
Hi,
We're seeing weird behaviour regarding network traffic between a Xen
dom0 and domU. I reported this issue yesterday to the
openvswitch-discuss mailing list, but it seems this could also be a
(regression?) bug in the xen hypervisor or th
When re-reading my post from yesterday...
On 06/28/2012 08:21 PM, Hans van Kranenburg wrote:
On the interface at the ovs (dom0) side, I can see arp requests, which
are not being answered by the problematic host.
# tcpdump -n -i domU-24-09
tcpdump: WARNING: domU-24-09: no IPv4 address assigned
Hi Folks,
We're seeing weird behaviour regarding network traffic between a Xen
dom0 and domU.
This setup is using Debian GNU/Linux, with Xen 4.0 and the Debian 2.6.32
kernel and Openvswitch 1.4.0-1 packages from Debian (30 Jan 2012) which
I repackaged for use with squeeze.
(http://packages.
