similar to: Bond & Team: RX dropped packets

This is that system with the missing management port, and I'm still fighting it. Everything *looks* right: 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:25:90:0a:42:87 brd ff:ff:ff:ff:ff:ff inet 192.168.0.100/24 brd 192.168.0.255 scope global enp6s0 ip route 192.168.0.0/24 dev enp6s0 proto kernel scope link

On 10/26/2017 10:38 AM, Ashish Kurian wrote: > Hi Yalan and Michal, > > Thank you for your response. So what I understand is that I can change > rx_queue size even if I use direct type interface and qemu driver as long > as the driver is virtio. Am I right? Yes. > If that is the case why am I getting > the error saying that > > error: XML document failed to validate

Dear Users/Developers, I am using a KVM Ubuntu VM as a degrader to apply specific delays to incoming packets. As the delay for my packets can be higher than 7.5 seconds, there is not enough buffer on my interface to buffer all the packets. Therefore those overflowing packets are dropped in the machine and not forwarded. When I tried to use the command ethtool -G ens8 rx 512 to increase the

Once upon a time, mark <m.roth at 5-cent.us> said: > This is that system with the missing management port, and I'm still > fighting it. Everything *looks* right: > > 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 00:25:90:0a:42:87 brd ff:ff:ff:ff:ff:ff > inet 192.168.0.100/24 brd

Hi all, I've got on AD DC using Samba 4.4.3 on Centos7 which accept Kerberos connections (kinit is working), which accept ldapsearch with credentials but which refuse ldapsearch with GSSAPI. The issue does not seem to be coming from the client as I discovered this issue writing a script to test all 22 DC, and all 21 others DC are working well from that client. The error: SASL/GSSAPI

More information, making me more crazy: - ldapsearch without SASL is working from any host: ldapsearch -D 'CN=user-ldapmodify,OU=OurUsers,DC=ad,DC=domain,dc=tld' -w Passw0rd -x -ZZ -b 'dc=ad,DC=domain,dc=tld' -h dc106 sAMAccountName=administrator dn - ldapsearch with SASL is not working (Kerberos ticket existing following a working kinit) from any host but it works when launched

Solved : ) Reminder of the issue: Every services (CIFS, Kerberos, LDAP, DNS, RPC) on one DC were working well and ldapsearch using DN and password were also working. The only thing which was not working was ldapsearch using GSSAPI authentication with the following error: SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic

Hi Michal, What I found was that when I restarted the machine and did a virsh edit command to see the xml config, I see that it is was not actually changed. This suggests why I saw 256 again after restarting. So now I tried again to edit the xml via virsh edit command and used the following to set the parameters. <driver name='qemu' txmode='iothread' ioeventfd='on'

Hi Ashish, IMO, it is yes, no way to increase tx_queue_size for direct type interface ------- Best Regards, Yalan Zhang IRC: yalzhang Internal phone: 8389413 On Thu, Oct 26, 2017 at 3:38 PM, Ashish Kurian <ashishbnv@gmail.com> wrote: > Hi Yalan, > > In the previous email you mentioned "tx_queue_size='512' will not work in > the guest with direct type

On 10/25/2017 01:53 PM, Ashish Kurian wrote: > Dear Users/Developers, > > I am using a KVM Ubuntu VM as a degrader to apply specific delays to > incoming packets. As the delay for my packets can be higher than 7.5 > seconds, there is not enough buffer on my interface to buffer all the > packets. Therefore those overflowing packets are dropped in the machine and > not

Hi Michal, Mine is iplab@iceman:~$ libvirtd --version libvirtd (libvirt) 1.3.1 I think this can be the issue. I will update and try again Best Regards, Ashish Kurian On Thu, Oct 26, 2017 at 10:46 AM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 10/26/2017 10:38 AM, Ashish Kurian wrote: > > Hi Yalan and Michal, > > > > Thank you for your response. So what I

On 20/09/2019 04:55, Carlos A. Carnero Delgado wrote: > Hi! > > I just upgraded a machine to 7.7.1908 and the default route is not being > set on boot. This particular server has a bonded interface, and the > corresponding configuration for the master is ( > /etc/sysconfig/network-scripts/ifcfg-bond0): > > TYPE=Bond > BOOTPROTO=none > DEFROUTE=yes >

Hi Michal, I installed the latest version from the git and did run the libvirt from the new directory using /home/to/your/checkout/daemon/libvirtd But I still see that the version is 1.3.1. I have also stopped the already running libvirt daemon and ran the new daemon from the directory and it is showing 1.3.1 Best Regards, Ashish Kurian On Thu, Oct 26, 2017 at 10:50 AM, Ashish Kurian

Hi! I just upgraded a machine to 7.7.1908 and the default route is not being set on boot. This particular server has a bonded interface, and the corresponding configuration for the master is ( /etc/sysconfig/network-scripts/ifcfg-bond0): TYPE=Bond BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes NAME=bond0 DEVICE=bond0 ONBOOT=yes IPADDR=10.3.20.131 PREFIX=24

Hi Ashish, I have tested with your xml in the first mail, and it works for rx_queue_size(see below). multiqueue need to work with vhost backend driver. And when you set "queues=1" it will ignored. Please check your qemu-kvm-rhev package, should be newer than qemu-kvm-rhev-2.9.0-16.el7_4.2 And the logs? tx_queue_size='512' will not work in the guest with direct type interface,

Hi all, We are hitting an error in the centos 7 installation with our kickstart configuration. =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File

Hi Michal, An update to what I have already said : when I try adding <driver name='qemu' txmode='iothread' ioeventfd='on' event_idx='off' queues='1' rx_queue_size='512' tx_queue_size='512'> although it showed me the error as mentioned, when I checked the xml again I saw that <driver name='qemu' txmode='iothread'

Hi Yalan and Michal, Thank you for your response. So what I understand is that I can change rx_queue size even if I use direct type interface and qemu driver as long as the driver is virtio. Am I right? If that is the case why am I getting the error saying that error: XML document failed to validate against schema: Unable to validate doc against /usr/share/libvirt/schemas/domain.rng Extra

Hi Yalan, Thank you for your response. I do not have the following packages installed vhost backend driver qemu-kvm-rhev package Are these packages available for free? How can I install them? In my KVM VM, I must have an IP address to the interfaces that I am trying to increasing the buffers. That is the reason I was using macvtap (direct type interface). Is it possible to have my interfaces

Hi Yalan, In the previous email you mentioned "tx_queue_size='512' will not work in the guest with direct type interface, in fact, no matter what you set, it will not work and guest will get the default '256'. " So if I am using macvtap for my interfaces, then the device type will always be direct type. Does it mean that there is no way I can increase the buffer size