> -----Original Message-----
> From: <email address hidden> <email address hidden> On Behalf Of
> Noam Angel
> Sent: Thursday, August 30, 2018 7:30 PM
> To: Moshe Levi <email address hidden>
> Subject: [Bug 1789074] Re: failed to boot guest with vnic_type direct when
> rx_queue_size and tx_queue_size are set
>
> If the regression is also in OSP13, can you backport to queens aswell?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbu
> gs.launchpad.net%2Fbugs%2F1789074&data=02%7C01%7Cmoshele%40
> mellanox.com%7Cef098d3c842e4a582d9908d60e96b015%7Ca652971c7d2e4d
> 9ba6a4d149256f461b%7C0%7C0%7C636712437707120011&sdata=Ch9PXl
> 4S8FPNg1k6GnwO10DPy%2BU4SfwC60zzqe5Oilg%3D&reserved=0
>
> Title:
> failed to boot guest with vnic_type direct when rx_queue_size and
> tx_queue_size are set
>
> Status in OpenStack Compute (nova):
> In Progress
> Status in OpenStack Compute (nova) rocky series:
> New
>
> Bug description:
> Description of problem:
>
> Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices.
> This makes VM spawn to fail. The configurable RX/TX Queue Size code is
> similar all the way from OSP10 to OSP13, so it's possible the issue is present
> also on other releases.
>
> Version-Release number of selected component (if applicable):
> OSP13 z3
>
> How reproducible:
>
> (quick and dirty way)
> Change nova config file
>
> # crudini --set /var/lib/config-data/puppet-
> generated/nova_libvirt/etc/nova/nova.conf libvirt rx_queue_size 1024
> # crudini --set /var/lib/config-data/puppet-
> generated/nova_libvirt/etc/nova/nova.conf libvirt tx_queue_size 1024
>
> # restart nova_compute container
> docker restart nova_compute
>
> # boot a VM with an SRIOV (PF or VF) interface
>
> Actual results:
> Nova add on the sriov port section rx_queue_size
>
> <interface type="hostdev" managed="yes">
> <mac address="fa:16:3e:9d:f0:52"/>
> <driver name="vhost" rx_queue_size="1024"/>
> <source>
> <address type="pci" domain="0x0000" bus="0x01" slot="0x14"
> function="0x7"/>
> </source>
> <vlan>
> <tag id="435"/>
> </vlan>
>
> Expected results:
>
> <interface type='hostdev' managed='yes'>
> <mac address='fa:16:3e:83:b2:84'/>
> <driver name='vfio'/>
> <source>
> <address type='pci' domain='0x0000' bus='0x01' slot='0x14'
> function='0x7'/>
> </source>
> <vlan>
> <tag id='435'/>
> </vlan>
> <alias name='hostdev0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x05'
> function='0x0'/>
> </interface>
>
> Additional info:
>
> To manage notifications about this bug go to:
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbu
> gs.launchpad.net%2Fnova%2F%2Bbug%2F1789074%2F%2Bsubscriptions&am
> p;data=02%7C01%7Cmoshele%40mellanox.com%7Cef098d3c842e4a582d990
> 8d60e96b015%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636712
> 437707120011&sdata=cOpCsejNPt2AIoQCzFhm2pyV92gyzbvgLIJyM1Hyr
> NA%3D&reserved=0
Let first get it merged in master :)
> -----Original Message----- /emea01. safelinks. protection. outlook. com/?url= https%3A% 2F%2Fbu net%2Fbugs% 2F1789074& amp;data= 02%7C01% 7Cmoshele% 40 com%7Cef098d3c8 42e4a582d9908d6 0e96b015% 7Ca652971c7d2e4 d 61b%7C0% 7C0%7C636712437 707120011& amp;sdata= Ch9PXl 0DPy%2BU4SfwC60 zzqe5Oilg% 3D& reserved= 0 config- data/puppet- nova_libvirt/ etc/nova/ nova.conf libvirt rx_queue_size 1024 config- data/puppet- nova_libvirt/ etc/nova/ nova.conf libvirt tx_queue_size 1024 "fa:16: 3e:9d:f0: 52"/> size="1024" /> 'fa:16: 3e:83:b2: 84'/> /emea01. safelinks. protection. outlook. com/?url= https%3A% 2F%2Fbu net%2Fnova% 2F%2Bbug% 2F1789074% 2F%2Bsubscripti ons&am 02%7C01% 7Cmoshele% 40mellanox. com%7Cef098d3c8 42e4a582d990 7Ca652971c7d2e4 d9ba6a4d149256f 461b%7C0% 7C0%7C636712 amp;sdata= cOpCsejNPt2AIoQ CzFhm2pyV92gyzb vgLIJyM1Hyr reserved= 0
> From: <email address hidden> <email address hidden> On Behalf Of
> Noam Angel
> Sent: Thursday, August 30, 2018 7:30 PM
> To: Moshe Levi <email address hidden>
> Subject: [Bug 1789074] Re: failed to boot guest with vnic_type direct when
> rx_queue_size and tx_queue_size are set
>
> If the regression is also in OSP13, can you backport to queens aswell?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
> gs.launchpad.
> mellanox.
> 9ba6a4d149256f4
> 4S8FPNg1k6GnwO1
>
> Title:
> failed to boot guest with vnic_type direct when rx_queue_size and
> tx_queue_size are set
>
> Status in OpenStack Compute (nova):
> In Progress
> Status in OpenStack Compute (nova) rocky series:
> New
>
> Bug description:
> Description of problem:
>
> Nova compute forces the virtio RX/TX Queue Size also on SRIOV devices.
> This makes VM spawn to fail. The configurable RX/TX Queue Size code is
> similar all the way from OSP10 to OSP13, so it's possible the issue is present
> also on other releases.
>
> Version-Release number of selected component (if applicable):
> OSP13 z3
>
> How reproducible:
>
> (quick and dirty way)
> Change nova config file
>
> # crudini --set /var/lib/
> generated/
> # crudini --set /var/lib/
> generated/
>
> # restart nova_compute container
> docker restart nova_compute
>
> # boot a VM with an SRIOV (PF or VF) interface
>
> Actual results:
> Nova add on the sriov port section rx_queue_size
>
> <interface type="hostdev" managed="yes">
> <mac address=
> <driver name="vhost" rx_queue_
> <source>
> <address type="pci" domain="0x0000" bus="0x01" slot="0x14"
> function="0x7"/>
> </source>
> <vlan>
> <tag id="435"/>
> </vlan>
>
> Expected results:
>
> <interface type='hostdev' managed='yes'>
> <mac address=
> <driver name='vfio'/>
> <source>
> <address type='pci' domain='0x0000' bus='0x01' slot='0x14'
> function='0x7'/>
> </source>
> <vlan>
> <tag id='435'/>
> </vlan>
> <alias name='hostdev0'/>
> <address type='pci' domain='0x0000' bus='0x00' slot='0x05'
> function='0x0'/>
> </interface>
>
> Additional info:
>
> To manage notifications about this bug go to:
> https:/
> gs.launchpad.
> p;data=
> 8d60e96b015%
> 437707120011&
> NA%3D&