Hi,

I've created two private bridge networks (virbr1 & virbr2) while on 7.0.1, using the information in the following thread:

but upon upgrading to 7.1.2, they disappeared for the selection for new VM (and from the VM settings as a default network source (I can still see them available and active using virsh net-list).

Is it a known bug I'm missing or something?

Thanks in advance

7.1.3 should be out soon with some fixes for that, you can also try this for now:

https://forums.unraid.net/bug-reports/stable-releases/docker-container-dont-start-br0-not-found-after-update-r3791/#findComment-33799

Unfortunately, didn't help.

My missing network was set using virsh - does Docker & KVM use the same network?

10 hours ago, gshlomi said:

does Docker & KVM use the same network?

I don't think, misread the original post.

23 minutes ago, JorgeB said:

I don't think, misread the original post.

So 7.1.3 not a solution for me? :-(

Not sure, @SimonF do you know what the issue is here?

On 6/3/2025 at 10:44 PM, gshlomi said:

Unfortunately, didn't help.

My missing network was set using virsh - does Docker & KVM use the same network?

Can you provide an example of you network xml?

2 hours ago, SimonF said:

Can you provide an example of you network xml?

This is one:

<network ipv6='no'>

<name>lan-network</name>

<bridge name="virbr1" stp="on" delay="0"/>

</network>

This is two:

<network ipv6='no'>

<name>dmz-network</name>

<bridge name="virbr2" stp="on" delay="0"/>

</network>

btw - upgrade to 7.1.3 doesn't resolve this :-(

Edited June 5, 20251 yr by gshlomi

2 hours ago, gshlomi said:

This is one:

<network ipv6='no'>

<name>lan-network</name>

<bridge name="virbr1" stp="on" delay="0"/>

</network>

This is two:

<network ipv6='no'>

<name>dmz-network</name>

<bridge name="virbr2" stp="on" delay="0"/>

</network>

btw - upgrade to 7.1.3 doesn't resolve this :-(

It is a bug and I have a fix so will create a pr and see if it can be back ported.

29 minutes ago, SimonF said:

It is a bug and I have a fix so will create a pr and see if it can be back ported.

Anything I can do in the meantime other than downgrading?

This should be fixed in 7.1.4, please retest.

Thanks @SimonF and @JorgeB , seems that 7.1.4 indeed fixed the issue.

Only thing I've noticed which is a bit strange (don't remember how it was on 7.0.1) - when creating a new VM and trying to choose the custom network, I've too many options (If I recall correctly, on 7.0 brunch had only the bridges to choose from):

Anyway, thanks for the fix

54 minutes ago, gshlomi said:

Thanks @SimonF and @JorgeB , seems that 7.1.4 indeed fixed the issue.

Only thing I've noticed which is a bit strange (don't remember how it was on 7.0.1) - when creating a new VM and trying to choose the custom network, I've too many options (If I recall correctly, on 7.0 brunch had only the bridges to choose from):

Anyway, thanks for the fix

libvirt network names where added for 7.1 but there was a bug which was also fixed. They are the same as virbrx but will the real names.

56 minutes ago, SimonF said:

libvirt network names where added for 7.1 but there was a bug which was also fixed. They are the same as virbrx but will the real names.

So does it matter which one I choose when creating a new VM?

Virbr1 is LAN-network, for instance

3 hours ago, gshlomi said:

So does it matter which one I choose when creating a new VM?

Virbr1 is LAN-network, for instance

Choice is yours. Ether will be ok