Bug 713180

>Description of Problem:
When we start virt-manager in the state that all the guest OS's of the bridge (br0)
constitution stopped, libvirtd reports a large quantity of error message in a syslog.

libvirtd reports the following error message to /var/log/messages every second
when virt-manager shuts down all guest OSes configuring with a bridge "br0".

-------------------------
May 24 10:30:09 rh61ga libvirtd: 10:30:09.707: 1918: error : virInterfaceDefParseXML:744 :
XML description for bridge interface misses the bridge element is not well formed or invalid
-------------------------

But, the above message looks improper and unnecessary because all guest OSes
have been shut down normally. We believe that this issue is due to a bug of
libvirt. Could you fix it so that it doesn't report the said messages then?


Red Hat Enterprise Linux Version Number: Red Hat Enterprise Linux 6.1
Architecture: x86_64
Kernel Version: kernel-2.6.32-131.0.15.el6.x86_64
Related Package Version: virt-manager-0.8.6-4.el6.noarch


>How reproducible:
always.

>Step to Reproduce:
1. Configure a virtual bridge that a guest OS doesn't connect to another host
OS including a guest OS created by it.
# cat /etc/sysconfig/network-script/ifcfg-br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
2. Activate "ifcfg-br0" as follows.
2-1. Turn off "NetworkManager" by "chkconfig".
# chkconfig NetworkManager off
2-2. Turn on "network" by "chkconfig".
# chkconfig network on
2-3. Stop the NetworkManager service.
# service NetworkManager stop
2-4. Restart the network.
# service network restart
3. Create a guest OS as follows.
3-1. Click "Create a new virtual machine" button.
3-2. Creating a new virtual machine according to the wizard "Step<1-5> of 5"
3-2-1. [Step 1 of 5] Input virtual machine name.
3-2-2. [Step 2 of 5] Specify ISO images, OS type, and Version as follows.
Use ISO images: RHEL6.1-Server-x86_64-DVD1.iso
OS type: Linux
Version: Red Hat Enterprise Linux 6
3-2-3. [Step 3 of 5] Specify memory size and the number of CPUs as follows.
Memory: 1024
CPUs : 1
3-2-4. Creating a new virtual machine according to the wizard "Step 4 of 5"
3-2-4-1. [Step 4 of 5] Select a radio button "Select managed or other existing
storage".
3-2-4-2. [Step 4 of 5] Specify an image file available for a guest OS.
3-2-5. Creating a new virtual machine according to the wizard "Step 5 of 5"
3-2-5-1. [Step 5 of 5] Check "Customizes setting before installation(U)".
3-2-5-2. [Step 5 of 5] Click "Advanced options".
3-2-5-3. [Step 5 of 5] Specify each parameter as follows.
Select "Specify shared device name" from the pull-down menu.
Bridged name(B): br0
Virt type (V): Kvm
Architecture (A): x86_64
3-2-5-4. [Step 5 of 5] Click "Finish" button.
3-2-6. Specify each parameter as follows.
Click "Machine Settings".
Click "Enable A_CPI:"
Check "Enable A_PIC:"
4. Run the following step after installing the guest OS.
4-1. Monitor /var/log/messages in the terminal on the host machine.
# tail -F /var/log/messages
4-2. Stop the guest OS.
# virsh shutdown <domain-id>
4-3. Start virt-manager.
# virt-manager
4-4. Check that libvirtd reports the said error message to /var/log/messages.

>Actual Results:
libvirtd reports the said error message.

>Expected Results:
libvirtd doesn't report the said error message.

This Fedora BZ is related:
https://bugzilla.redhat.com/show_bug.cgi?id=698108