similar to: loopback.nloopbacks

Displaying 20 results from an estimated 10000 matches similar to: "loopback.nloopbacks"

2006 Sep 20
2
Bug#388486: xen-utils-common: upgrade new 2.6.17-2-xen breaks create domU until modprobe netloop nloopbacks=n
Package: xen-utils-common Version: 3.0+hg11292-2 Severity: normal After a recent etch upgrade (2.6.17, xen-3.0.2) I was unable to "xm create" until I "modprobe netloop nloopbacks=10" Error was network-bridge couln't create vif interface (backend not found). brctl addbr ... fails because of no free netloop device. passing more nloopbacks device to the module fixed the
2009 Apr 21
1
options netloop nloopbacks=<n> ignored
Hi list, since release 5.3 all kernels ignore options netloop nloopbacks=<n> within /etc/modprobe.conf If <n> is smaller than four there are always four vifs created. If <n> is bigger than four the appropriate number of vifs are created. Is this expected/new/feature/bug? Henry
2006 Sep 20
3
Bug#388352: xen-hypervisor-3.0-unstable-1-amd64: veth0 is missing
Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for
2008 Jan 31
3
xen 3.2 network problems
Hi, I try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I
2010 Dec 09
0
[PATCH linux-2.6.18-xen] make netloop permanent
Hi, with reference to RH BZ#567540 [0], this patch makes the netloop module permanent (like netback is currently). It reverts parts of xen-unstable c/s 9019:271cb04a4f2b [1] [2] (though that has a typo: "__init clean_loopback", so it was probably changed later too). The patch fixes the problem of "rmmod netloop" hanging, resulting in blocked tasks and inability to shut down
2006 Sep 05
0
Problem with network-bridge script and veth0
Hello, Since my last update of xen, I am having problems with bridges and xen. When I want to start a bridge on the dom0 (to run a domU in a different vlan than the default) I run /etc/xen/scripts/network-bridge start netdev=eth0.302 bridge=xen-br302 antispoof=no where eth0.302 is an interface associated with my vlan 302 (it tags with this vlan identifier). The problem I have is that it
2007 May 14
3
Number of xenbr''s limited to four on openSuSE 10.2 ?
Hi Group ... 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
2009 Jan 11
0
network-bridge status something strange
Hello, I have got something strange when I done a /etc/xen/scripts/network-bridge status : 201: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:15:17:8d:cb:1c brd ff:ff:ff:ff:ff:ff And when I done a /etc/xen/scripts/network-bridge I have got this : Link veth0 1 is missing. This may be because you have reached the limit of the number of
2009 Aug 05
2
bridge vs macvlan performance (was: some veth related issues)
Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where
2009 Aug 05
2
bridge vs macvlan performance (was: some veth related issues)
Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where
2008 Feb 01
3
No peth interface for xenbr4 and xenbr5
Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"
2012 Jul 13
11
Backport requests of cs 23420..23423 for 4.0 and 4.1
Hi, we are experiencing significant performance degradation after live migration of hvm domains in Xen 4.0 (SLES11 SP1): after live migration the performance is dropping to less than 90%. I did a backport of cs 23420-23423 and the performance is okay now. I would like to request to include these changesets in 4.0 and 4.1. The backport is quite trivial, I can send patches if you are willing to
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
2020 Feb 12
1
[PATCH] virtio: Work around frames incorrectly marked as gso
On Wed, Feb 12, 2020 at 10:03:31AM +0000, Anton Ivanov wrote: > > > On 11/02/2020 10:37, Michael S. Tsirkin wrote: > > On Tue, Feb 11, 2020 at 07:42:37AM +0000, Anton Ivanov wrote: > > > On 11/02/2020 02:51, Jason Wang wrote: > > > > > > > > On 2020/2/11 ??12:55, Anton Ivanov wrote: > > > > > > > > > > > >
2016 Apr 11
2
Re: [Bug 1325687] network type="ethernet" not supported with LXC
Hi Team I'm trying to launch LXC VM with libvirt 1.2.12 having commit *22cff52a2b8e06c913b1f97767e5d3**90fb17fc3b *with below XML configuration.. <domain type="lxc"> <uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid> <name>test</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type
2007 Mar 20
62
RFC: [0/2] Remove netloop by lazy copying in netback
Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it
2007 Nov 28
1
network-bridge does not create veth or peth devices
Hi I am trying to install xen (64bit) on a Dell PowerEdge 2900. The installation process was something like the following: ----- apt-get install iproute bridge-utils python-twisted binutils zlib1g-dev python-dev transfig bzip2 screen ssh debootstrap libcurl3-dev libncurses5-dev x-dev build-essential gettext python-pyopenssl python-pam python-xml latex tetex-extra tetex-base
2011 Feb 18
1
problem for add second bridge xenbr1
Dear I need create second bridge xenbr1 for separate traffic between my virtual machine , I following this step but show message that Link veth0 is missing, how I can create veth0 ? When I run script for create xenbr1 ./network-bridge netdev=eth1 bridge=xenbr1 start Shwo this message Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the
2016 Jan 30
1
bonding (IEEE 802.3ad) not working with qemu/virtio
On 01/30/2016 07:59 AM, David Miller wrote: > From: Nikolay Aleksandrov <nikolay at cumulusnetworks.com> > Date: Fri, 29 Jan 2016 22:48:26 +0100 > >> On 01/29/2016 10:45 PM, Jay Vosburgh wrote: >>> Nikolay Aleksandrov <nikolay at cumulusnetworks.com> wrote: >>> >>>> On 01/25/2016 05:24 PM, Bj?rnar Ness wrote: >>>>> As subject