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 calls not found

To: Pierre-Philipp Braun <pbraun@xxxxxxxxxx>
Subject: Re: [Xen-users] API calls not found
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 24 Jan 2010 13:58:16 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 24 Jan 2010 03:58:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B5C323E.5010309@xxxxxxxxxx>
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: <4B5C323E.5010309@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sun, Jan 24, 2010 at 12:42:54PM +0100, Pierre-Philipp Braun wrote:
> Dear XEN users,
>
>
> I installed xen 3.4.2 from source on slackware64.  I'm using latest dom0  
> from git with the recommended kernel options  
> (http://wiki.xensource.com/xenwiki/XenParavirtOps) without using pv_ops.  
>  When xend launches, I get those in the logs,
>
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call:  
> VBD.set_device not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call: VBD.set_type  
> not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call:  
> session.get_all_records not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call:  
> event.get_record not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call: event.get_all  
> not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call:  
> VIF.get_network not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call:  
> VIF.set_device not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call: VIF.set_MAC  
> not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call: VIF.set_MTU  
> not found
> [2010-01-24 12:14:18 3123] WARNING (XendAPI:701) API call: debug.get_all  
> not found
>

I guess these are only WARNINGs.. not sure why they show up though.

> How to fix this?  Is that why eventhough I'm able to start a pv guest  
> (netbsd) and configure the vif it sees, network doesn't respond at all  
> inside it ? I use network-bridge on the dom0.
>
>
> Some additionnal info below.
>
>
> teillard# brctl show
> bridge name     bridge id               STP enabled     interfaces
> eth0            8000.90e6baa651c7       no              peth0
>                                                         vif2.0

This looks correct. The guest with ID 2 is bridged to the bridge called eth0.

>
> ps. isn't vif0.0 missing ?  network's fine on dom0 anyways.
>

Nope. Xen 3.3/3.4 changed to different default bridged network setup.
They create a bridge called 'eth0' and assign the dom0 IP to the bridge.

-- Pasi


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>