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.
I'm not sure why this BZ was cloned from 6.5 to 7.0, since everything fixed in 6.5 will also be fixed in 7.0, but the problem has been fixed as of libvirt-1.0.5 (plus one patch - the 2nd patch listed below) with the following two commits (and several other that precede them):
commit 446dd66b7c7641974d25423c4cb5c48e481a84e4
Author: Peter Krempa <pkrempa>
Date: Tue Apr 16 18:35:59 2013 +0200
network: bridge_driver: don't lose transient networks on daemon restart
Until now tranisent networks weren't really useful as libvirtd wasn't
able to remember them across restarts. This patch adds support for
loading status files of transient networks (that already were generated)
so that the status isn't lost.
This patch chops up virNetworkObjUpdateParseFile and turns it into
virNetworkLoadState and a few friends that will help us to load status
XMLs and refactors the functions that are loading the configs to use
them.
commit 2ffd87d8204c209b81610b56ee5161ae71b58b8c
Author: Laine Stump <laine>
Date: Thu May 2 13:59:52 2013 -0400
network: fix network driver startup for qemu:///session
This was a regression cause the the prior patch.
This should resolve https://bugzilla.redhat.com/show_bug.cgi?id=958907
pkgs:
libvirt-1.0.5-2.el7.x86_64
qemu-kvm-1.4.0-4.el7.x86_64
kernel-3.9.0-0.55.el7.x86_64
steps:
1. create a network with xml
# cat net.xml
<network>
<name>definebr1</name>
<uuid>fb09e249-7cce-252e-2417-c47d6d60b3d6</uuid>
<forward/>
<bridge name='definebr1' stp='on' forwardDelay='0' />
<ip address='192.168.111.1' netmask='255.255.255.0'>
<dhcp>
<range start='192.168.111.2' end='192.168.111.254' />
</dhcp>
</ip>
</network>
# virsh net-create net.xml
Network definebr1 created from net.xml
# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default active yes yes
definebr1 active no no
# brctl show
bridge name bridge id STP enabled interfaces
definebr1 8000.52540088edf3 yes definebr1-nic
virbr0 8000.029a318189a6 yes veth1
veth10
veth11
veth2
veth3
veth4
veth5
veth6
veth9
vnet0
2. restart libvirtd
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
3. recheck
# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default active yes yes
definebr1 active no no
# brctl show
bridge name bridge id STP enabled interfaces
definebr1 8000.52540088edf3 yes definebr1-nic
virbr0 8000.ce2f60dc3110 yes veth1
vnet0
so the created network will not disappear after restart, this is as expected as verified in bug:
https://bugzilla.redhat.com/show_bug.cgi?id=949926
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
I'm not sure why this BZ was cloned from 6.5 to 7.0, since everything fixed in 6.5 will also be fixed in 7.0, but the problem has been fixed as of libvirt-1.0.5 (plus one patch - the 2nd patch listed below) with the following two commits (and several other that precede them): commit 446dd66b7c7641974d25423c4cb5c48e481a84e4 Author: Peter Krempa <pkrempa> Date: Tue Apr 16 18:35:59 2013 +0200 network: bridge_driver: don't lose transient networks on daemon restart Until now tranisent networks weren't really useful as libvirtd wasn't able to remember them across restarts. This patch adds support for loading status files of transient networks (that already were generated) so that the status isn't lost. This patch chops up virNetworkObjUpdateParseFile and turns it into virNetworkLoadState and a few friends that will help us to load status XMLs and refactors the functions that are loading the configs to use them. commit 2ffd87d8204c209b81610b56ee5161ae71b58b8c Author: Laine Stump <laine> Date: Thu May 2 13:59:52 2013 -0400 network: fix network driver startup for qemu:///session This was a regression cause the the prior patch. This should resolve https://bugzilla.redhat.com/show_bug.cgi?id=958907