Re: [Xen-users] vifs and veth not created

[ccmail111 <ccmail111@xxxxxxxxx>]

Thanks Fajar !

questions inline..

--- On Thu, 6/17/10, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:

From: Fajar A. Nugraha <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] vifs and veth not created
To: "ccmail111" <ccmail111@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Thursday, June 17, 2010, 10:11 PM

On Fri, Jun 18, 2010 at 8:54 AM, ccmail111 <ccmail111@xxxxxxxxx> wrote:
>
>
> I see veth interfaces also not created.
> only  peth0 is created.
>
> Kindly cc me email response/suggestions.
>
>
> Hi,
>
> I have Xen4.0 and see:
>
> bash-4.1# brctl show
> bridge name           bridge id                 STP enabled                             interfaces
> eth0                      8000.524603000401 no                                            peth0

That is normal in newer Xen setup. veth are not created. vifs are only
created when there's a domU running. This is different from older Xen
setup, where it would create vif-veth pair in dom0.

^^^^
  hmm, yep I see that in 3.4.2 veth and vif were created by default but in xen 4.0 I dont see veth and/or vif  being created.

Is there any documentation for above or related in Xen 4.0 ?

>
> I dont see any vifs being created (ifconfig cmd used).
>
> Also in log I see:
> WARNING (XendAPI:705) API call: VIF.set_device not found

I'm guessing you don't have network backend support built on dom0.
Which dom0 kernel did you use? How did you build it?
^^^^^^^^^^^
   I build and package it myself. dom0: 2.6.32-13 kernel.   How do I enable the backend support ?


--
Fajar

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