On 9/17/21 19:04, Jim Fehlig wrote:
> On 9/17/21 10:46, Laine Stump wrote:
>> On 9/17/21 7:11 AM, Michael Ströder wrote:
>>> When restarting libvirtd itself I see the following syslog warning
>>> message:
>>>
>>> libvirtd: 5733: warning : netcfIfaceRegister:1287 : Failed to initialize
>>> libnetcon
sh net-start vnet1
>> error: Failed to start network vnet1
>> error: internal error: Network is already in use by interface virbr0
>
> Someone else (probably libvirt itself, for libvirt's "default" network)
> has created a bridge device called virbr0, and has set
the network does not work either:
# virsh net-start vnet1
error: Failed to start network vnet1
error: internal error: Network is already in use by interface virbr0
In syslog I find:
libvirtd: 6325: error : networkCheckRouteCollision:296 : internal error:
Network is already in use by interface vi
e-dir-suse-p1'
error: Requested operation is not valid: network 'vnet1' is not active
Manually starting the network does not work either:
# virsh net-start vnet1
error: Failed to start network vnet1
error: internal error: Network is already in use by interface virbr0
In syslog I fin
ir-suse-p1
> error: Failed to start domain 'ae-dir-suse-p1'
> error: Requested operation is not valid: network 'vnet1' is not active
>
> Manually starting the network does not work either:
>
> # virsh net-start vnet1
> error: Failed to start network vnet1
&g
on is not valid: network 'vnet1' is not active
Manually starting the network does not work either:
# virsh net-start vnet1
error: Failed to start network vnet1
error: internal error: Network is already in use by interface virbr0
In syslog I find:
libvirtd: 6325: error : networkCheckRout
