RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1947720 - Live update the interface to delete the Qos setting will crash the libvirtd
Summary: Live update the interface to delete the Qos setting will crash the libvirtd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: All
OS: Unspecified
high
unspecified
Target Milestone: beta
: ---
Assignee: Michal Privoznik
QA Contact: Yanqiu Zhang
URL:
Whiteboard:
Depends On: 1919619
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-09 03:07 UTC by yalzhang@redhat.com
Modified: 2021-12-07 22:02 UTC (History)
6 users (show)

Fixed In Version: libvirt-7.3.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1919619
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version: 7.1.0
Embargoed:

Attachments (Terms of Use)

Comment 5 Yanqiu Zhang 2021-06-08 07:59:50 UTC 
Verified on:
libvirt-7.4.0-1.el9.x86_64
qemu-kvm-6.0.0-4.el9.x86_64

Steps:
Scenario 1: by update-device
1. Add Qos setting
# pidof libvirtd
2055776
# virsh list
 Id   Name             State
--------------------------------
 1    avocado-vt-vm1   running

# virsh dumpxml avocado-vt-vm1 |grep /inter -B7
    <interface type='network'>
      <mac address='52:54:00:fb:73:62'/>
      <source network='default' portid='d43999bb-37db-424a-9555-d5ed723aea63' bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

Copy interface into net.xml, add Qos into net-Qos.xml, net-Qos-2.xml

# virsh update-device avocado-vt-vm1 net-Qos.xml 
Device updated successfully

# virsh dumpxml avocado-vt-vm1 |grep /inter -B11
...
      <bandwidth>
        <inbound average='2000' peak='3000' burst='2048'/>
        <outbound average='256' peak='512' burst='512'/>
      </bandwidth>
...
# pidof libvirtd
2055776

2.update the Qos
# virsh update-device avocado-vt-vm1 net-Qos-2.xml 
Device updated successfully

]# virsh dumpxml avocado-vt-vm1 |grep /inter -B11
...
      <bandwidth>
        <inbound average='512' peak='1024' burst='32'/>
        <outbound average='128' peak='1024' burst='32'/>
      </bandwidth>
...
# pidof libvirtd
2055776

3. Delete Qos
# virsh update-device avocado-vt-vm1 net.xml 
Device updated successfully

# virsh dumpxml avocado-vt-vm1 |grep /inter -B7
    <interface type='network'>
      <mac address='52:54:00:fb:73:62'/>
      <source network='default' portid='ab3abf2e-2647-4c15-8681-11aac4a93b9c' bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

# pidof libvirtd
2055776

Scenario 2: by domiftune 
1.Add
#  virsh domiftune avocado-vt-vm1 vnet0 --inbound 2000,3000,2048 --outbound 2000,4000,1024

# virsh dumpxml avocado-vt-vm1 |grep /inter -B11
...
      <bandwidth>
        <inbound average='2000' peak='3000' burst='2048'/>
        <outbound average='2000' peak='4000' burst='1024'/>
      </bandwidth>
...
# pidof libvirtd
2055776

2. Update
#  virsh domiftune avocado-vt-vm1 vnet0 --inbound 512,1024,32 --outbound 128,1024,32

# virsh dumpxml avocado-vt-vm1 |grep /inter -B11
...
      <bandwidth>
        <inbound average='512' peak='1024' burst='32'/>
        <outbound average='128' peak='1024' burst='32'/>
      </bandwidth>
…
# pidof libvirtd
2055776

3. Delete
#  virsh domiftune avocado-vt-vm1 vnet0 --inbound 0,0,0 --outbound 0,0,0

# virsh dumpxml avocado-vt-vm1 |grep /inter -B7
    <interface type='network'>
      <mac address='52:54:00:fb:73:62'/>
      <source network='default' portid='ab3abf2e-2647-4c15-8681-11aac4a93b9c' bridge='virbr0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
# pidof libvirtd
2055776
Note You need to log in before you can comment on or make changes to this bug.