search for: vethx

...route traffic to/from them from the Dom0. This network-multinet script sounds ideal for what I want: http://thepenguinpriest.com/linux/scripts/network-multinet.html However, the description of building a routed network says I need to call the script and give it the "virtual ethernet device (vethX)" that lives in Dom0. Where the heck do I get one of those? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

what i am doing wrong? My vethX of xend-dom0 dont start. ---- dcgs0058:~# lspci |grep Ether 0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 0000:07:08.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) dcgs0058:~# ifconfig eth0 Link encap:Ethern...

...39;type=ioemu, bridge=xenbr0''] Could never ping a external from DomU!! What I know: - the ethX device is a logical device and the physical device is renamed to pethX; - the vifX.Y devices are linked with ethY from DomX (ie.: vif1.0 <-> Dom1 eth0); - there is also a vethX ... What configuration I have to do on Dom0? What configuration I have to do on DomU? When rebooting I have always need to do ''ifconfig ethX up'' !!! thanx _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xens...

> That''s great, except when you need *two* bridges, for two > independent subnets, and there is no, as far as I can see, peth1. You can have multiple vethX interfaces on recent builds -- see netback/loopback.c. I think the current default is a rather miserly 1 (and should be increased), but can be set on the command line. Ian > Em Wednesday 14 September 2005 16:30, John Wilson escreveu: > > Yo, > > > > I had big problems with...

Hi, I was hoping someone on this forums could help me out with a problem I was facing with Xen. When I compiled the kernel for Xen-3.1.3 using "make world"(I know this is an old version but I need to use it for some compatibility issues), the kernel was missing the Xen netloop module. There was no /kernel/drivers/xen/netback/netloop.ko in the newly compiled kernel. I think we would

Hi ! I have install the xen4+centos5 on my server following the post of the kernel version is 2.6.32.27 which is download from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git But after I reboot the server ,and run the "ifconfig", whose output likes the following [root@localhost scripts]# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C5:EB:96:C3

...device which is a bridge ># ># ..then we translate xenbrX to ethX ># ># This lets old config files work without modification > >So it turns out Xen networking changed in current releases and they never >updated their Wiki. > >Now I am not sure how the vif0.X and vethX interfaces fit into the >picture here... Maybe these are no longer used? > >vifX.Y interfaces are still used though for linking domU interfaces >with the physical interface. > > >-Ross > >______________________________________________________________________ &gt...

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0)

...in OUTPUT (policy ACCEPT) target prot opt source destination foobar:~ # depending on of the domU''s are started or not. What I found strange, is that a peth isn''t displayed at all in my ip a output. Is this the result of renaming the eth devices while setting up vethX? I saw also in some posts that xenbr0 was assigned an ip address. Tried that as well and also set a routing entry for it but my domU''s don''t wanna talk to the outsite. Has anyone an idea what could cause this problem? Regards, Sascha This email was Anti Virus checked by Asta...

Hi *, having built Xen 4.1.0 and running my Dom0 on Slackware 13.1, I''m trying to assign different physical network interfaces to different DomU guests: vif = [ ''bridge=ethX'' ] in the DomU configuration files. My /etc/xen/scripts/network-bridge script, however, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start