search for: vhostus

I am planning to configure vlan on vhostuser interfaces in the libvirt xml, it throws out error. Does this configuration is supported ? I can install higher version if required. *Error:* unsupported configuration: an interface of type 'vhostuser' is requesting a vlan tag, but that is not supported for this type of connection *Libv...

Hi, I'm having trouble starting a VM with vhostuser interfaces. I have a simple configuration where a VM running Debian has 1 vhostuser interface plugged into an OVS switch where a DPDK interface is already plugged in. $ ovs-vsctl show: Bridge "switch1" Port "switch1" Interface "switch1" type:...

On 02/22/2018 11:41 AM, Riccardo Ravaioli wrote: > Hi, > > I'm having trouble starting a VM with vhostuser interfaces. > > I have a simple configuration where a VM running Debian has 1 vhostuser > interface plugged into an OVS switch where a DPDK interface is already > plugged in. > $ ovs-vsctl show: > Bridge "switch1" >     Port "switch1" >         Interfa...

...0" and it was apparently needed in the past with old versions of libvirt. I see examples on the net where it is used to configure interfaces with shell commands. I don't need it. I see that everything works fine without the <script path="/opt/oa/etc/qemu-ifup"/> line, for vhostuser and ethernet interfaces. Are there any side effects or can I safely remove that line? Thanks again! Riccardo On 22 February 2018 at 20:55, Laine Stump <laine@redhat.com> wrote: > [...] > > <interface type="vhostuser"> > > <script path="/o...

...<reconnect enabled='yes' timeout='5' /> </source> <queue num='4'/> </vhost-user-blk-pci> As Cole's suggestion, the better design with all vhost-user-scsi/blk features would like this: vhost-user-blk: <disk type='vhostuser' device='disk'> <source type='unix' path='/path/to/vhost-user-blk.sock' mode='client'> <reconnect enabled='yes' timeout='5' /> </source> <target dev='vda' bus='virtio'/> <queue nu...

...nt to use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? this is my xml: <cpu> <numa> <cell id='0' cpus='0' memory='1048576' memAccess='shared'/> <cell id='1' cpus='1' memory='1048576' memAccess='...

...t; > > <queue num='4'/> > > </vhost-user-blk-pci> > > > > As Cole's suggestion, the better design with all vhost-user-scsi/blk > > features would like this: > > > > vhost-user-blk: > > > > <disk type='vhostuser' device='disk'> > > <source type='unix' path='/path/to/vhost-user-blk.sock' mode='client'> > > <reconnect enabled='yes' timeout='5' /> > > </source> > > <target dev='vda...

Hi Guys, And I want to add the vhost-user-scsi-pci/vhost-user-blk-pci support for libvirt. The usage in qemu like this: Vhost-SCSI -chardev socket,id=char0,path=/var/tmp/vhost.0 -device vhost-user-scsi-pci,id=scsi0,chardev=char0 Vhost-BLK -chardev socket,id=char1,path=/var/tmp/vhost.1 -device vhost-user-blk-pci,id=blk0,chardev=char1 What type should I add for libvirt. Type1: <hostdev

...9;5' /> > </source> > <queue num='4'/> > </vhost-user-blk-pci> > > As Cole's suggestion, the better design with all vhost-user-scsi/blk > features would like this: > > vhost-user-blk: > > <disk type='vhostuser' device='disk'> > <source type='unix' path='/path/to/vhost-user-blk.sock' mode='client'> > <reconnect enabled='yes' timeout='5' /> > </source> > <target dev='vda' bus='virtio...

...this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. >> because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? >> >> this is my xml: >> <cpu> >> <numa> >> <cell id='0' cpus='0' memory='1048576' memAccess='shared'/> >> <cell id='1' cpus=...

...that socket. target bus=virtio vs bus=scsi is already used to distinguish between virtio-blk and virtio-scsi, so I think we can keep that bit as is, with the <address type=drive|pci> to match. We just need to differentiate between plain virtio and vhost-user network devices already have vhostuser support: <interface type='vhostuser'> <source type='unix' path='/tmp/vhost1.sock' mode='server|client'/> <model type='virtio'/> </interface> Internally that <source> is a virDomainChrSourceDefPtr which is our...

Hi All, First time mailing here. I have installed on a CentOS 7.0 KVM (with DPDK and OVS) one Deep Packet Inspection VM. I have one channel and some virtual traffic generator. The traffic is lost between dpdk vhostuser and the DPI VM. The setup is attached. Any suggestions or ideas? Regarding the OVS+DPDK configuration, the following configuration is already made: - SELINUX is disabled - QEMU 2.9.0 was downloaded from sources - All Linux packages were updated for QEMU 2.9.0 - DPDK source was downloaded - Paths...

In my Linux VM, I am unable to change scatter-gather / tx-checksumming / TCP-segmentation offload features by ethtool command. I am using virtio nic with vhostuser port backend. It shows me an error: Cannot change tx-checksumming Cannot change scatter-gather Cannot change tcp-segmentation offload Could not change any device features Ony running command ethtool -k ens3, I get the following: [image: image.png] If there is something that needs to be changed...

...o use this qemu command '-object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on' with libvirt but i can't find the 'mem-path' and 'share' in the documentation. >because the vhost-user backend based on 'share=on' parameter and libvirt support vhostuser i guess there maybe another way to support this parameter? > >this is my xml: > <cpu> > <numa> > <cell id='0' cpus='0' memory='1048576' memAccess='shared'/> > <cell id='1' cpus='1' memory='104...

Hello there, i am trying to start my VM with 2 virtio interfaces as a vhost-user interface Following is my relevant xml network configuration " <interface type='vhostuser'> <mac address='52:54:00:c7:ac:38'/> <source type='unix' path='/tmp/vhost1.sock' mode='server'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09...

On 5/3/19 10:19 AM, Harsh Gondaliya wrote: > In my Linux VM, I am unable to change scatter-gather / tx-checksumming / > TCP-segmentation offload features by ethtool command. I am using virtio nic > with vhostuser port backend. > It shows me an error: > Cannot change tx-checksumming > Cannot change scatter-gather > Cannot change tcp-segmentation offload > Could not change any device features You need to enable those in domain XML: https://libvirt.org/formatdomain.html#elementsDriverBackend...

...s-use-qapi_free_SocketAddress-in-cleanup.patch [bz#1354090] - kvm-tap-use-an-exit-notifier-to-call-down_script.patch [bz#1354090] - kvm-slirp-use-exit-notifier-for-slirp_smb_cleanup.patch [bz#1354090] - kvm-net-do-not-use-atexit-for-cleanup.patch [bz#1354090] - Resolves: bz#1354090 (Boot guest with vhostuser server mode, QEMU prompt 'Segmentation fault' after executing '(qemu)system_powerdown') * Fri Jul 08 2016 Miroslav Rezanina <mrezanin at redhat.com> - rhev-2.3.0-31.el7_2.18 - kvm-vhost-user-disable-chardev-handlers-on-close.patch [bz#1351892] - kvm-char-clean-up-remaining-c...

...oss its releases. Moreover, some hypervisors may pose some restrictions on actual value. For instance, QEMU v2.9 requires value to be a power of two from [256, 1024] range. In addition to that, this may work only for a subset of interface types, e.g. aforementioned QEMU enables this option only for vhostuser type. Since 3.7.0 (QEMU and KVM only) multiqueue only supports vhost as backend driver. # rpm -q libvirt qemu-kvm-rhev libvirt-3.2.0-14.el7_4.3.x86_64 qemu-kvm-rhev-2.9.0-16.el7_4.9.x86_64 1. the xml as below <interface type='direct'> <mac address='52:54:00:00:b5:9...

...9;dir' device='disk'> <driver name='qemu' type='fat'/> <source dir='/usr/src/dpdk-stable-16.11.1'/> <target dev='vdb' bus='virtio'/> <readonly/> </disk> <interface type='vhostuser'> <mac address='00:00:00:00:00:01'/> <source type='unix' path='/var/run/openvswitch/dpdkvhostuser0' mode='client'/> <model type='virtio'/> <driver queues='2'> <host mrg_rxbuf=&...

...reover, some hypervisors may pose > some restrictions on actual value. For instance, QEMU v2.9 requires value > to be a power of two from [256, 1024] range. In addition to that, this may > work only for a subset of interface types, e.g. aforementioned QEMU enables > this option only for vhostuser type. Since 3.7.0 (QEMU and KVM only) > multiqueue only supports vhost as backend driver. > > # rpm -q libvirt qemu-kvm-rhev > libvirt-3.2.0-14.el7_4.3.x86_64 > qemu-kvm-rhev-2.9.0-16.el7_4.9.x86_64 > > 1. the xml as below > <interface type='direct'> >...