WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] API call: VIF.get_network not found

To: Jordi Moles <jordi@xxxxxxxxx>
Subject: Re: [Xen-users] API call: VIF.get_network not found
From: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Date: Mon, 25 Feb 2008 11:57:28 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Feb 2008 02:58:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47C2875C.3030305@xxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: netz-haut e.K.
References: <47C2875C.3030305@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20071022)
Jordi Moles schrieb:
hi everyone,
i'm trying to install xen 3.2.0 on debian etch. i've been stuck at one point for days. when xend starts, i get this in the log file: "API call: VIF.get_network not found" so... vifx.x devices don't load and vm don't have access to the network bridge.
anyone has faced this?
i've read something about a python package missing, but i don't have a clue of what to install
i've got python already installed.

Hi,

I don't think this is a python problem.


[2008-02-25 09:32:35 3589] INFO (__init__:1072) Not recreating missing unmanaged network xenbr1 [2008-02-25 09:32:35 3589] INFO (__init__:1072) Not recreating missing unmanaged network xenbr0

Maybe your config files are wrong (or from 3.0/3.1 xen).
The default bridge names have been changed in 3.2 from xenbr0 to eth0
xenbr1 -> eth1 and so on.

It also could be, that you don't have bridge-utils installed.

cheers,

Stephan

Attachment: s_seitz.vcf
Description: Vcard

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>