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
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
Any suggestions ?
Which script creates vifs ?
CM
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Fri, Jun 18, 2010 at 8:54 AM, ccmail111 <ccmail111@yahoo.com> 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 peth0That 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.> > I dont see any vifs being created (ifconfig cmd used). > > Also in log I see: > WARNING (XendAPI:705) API call: VIF.set_device not foundI''m guessing you don''t have network backend support built on dom0. Which dom0 kernel did you use? How did you build it? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Fajar ! questions inline.. --- On Thu, 6/17/10, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: [Xen-users] vifs and veth not created To: "ccmail111" <ccmail111@yahoo.com> Cc: xen-users@lists.xensource.com Date: Thursday, June 17, 2010, 10:11 PM On Fri, Jun 18, 2010 at 8:54 AM, ccmail111 <ccmail111@yahoo.com> 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 peth0That 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 foundI''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@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 18, 2010 at 9:27 AM, ccmail111 <ccmail111@yahoo.com> wrote:> hmm, yep I see that in 3.4.2 veth and vif were created by defaultReally? 3.4.2 should bevahe the same way as 4.0 regarding bridged networking. Unless if you have your own custom network-bridge script? 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 -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar, --- On Thu, 6/17/10, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: [Xen-users] vifs and veth not created To: "ccmail111" <ccmail111@yahoo.com> Cc: xen-users@lists.xensource.com Date: Thursday, June 17, 2010, 10:34 PM On Fri, Jun 18, 2010 at 9:27 AM, ccmail111 <ccmail111@yahoo.com> wrote:> hmm, yep I see that in 3.4.2 veth and vif were created by defaultReally? 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi Fajar,
I do see..
--- On Thu, 6/17/10, Fajar A. Nugraha <fajar@fajar.net> wrote:
From: Fajar A. Nugraha <fajar@fajar.net>
Subject: Re: [Xen-users] vifs and veth not created
To: "ccmail111" <ccmail111@yahoo.com>
Cc: xen-users@lists.xensource.com
Date: Thursday, June 17, 2010, 10:34 PM
<clipped>
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
^^^^^^^^^^^
I do see:
#
# TI VLYNQ
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_NETDEV_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_BLKBACK_PAGEMAP=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
CONFIG_XENFS=y
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y
# CONFIG_XEN_PLATFORM_PCI is not set
CONFIG_XEN_MCE=y
CONFIG_XEN_XENBUS_FRONTEND=y
CONFIG_XEN_GNTDEV=y
CONFIG_XEN_S3=y
CONFIG_ACPI_PROCESSOR_XEN=y
CONFIG_STAGING=y
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Fri, Jun 18, 2010 at 12:07 PM, ccmail111 <ccmail111@yahoo.com> wrote:> 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 ?vethX and vif0.X are not created by default on newer Xen versions. These are the ones created by netloop kernel module. vifY.X, where Y > 0, is created when domUs are created (unless you assign different names on domU config file). Do you actually have problems creating domU? Or is it simply you just see different output with brctl and ifconfig? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users