virtio-net-tx-queue-size reflects in nova conf but not for the vm even after a hard reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned | ||
OpenStack Nova Compute Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After modifying the nova compute config options,
- virtio-
- virtio-
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_
```
- nova.conf
```
# grep -i queue /etc/nova/nova.conf
tx_queue_size = 512
rx_queue_size = 512
```
- inside the vm
```
root@jammy-
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-
- qemu 4.2-3ubuntu6.27
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.