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-users] Re: netbsd/amd64 5.1rc4 domU network

To: Pierre-Philipp Braun <pbraun@xxxxxxxxxx>
Subject: [Xen-users] Re: netbsd/amd64 5.1rc4 domU network
From: Stephen Borrill <netbsd@xxxxxxxxxxxxxxxx>
Date: Thu, 23 Sep 2010 11:53:33 +0100 (BST)
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, port-xen@xxxxxxxxxx
Delivery-date: Thu, 23 Sep 2010 04:18:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <225c6c9cdfa38a3ca329a73ac97e7b3e@localhost>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <225c6c9cdfa38a3ca329a73ac97e7b3e@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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).


Xen-users mailing list