On Thu, 23 Sep 2010, Pierre-Philipp Braun wrote:
I'm running a Slackware64 dom0 on top of XEN 4.0.1. I tryed both xen/next and xen/master kernel repositories, same problem : the NetBSD guest sees its network interface (xennet0) but it's unusable. It doesn't ping nor responds to ping. Another guest, RHEL5 (2.6.18) network works fine. I tryed both -bridge and -route configurations (I would like to keep the latter), no changes.
Stab in the dark: lack of copy support in the network frontend? NetBSD currently only has flip support and when attempting to get NetBSD running as PV guest in XenServer, Citrix said that flip support is deprecated. Symptoms on XenServer were that not only did the guest not have network access, it also stopped all other domUs (and meant the XenServer dom0 had to be powercycled).
-- Stephen