yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #92605
[Bug 2026284] Re: virtio-net-tx-queue-size reflects in nova conf but not for the vm even after a hard reboot
This does not appear to be a charm issue, but rather it appears to
potentially be a nova issue. I can confirm that setting the
rx_queue_size and tx_queue_size results in the nova.conf file being
updated by the charm, but that the resulting hard rebooted guest does
not get the tx_queue_size, only the rx_queue_size.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2026284
Title:
virtio-net-tx-queue-size reflects in nova conf but not for the vm even
after a hard reboot
Status in OpenStack Nova Compute Charm:
New
Status in OpenStack Compute (nova):
Incomplete
Bug description:
After modifying the nova compute config options,
- virtio-net-rx-queue-size=512
- virtio-net-tx-queue-size=512
I hard rebooted my vm and spawned a new vm and what I see (on both of them) is:
- virsh xml
```
# virsh dumpxml 2 | grep -i queue
<driver name='vhost' rx_queue_size='512'/>
```
- nova.conf
```
# grep -i queue /etc/nova/nova.conf
tx_queue_size = 512
rx_queue_size = 512
```
- inside the vm
```
root@jammy-135110:~# ethtool -g ens2
Ring parameters for ens2:
Pre-set maximums:
RX: 512
RX Mini: n/a
RX Jumbo: n/a
TX: 256
Current hardware settings:
RX: 512
RX Mini: n/a
RX Jumbo: n/a
TX: 256
```
The RX config gets propagated, but the TX config does not
Please let me know if any more information is needed.
----------------------------------------------------------
env:
- focal ussuri
- nova-compute:
charm: nova-compute
channel: ussuri/stable
revision: 669
- this is a freshly deployed openstack on vms (not on baremetal)
- libvirt: 6.0.0-0ubuntu8.16
- nova-compute-libvirt 21.2.4-0ubuntu2.5
- qemu 4.2-3ubuntu6.27
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/2026284/+subscriptions