Displaying 5 results from an estimated 5 matches for "elementsconnect".
2016 Jul 24
2
Network without forward mode
Hey!
Another question. The documentation about networks say:
╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├─────
│Inclusion of the forward element indicates that the virtual network is
│to be connected to the physical LAN.Since 0.3.0. The mode attribute
│determines the method of forwarding. If there is no forward element, the
│network will be isolated from any other network (unless a guest
│connected t...
2016 Jul 25
2
Re: Network without forward mode
❦ 25 juillet 2016 06:06 CEST, Martin Kletzander <mkletzan@redhat.com> :
>>╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├─────
>>│Inclusion of the forward element indicates that the virtual network is
>>│to be connected to the physical LAN.Since 0.3.0. The mode attribute
>>│determines the method of forwarding. If there is no forward element, the
>>│network will be isolated from any other netw...
2016 Jul 25
0
Re: Network without forward mode
On Sun, Jul 24, 2016 at 11:18:19PM +0200, Vincent Bernat wrote:
>Hey!
>
>Another question. The documentation about networks say:
>
>╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├─────
>│Inclusion of the forward element indicates that the virtual network is
>│to be connected to the physical LAN.Since 0.3.0. The mode attribute
>│determines the method of forwarding. If there is no forward element, the
>│network will be isolated from any other network (unless a gu...
2016 Jul 25
0
Re: Network without forward mode
On Mon, Jul 25, 2016 at 06:58:53AM +0200, Vincent Bernat wrote:
> ❦ 25 juillet 2016 06:06 CEST, Martin Kletzander <mkletzan@redhat.com> :
>
>>>╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├─────
>>>│Inclusion of the forward element indicates that the virtual network is
>>>│to be connected to the physical LAN.Since 0.3.0. The mode attribute
>>>│determines the method of forwarding. If there is no forward element, the
>>>│network will be isolated fro...
2019 May 10
1
Re: Cannot get interface MTU - qemu quest fails to start off OpenVswitch
On 10/05/2019 14:44, Michal Privoznik wrote:
> On 5/10/19 3:26 PM, lejeczek wrote:
>> hi guys
>>
>> I have a qemu guest and openvswitch bridge and the guest fails to start:
>>
>> $ virsh start work8
>> error: Failed to start domain work8-vm-win2016
>> error: Cannot get interface MTU on 'ovsbr0': No such device
>
> Well, this means that