virbr0-nic
I'd like to raise a question about this ugly hack.
The only reason why we need to create this is to assign mac address to the bridge. Right? You can create an operational bridge in UNKNOWN state with randomly assigned address using this.
# ip link add virbr0 type bridge
# ip link set virbr0 up
# ip link show virbr0
virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 36:28:ee:d1:48:9b brd ff:ff:ff:ff:ff:ff
assign it IP address and use it. But one can't bring it up if a MAC address is assigned to it
# ip link set virbr0 address 22:33:44:55:66:77
# ip link set virbr0 up
# ip link show virbr0
virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 22:33:44:55:66:77 brd ff:ff:ff:ff:ff:ff
And the only way to overcome this is to add this dummy virbr0-nic
device.
Hence the question: does anyone consider this hack ugly? Have anyone contacted kernel developers to fix this unnecessary limitation in the driver and let us assign bridge addresses directly to the bridge and use it without any additional virbr0-nic
hackery that spams our configs?