Bug 1047401 - When using a NetworkManager created bridge libvirt domains with autostart fail to start at boot time
Summary: When using a NetworkManager created bridge libvirt domains with autostart fai...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-31 00:05 UTC by Shawn Starr
Modified: 2014-01-27 04:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-27 04:50:45 UTC
Type: Bug


Attachments (Terms of Use)

Description Shawn Starr 2013-12-31 00:05:49 UTC
Description of problem:

Using the following NetworkManager configuration:

File: ifcfg-bridge0

--- CUT ---
DEVICE=br0
STP=no
TYPE=Bridge
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=bridge0
UUID=69e1abdf-731a-41e8-9077-dba5895c475d
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_PRIVACY=no
-- CUT ---

file: ifcfg-New_802-3-ethernet_connection (MAC address replaced with fake vlaues)

-- CUT --
TYPE=Ethernet
NAME=bridge0-enp0s25
UUID=276128df-58b0-4dd4-84cc-c2c71aeec1ef
ONBOOT=yes
BRIDGE=69e1abdf-731a-41e8-9077-dba5895c475d
HWADDR=AA:BB:CC:DD:EE:FF
USERS=spstarr
--- CUT --


Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-22.git20131003.fc20.x86_64
libvirt-daemon-1.1.3.2-1.fc20.x86_64

How reproducible: 100%


Steps to Reproduce:
1. Create NetworkManager bridge
2. Set VM guests to use this bridge
3. Set guest VM/domain to autostart
4. Reboot machine
5. guest VM not booted.
 
Actual results:
Fails to boot guest

Expected results:
Guest is booted on start of host machine

Comment 1 Shawn Starr 2013-12-31 00:10:28 UTC
Guest VM XML config for networking:

    <interface type='bridge'>
      <mac address='52:54:00:f0:67:11'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

Note: there is no virtual networks configure in virt-manager I am using bridge networking only

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.18.2.4  netmask 255.255.255.0  broadcast 172.18.2.255
        inet6 fe80::4835:10ff:fe03:4c81  prefixlen 64  scopeid 0x20<link>
        ether  AA:BB:CC:DD:EE:FF   txqueuelen 0  (Ethernet)
        RX packets 10108  bytes 7422082 (7.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9356  bytes 1639487 (1.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:68ff:fe0c:96e3  prefixlen 64  scopeid 0x20<link>
        ether AA:BB:CC:DD:EE:FF  txqueuelen 1000  (Ethernet)
        RX packets 12318  bytes 7989297 (7.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9497  bytes 1700180 (1.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xfc200000-fc220000

Comment 2 Shawn Starr 2013-12-31 00:12:09 UTC
I confirm this is some sort of ordering problem because if I restart libvirtd after booting the domains marked autostart will then boot up normally.

Comment 3 Shawn Starr 2014-01-27 04:50:45 UTC
Closing, if NetworkManager is confused, libvirtd will be, deleting bridge/creating a new one makes libvirtd autostart VMs.. but another issue has been uncovered.. another bug filed..


Note You need to log in before you can comment on or make changes to this bug.