search for: elementsnicsbridge

...as I start a domain that uses bridged networking. The XML specification of the domain contains the following configuration <interface type='bridge'> <source bridge='br0'/> </interface> The libvirt documentation ( http://libvirt.org/formatdomain.html#elementsNICSBridge) and other discussions online tell me that I just need to include the <target dev='desired_dev_name'/> tag in the XML specification of the domain under the <interface> tag. Unfortunately doing so appears to have no effect; the tun device created and 'enslaved' in the bri...

...n of the >> domain contains the following configuration >> >> <interface type='bridge'> >> <source bridge='br0'/> >> </interface> >> >> The libvirt documentation (http://libvirt.org/formatdoma >> in.html#elementsNICSBridge) and other discussions online tell me that I >> just need to include the <target dev='desired_dev_name'/> tag in the XML >> specification of the domain under the <interface> tag. Unfortunately doing >> so appears to have no effect; the tun device created and ...

...etworking. The XML > specification of the domain contains the following configuration > > <interface type='bridge'> > <source bridge='br0'/> > </interface> > > The libvirt documentation > (http://libvirt.org/formatdomain.html#elementsNICSBridge) and other > discussions online tell me that I just need to include the <target > dev='desired_dev_name'/> tag in the XML specification of the domain > under the <interface> tag. Unfortunately doing so appears to have no > effect; the tun device created and '...

...faces with an IP address inside the VM >>> to be bridged to the physical interfaces on the host? >>> => Yes, you can create a linux bridge with physical interface connected, >>> and use bridge type interface. Refer to https://libvirt.org/formatd >>> omain.html#elementsNICSBridge >>> direct type is also ok (but your host and guest have no access to each >>> other). >>> >>> Is it also a possibility that I change the rx and tx buffer on the >>> physical interface on the host and it is reflected automatically inside the >>>...

...to have my interfaces with an IP address inside the VM to >> be bridged to the physical interfaces on the host? >> => Yes, you can create a linux bridge with physical interface connected, >> and use bridge type interface. Refer to https://libvirt.org/formatd >> omain.html#elementsNICSBridge >> direct type is also ok (but your host and guest have no access to each >> other). >> >> Is it also a possibility that I change the rx and tx buffer on the >> physical interface on the host and it is reflected automatically inside the >> VM as you said it will...

...P address inside the VM >>>> to be bridged to the physical interfaces on the host? >>>> => Yes, you can create a linux bridge with physical interface >>>> connected, and use bridge type interface. Refer to >>>> https://libvirt.org/formatdomain.html#elementsNICSBridge >>>> direct type is also ok (but your host and guest have no access to each >>>> other). >>>> >>>> Is it also a possibility that I change the rx and tx buffer on the >>>> physical interface on the host and it is reflected automatically ins...

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,