Il 2021-03-11 16:05 Laine Stump ha scritto:
That's correct. Support was added to the Linux host-bridge device a
few years ago for per-port VLAN tagging/filtering, but there hasn't
been anyone sufficiently compelled (by their own needs or by their
altruistic instincts) to support that. It likely w
On Thu, Mar 11, 2021 at 3:24 PM Peter Krempa wrote:
>
> On Thu, Mar 11, 2021 at 10:51:13 +0200, Liran Rotenberg wrote:
> > We recently had this bug[1]. The thought that came from it is the handling
> > of error code after running virDomainSnapshotCreateXML, we encountered
> > VIR_ERR_OPERATION_ABO
On 3/11/21 5:53 AM, Gionatan Danti wrote:
Dear list,
I am a question about the best use of bridge, vlan trunk and libvirt.
When dealing with virtual machies bound to specific vlan, I generally
use a straightforward approach:
eth -> bridge -> vm (for untagged traffic)
eth -> eth.10 -> bridge ->
On Thu, Mar 11, 2021 at 10:51:13 +0200, Liran Rotenberg wrote:
> We recently had this bug[1]. The thought that came from it is the handling
> of error code after running virDomainSnapshotCreateXML, we encountered
> VIR_ERR_OPERATION_ABORTED(78).
VIR_ERR_OPERATION_ABORTED is an error code which is
Dear list,
I am a question about the best use of bridge, vlan trunk and libvirt.
When dealing with virtual machies bound to specific vlan, I generally
use a straightforward approach:
eth -> bridge -> vm (for untagged traffic)
eth -> eth.10 -> bridge -> vm
eth -> eth.nn -> bridge -> vm
Now I am
We recently had this bug[1]. The thought that came from it is the handling
of error code after running virDomainSnapshotCreateXML, we encountered
VIR_ERR_OPERATION_ABORTED(78).
Apparently, the new volume is in use. Are there cases where this will
happen and the new volume won't appear in the volume
