similar to: [patch] xen bridged network setup fixes

Displaying 20 results from an estimated 500 matches similar to: "[patch] xen bridged network setup fixes"

2006 May 17
1
RE: RE: [Xen-changelog] Fix MOVS instruction emulation for HVM MMIO.
> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Gerd Hoffmann > Sent: 17 May 2006 07:43 > To: Petersson, Mats > Cc: xen-devel@lists.xensource.com; xen-changelog@lists.xensource.com > Subject: Re: [Xen-devel] RE: [Xen-changelog] Fix MOVS > instruction emulation for HVM MMIO. >
2006 Jul 07
7
[PATCH] xenconsole fix
xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2007 Nov 23
12
[SECURITY] preventing Hwaddr spoofing on bridge
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Is there a way to prevent hwaddr/mac address spoofing between DomU''s? So in a way ''binding'' a mac-address on boot time with a virtual interface? (with something like ebtables/arptables/etc?) Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla -
2008 Apr 14
0
Etch Release / Bond networking
Hello, I just setup a Xen server and wanted to use bond0 for my network connection. I ended up downloading and addeding the attatched file and making the following change in /etc/xen/xend-config.sxp. I added this line: (network-script 'network-bond netdev=bond0') Would this line be a good one to add to the commented lines and include the network-bond file in the scripts? Just thought
2010 Feb 10
0
Script for bond+vlan bridging from red hat
2007 Apr 18
2
unfixing fixmap_top
Rusty Russell wrote: > Chris: [RFC PATCH 12/33] Change __FIXADDR_TOP to leave room for the hypervisor. > - Replace with dynamic (Geerd) patch, put in paravirt_ops structure. > I'm looking at this, and I'm not sure that there needs to be a void (*set_fixmap_top)(unsigned long top) entry in paravirt ops. It seems to me that the hypervisor's init code can call the
2008 Dec 23
2
DomU strange network behavior
I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the
2006 Oct 12
2
[PATCH][RFC] do ifdown netdev before shutting down 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
2005 Nov 04
1
RE: Error "Device 0 (vif) could not be connected"
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-users] Error "Device 0
2011 Jan 26
3
missing vif.0 port after install xen4+centos5
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
2011 Jan 05
7
Xen Netloop module missing
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
2007 Apr 18
2
[PATCH] exec-shield style vdso move.
So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >
2007 Apr 18
2
[PATCH] exec-shield style vdso move.
So, is everyone happy with this smerge of Ingo and Gerd's work? Reposted below. Thanks, Rusty. -------- Forwarded Message -------- From: Linus Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: >
2007 Jul 31
1
[Bridge] brctl uses incorrect sysfs path
Hi, I noticed that brctl (or more accurately, libbridge) is using the wrong path when doing various lookups in sysfs: e.g. /sys/class/net/brXXX/stp_state when it should use /sys/class/net/brXXX/bridge/stp_state. This doesn't cause any problems on most systems as it falls back to the ioctl when the sysfs attempt fails; however the ioctl method is apparently deprecated. I believe the
2011 Sep 10
2
xen 4.1.1 missing veth0 <--> vif0.0 pairs
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
2011 Sep 10
2
xen 4.1.1 missing veth0 <--> vif0.0 pairs
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
2008 Feb 23
6
network-multinet usage?
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
2010 Jul 08
0
Bug#588406: xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set
Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was
2008 Mar 27
2
xenbr0 isn't created anymore
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)
2007 Sep 28
2
[Bridge] Flushing MAC-tables(?)
Dear list-members! I am using OpenWRT (www.openwrt.org) on two accesspoints. Within OpenWRT, the wireless interface and the ethernet interface are bridged to one interface (br0). Those two accesspoints are standing quite far from one another. Their WLAN-cells do not cross each other, meaning I have an area in between the two accesspoints, where there is no accesspoint of the two accessible: a