search for: vif0

I''ve been trying to track down an occasional system hang when doing /etc/xen/scripts/network-bridge stop. Would it be reasonable to do the fdown ${netdev} and then set ${vif0} down to provide ifdown with a behavior that is as close as possible to a real network card? Signed- off- by: Kirk Allan <kallan@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-us...

...root@localhost scripts]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 512 4 r----- 1900.3 the libvirtd''s version is 0.8.4 I cannot find the network bridge "xenbr0" and "vif0" , so Did anyone have met such problem? Please do me a favour! Thank you very much! Chqiu _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, The attached patch fixes the setup of the bridge ports and the bridge itself. Changes: * move some functions to xen-network-common.sh, so both vif-bridge and network-bridge can use them. * add a new function to configure bridge ports and use it. * make sure arp requests, ipv6 autoconfiguration and ipv6 router solicitations are disabled for the bridge ports and also for the

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help me with understanding following things 1)...

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help me with understanding following things 1)...

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

Still trying to make my VMs appear on a subnet of their very own and 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

...ight run it, so I assume >> it's xend doing that, but there's no error in any log. > >Kai, > >Snooping around I found this in /etc/xen/qemu-ifup: > ># ># Old style bridge setup with netloop, used to have a bridge name ># of xenbrX, enslaving pethX and vif0.X, and then configuring ># eth0. ># ># New style bridge setup does not use netloop, so the bridge name ># is ethX and the physical device is enslaved pethX ># ># So if... ># ># - User asks for xenbrX ># - AND xenbrX doesn't exist ># - AND there is a...

...... havin'' read whatever I could "google" on this topic, I didn`t find any solution: openSuSE 10.2 (out of the box), xenkernel, running on HP Proliant DL360G5 (dual internal networking, plus additional 4-port adapter) gives me eth0 - eth5, but only peth0 - peth3 (as well as vif0 - vif3 and consequentely xenbr0 - xenbr3). I increased the number of loopback-devices to 64 ... no result Whenever I try to "/etc/xen/scripts/network-bridge start vifnum=4" I get a message regarding to a "nonexisting veth4" ... What am I missing Thanks for your time Joe...

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)

...he bridge. Attached are examples for iptables rulesets in bridging, routing, nat-ing network setups. Also attached the patch. Please note that many iptables rules shown below could be collapsed if we assumed that all domains are permitted to talk to Domain0, i.e., all vifX.Y can communicate to vif0.Y. In this case, we can just add two rules saying in/out traffic through vif0.Y is always ACCEPTed. This patch does currently not leverage this simplification because we anticipate that Domain0 will become less powerful than it is today. Comments welcome. Thanks Reiner The following show exam...

...ut it''s because domU''s vif (vif1.0, vif2.0, etc) uses MAC FE:FF:FF:FF:FF:FF, and it pretty much results in http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=339 For dom0 part it can be "fixed" using the new network-bridge attached in bug report (basically assigning vif0.x unique MAC address). This does not fix domU though, as they''re vif still use FE:FF:FF:FF:FF:FF. I had to hack vif-bridge, adding a random MAC generator to solve this problem. Do you guys have this problem as well? How did you deal with it? -- Fajar ___________________________________...

I am using nat for guest domU with dhcp running on dom0. on creating the domU xend-debug.log reports: Can''t open /etc/dhcp3/dhcpd.conf: Permission denied and dhcp fails. The vif0.X is created and the dhcp.conf is modified according to the randomly generated mac address and the address of vifx.0. I think the problem lies in the vif-nat script in synchronization during dhcpd.conf modification. Restart(start) of the dhcp server fails and the failure is ignored. With the fol...

...ers/xen/netback/loopback.c Tue Dec 07 18:35:16 2010 +0000 +++ b/drivers/xen/netback/loopback.c Wed Dec 08 18:27:41 2010 +0100 @@ -290,23 +290,6 @@ return err; } -static void __exit clean_loopback(int i) -{ - struct net_device *dev1, *dev2; - char dev_name[IFNAMSIZ]; - - sprintf(dev_name, "vif0.%d", i); - dev1 = dev_get_by_name(dev_name); - sprintf(dev_name, "veth%d", i); - dev2 = dev_get_by_name(dev_name); - if (dev1 && dev2) { - unregister_netdev(dev2); - unregister_netdev(dev1); - free_netdev(dev2); - free_netdev(dev1); - } -} - static int __init loopback_in...

..." size=\"21474836480\" sr=\"\" bootable=\"true\" type=\"system\"/></provision>" # install VM xe vm-install template="CentOS 5.4 x64" new-name-label="Test" sr-uuid=be51be94-8f80-1010-c88c-0e07a55c39a8 # create VM vif0 xe vif-create vm-uuid=fd478bba-f12f-8402-21b7-685566164390 network-uuid=b82128e2-aa9a-8971-47c8-95b819dce275 mac=random device=0 # set install repository to local install server xe vm-param-set uuid=fd478bba-f12f-8402-21b7-685566164390 other-config:install-repository="http://mi.mirror.ga...

...r/network-bridge" "$@" vifnum=5 netdev=eth5 bridge=xenbr5 When i done brct show i have this : bridge name bridge id STP enabled interfaces bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 xenbr1 8000.feffffffffff no vif0.1 peth1 xenbr2 8000.feffffffffff no vif0.2...

Hello, Was wondering if there is a solution to the error posted by "Dominique H Schramm" on the 5 Jan 2008 I''ve just changed from network-bridge to network-route and just noticed this problem Thanks, """ Hi guys, i got the following error: /etc/xen/scripts/network-route: line 27: /proc/sys/net/ipv4/conf/eth/proxy_arp: no such file or directory I use the

I guess I have stumbled upon a bug in gplpv drivers. If you try to re-enable an nic adapter after disabling it, it just hides out of blue. And you have to reboot. Latest version of gplpv drivers and Windows 2008 R2 here. Anyone else noticed the same issue? I wonder if this is related to hot-plugging something like

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s