search for: vifs

Netback and netfront only use one event channel to do tx / rx notification. This may cause unnecessary wake-up of process routines. This patch adds a new feature called feautre-split-event-channel to netback, enabling it to handle Tx and Rx event separately. Netback will use tx_irq to notify guest for tx completion, rx_irq for rx notification. If frontend doesn''t support this feature,

This patch adds code to handle SKB_GSO_TCPV6 skbs and construct appropriate extra or prefix segments to pass the large packet to the frontend. New xenstore flags, feature-gso-tcpv6 and feature-gso-tcpv6-prefix, are sampled to determine if the frontend is capable of handling such packets. Signed-off-by: Paul Durrant <paul.durrant@citrix.com> Cc: Wei Liu <wei.liu2@citrix.com> Cc: David

A buggy or malicious frontend should not be able to confuse netback. If we spot anything which is not as it should be then shutdown the device and don''t try to continue with the ring in a potentially hostile state. Well behaved and non-hostile frontends will not be penalised. As well as making the existing checks for such errors fatal also add a new check that ensures that there

VM traffic is already limited by a throughput limit, but there is no control over the maximum packet per second (PPS). In DDOS attack the major issue is rather PPS than throughput. With provider offering more bandwidth to VMs, it becames easy to coordinate a massive attack using VMs. Example: 100Mbits ~ 200kpps using 64B packets. This patch provides a new option to limit VMs maximum packets per

This dependence is undesirable and logically incorrect. It''s undesirable because Xen network protocol should not depend on a OS-specific constant. It''s incorrect because the ring slots required doesn''t correspond to the number of frags a SKB has (consider compound page frags). This patch removes this dependence by correctly counting the ring slots required.

...1 deletions(-) create mode 100644 tools/hotplug/Linux/vif-openvswitch diff --git a/tools/examples/xl.conf b/tools/examples/xl.conf index 9402c3f..625b1a4 100644 --- a/tools/examples/xl.conf +++ b/tools/examples/xl.conf @@ -9,7 +9,7 @@ #lockfile="/var/lock/xl" # default vif script -#vifscript="vif-bridge" +vifscript="vif-openvswitch" # default output format used by "xl list -l" #output_format="json" diff --git a/tools/hotplug/Linux/Makefile b/tools/hotplug/Linux/Makefile index 0605559..99bf87f 100644 --- a/tools/hotplug/Linux/Makefile +++...

> -----Original Message----- > From: Ewan Mellor [mailto:ewan@xensource.com] > Sent: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > >

time_after_eq() only works if the delta is < MAX_ULONG/2. For a 32bit Dom0, if netfront sends packets at a very low rate, the time between subsequent calls to tx_credit_exceeded() may exceed MAX_ULONG/2 and the test for timer_after_eq() will be incorrect. Credit will not be replenished and the guest may become unable to send packets (e.g., if prior to the long gap, all credit was exhausted).

Hi, > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? Toying with the vif-route script, I might have found a workaround for this issue. If I disable the ifconfig and ip route commands from vif-route script, and bring up vif interface by hand later on, everything seems to work. In other works,

# HG changeset patch # User Brendan Cully <brendan@cs.ubc.ca> # Date 1282083158 25200 # Node ID 74b9fe513d8591ca14233590062079b042abb68d # Parent 774dfc178c39bd3fe2ec14b4f96e60b78391b397 hotplug: 21549:8bcaec29574e breaks vif-script with arguments. For example, (vif-script ''vif-bridge bridge=eth1'') in xend-config.sxp will cause vif-setup to attempt to execute

Hi, I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and I''m facing some problems when I start the DomU. In detail, it means that the DomU IP-Adress will not be implemented in the Kernel routing table after starting the domU via "xm create /<path +configfle>" After making a "netstat -nr" it will not show the IPadress bound to the

Package: xen-utils-common Version: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 Severity: important Tags: patch security -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),

Hi, the vif scripts (vif-route, vif-bridge, etc.) that come with xen just don't work for me. I don't feel like I need a bridged setup. My ISP insists of routing the IPs of the domUs to my dom0. So now I'm using script=vif-route. But it has some caveats ... The vif-route script turns on proxy_arp, even though the domUs use the dom0 as a default gateway, for everything except their own

Package: src:xen Version: 4.17.3+10-g091466ba55-1~deb12u1 Severity: wishlist I wasn't sure if this script comes from Debian or Xen or somewhere else, so I thought it safest to report it here. /etc/xen/scripts/vif-bridge handles MTU settings in the vif, but the otherwise similar /etc/xen/scripts/vif-openvswitch does not. I added it in, here's the diff-c and the full fixed file is also

Hi, I've been generating linear models with lm(). I wanted to look at the VIF's for the coefficient. Using the vif() function from the package Design, I would get unusually high VIF's. However using vif() from the car package I get more reasonable values (ie in line with the quality of the model). What is the difference between the two vif functions? (I dont have access to the

Hi, we are trying to secure our Xen boxes with IPtables on Dom0 but we always seem to get cut off and can only cure it be rebooting the box. Has anyone got a sucessful config they can share that secures the server with one nic? We are using Xen 3.0.4 thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT

...r. (And, BTW 2nd vif of the FW6 & 1st vif of router 6 are connected via a third bridge) The idea is to get the 802.1Q port on the Router6 host (via the bridge), and then use virtual interfaces (eth1.xxx where xxx are the vlan ID) inside the XenU. Well, it works, only if I use mtu 1496 for the vifs. I know the physical interfaces (eepro1000) can cope with vlan natively. Don''t know for the bridge code but i''m not aware of limitations there. So it is a limitation on vif code ?? -- Yann Dupont, Cri de l''université de Nantes Tel: 02.51.12.53.91 - Fax: 02.51.12.58.60...

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: normal My setup is a basic one. No changes to the /etc/xen/* files. Network in a domU works perfectly fine. But, after shutdowning a domU, I can see the following lines in /var/log/debug: May 6 10:31:45 vaio logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/18/0 May 6 10:31:46 vaio logger: /etc/xen/scripts/vif-bridge: