Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
when changing interface parameters with 'inbound' or 'outbound' option on first time, libvirtd will be crashed.
Version-Release number of selected component (if applicable):
# rpm -q libvirt
libvirt-0.9.9-1.el6.x86_64
How reproducible:
always
Steps to Reproduce:
# virsh start foo
Domain demo started
# virsh domiftune foo vnet0
inbound.average: 0
inbound.peak : 0
inbound.burst : 0
outbound.average: 0
outbound.peak : 0
outbound.burst : 0
# virsh domiftune foo vnet0 --inbound 10000
error: Unable to set interface parameters
error: End of file while reading data: Input/output error
or
# virsh domiftune demo vnet0 --outbound 10000
# service libvirtd status
libvirtd dead but pid file exists
Note, it's okay if I change them together on the first time then do separated change for inbound or outbound:
# virsh domiftune foo vnet0 --inbound 10000 --outbound 20000
# virsh domiftune foo vnet0
inbound.average: 10000
inbound.peak : 0
inbound.burst : 0
outbound.average: 20000
outbound.peak : 0
outbound.burst : 0
# virsh domiftune foo vnet0 --inbound 30000
# virsh domiftune foo vnet0
inbound.average: 30000
inbound.peak : 0
inbound.burst : 0
outbound.average: 20000
outbound.peak : 0
outbound.burst : 0
Actual results:
# service libvirtd status
libvirtd dead but pid file exists
Expected results:
can separately change inbound or outbound for interface device.
Additional info:
it should be the same issue with bug 771562.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2012-0748.html