This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 449] Packets sent by dom0 to domU lost in domU before us

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 449] Packets sent by dom0 to domU lost in domU before userspace delivery
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 14 Dec 2005 10:01:58 +0000
Delivery-date: Wed, 14 Dec 2005 10:05:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From website+xen@xxxxxxxxxxxxxx  2005-12-14 10:01 
I tried reproducing the bug using the same dom0 network settings (bridging the
physical interface with the domU's vif, assigning ip to bridge) but it worked
out fine.

Note that the only similarity between my configuration and Craig's was that we
both use Debian SArge. I probably was using a different Xen patchset, and
different dom0/U kernel configs. So, it probably wasn't a good shot at
reproducing the problem.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list