similar to: Missing vnet interface in migration

On Fri, Jun 29, 2018 at 3:40 AM Thiago Oliveira <cpv.thiago@gmail.com> wrote: > Hi Ales, > > I would like to prevent the guests from different subnets start a > communication. In other words I have the subnet 192.168.1.0/24 and > 192.168.2.0/24 and the guests from 192.168.1.0/24 cannot reach/talk with > guests on 192.168.2.0/24 at the same host. Is this possible using a

Hi Ales, I would like to prevent the guests from different subnets start a communication. In other words I have the subnet 192.168.1.0/24 and 192.168.2.0/24 and the guests from 192.168.1.0/24 cannot reach/talk with guests on 192.168.2.0/24 at the same host. Is this possible using a filter like yours? Thank you. Thiago. Em qui, 28 de jun de 2018 às 09:37, Ales Musil <amusil@redhat.com>

On Thu, Jun 28, 2018 at 10:18:57AM +0200, Ales Musil wrote: > Hello, > > I would like to make filter that allows communication only between > specified VMs. Those VMs should be specified by their MAC address. The > filter should extend clean-traffic but I was not able to get it working > with that reference. I have came up with modified clean-traffic which works > fine [1].

Hello, I would like to make filter that allows communication only between specified VMs. Those VMs should be specified by their MAC address. The filter should extend clean-traffic but I was not able to get it working with that reference. I have came up with modified clean-traffic which works fine [1]. Is there a way to achieve the same behavior with reference to clean-traffic? Thank you. Best

Hallo! The attached patch repair the vnet-module (patch base is xen-3.1.0) - moves the "skb_pull" function from kernel to skb_util.c because pulling in the data will rise a "BUG_ON" in the kernel. - the skb_buff is not always possible to modify. (vnet_forward.c and etherip.c) The code now work''s.. I think with no or less time-penalty. Info for

This patch fixes the tools/vnet makefiles so that vnets will compile and includes updates to the vnet implementation. Vnet ids are increased to 128 bits. The vnet module will insmod whether xen-br0 exists or not. Signed-off-by: Mike Wray <mike.wray@hp.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

During concurrent 80 VM creation, each VM takes two network connections, libvirtd failed to respond. Neither restart libvirtd nor restart CIMOM helped. There were 152 vnet bridges found on this RHEL KVM host. After all the vnet bridges were manually removed, libvirtd responded normally again. Is there a known issue about the number limit of vnet bridges regarding libvirtd? Thank you. --Yih

On Wed, May 06, 2020 at 02:16:32PM +0800, Jason Wang wrote: > We tried to reserve space for vnet header before > xdp.data_hard_start. But this is useless since the packet could be > modified by XDP which may invalidate the information stored in the > header and there's no way for XDP to know the existence of the vnet > header currently. What do you mean? Doesn't XDP_PASS

On Wed, May 06, 2020 at 04:19:40PM +0800, Jason Wang wrote: > > On 2020/5/6 ??3:53, Michael S. Tsirkin wrote: > > On Wed, May 06, 2020 at 02:16:32PM +0800, Jason Wang wrote: > > > We tried to reserve space for vnet header before > > > xdp.data_hard_start. But this is useless since the packet could be > > > modified by XDP which may invalidate the information

On 19.04.2015 04:02, wh.h@foxmail.com wrote: > inquiry about differences between the tap and the vnet in the virt-manager > > when I establish the network by the first method: create a bridge with the help of Linux commad: brctl, tap0 device is created in the host and assigned to the guest OS. tap0 device gets a name “eth0” in the guest OS. > I use “ping ” command to test network

On 28.10.2016 11:09, Anton Gorlov wrote: > Can i assign static vnet* device for some guests? > What do you mean? vnet* devices are created by libvirt when a domain is being started (or on device hotplug). In general, unless all devices would be statically allocated, it would be impossible to guarantee certain vnet name. However, what you can do is to create the device yourself and then

On 28.10.2016 14:17, Anton Gorlov wrote: > 28.10.2016 23:32, Michal Privoznik пишет: > > > On my host node i using system created bridge. example > > brctl show br1 > bridge name bridge id STP enabled interfaces > br1 8000.0025907925d3 no eth1 > vnet0 >

31.10.2016 16:45, Laine Stump пишет: > ... but *is* in the status xml (i.e. the output of "visrh dumpxml > $domain" while the domain is running, and also the xml provided on stdin > to the qemu and network hooks when they are called). > > (also, what Vincent said in his email - names with the prefix "vnet" are > assumed to be "leftover" from a

03.11.2016 21:49, Vincent Bernat пишет: >>> ... but *is* in the status xml (i.e. the output of "visrh dumpxml >>> $domain" while the domain is running, and also the xml provided on stdin >>> to the qemu and network hooks when they are called). >>> (also, what Vincent said in his email - names with the prefix "vnet" are >>> assumed

Hi all, How can I see what vnet is attached to a certain kvm guest?? For example: I have a kvmguest1. When I launch this guest with virsh command, virsh creates a new vnetX interface for this guest. How can I extract this virtual net interface (vnet0, vnet1, vnet2 or so on) using a script?? Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

Hallo! Has anybody a working version for linux-2.6.16 ARCH=x86_64? As i see it correctly, there is a kernel-call for socketcall, with x86_64 will not have... (and this in kernel-module ?) wbr Robert Valentan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

❦ 3 novembre 2016 20:43 +0300, Anton Gorlov <stalker@altlinux.ru> : >> ... but *is* in the status xml (i.e. the output of "visrh dumpxml >> $domain" while the domain is running, and also the xml provided on stdin >> to the qemu and network hooks when they are called). >> >> (also, what Vincent said in his email - names with the prefix

We copy vnet header unconditionally in page_to_skb() this is wrong since XDP may modify the packet data. So let's keep a zeroed vnet header for not confusing the conversion between vnet header and skb metadata. In the future, we should able to detect whether or not the packet was modified and keep using the vnet header when packet was not touched. Fixes: f600b6905015 ("virtio_net: Add

On 10/28/2016 05:30 PM, Michal Privoznik wrote: > On 28.10.2016 14:17, Anton Gorlov wrote: >> 28.10.2016 23:32, Michal Privoznik пишет: >> >> >> On my host node i using system created bridge. example >> >> brctl show br1 >> bridge name bridge id STP enabled interfaces >> br1 8000.0025907925d3 no