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

[ccmail111 <ccmail111@xxxxxxxxx>]

Hi Fajar,

 

--- 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:34 PM

On Fri, Jun 18, 2010 at 9:27 AM, ccmail111 <ccmail111@xxxxxxxxx> wrote:
>   hmm, yep I see that in 3.4.2 veth and vif were created by default

Really? 3.4.2 should bevahe the same way as 4.0 regarding bridged
networking. Unless if you have your own custom network-bridge script?

^^^^^^^^^

          sorry typo, I meant what you mentioned: veth and vif are not created by default.

  So in Xen 4.0 veth and vif are only created while creating domUs ? Are they added to bridge at same time also ?

----
The one responsible for creating vif-veth pair in dom0 is the netloop
module. After that, network-bridge script does some renaming (like old
eth0 -> peth0, and veth0 -> eth0 for older version of xen).

> 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 ?

The one documenting the change? not that I know of. Also like I said,
it's not a change in Xen 4.0, but in previous versions (don't know
which one exactly)

> 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 ?

This is my dom0 pv_ops kernel config: http://pastebin.com/5L44xXQj

The most important backend-related configs are
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=m
CONFIG_XEN_BLKDEV_BACKEND=m
^^^^^^^^^^^

   Thanks, I will check that.

 

--
Fajar

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