On Wed, Jan 22, 2020 at 02:59:36PM +0200, Dan Kenigsberg wrote:
> On Tue, Jan 21, 2020 at 4:47 PM Daniel P. Berrangé
> wrote:
> >
> > On Tue, Jan 21, 2020 at 12:46:38PM +0200, Dan Kenigsberg wrote:
> > > On Mon, Jan 20, 2020 at 8:33 PM Daniel P. Berrangé
> > > wrote:
> > > >
> > > > On Sun,
On Tue, Jan 21, 2020 at 4:47 PM Daniel P. Berrangé wrote:
>
> On Tue, Jan 21, 2020 at 12:46:38PM +0200, Dan Kenigsberg wrote:
> > On Mon, Jan 20, 2020 at 8:33 PM Daniel P. Berrangé
> > wrote:
> > >
> > > On Sun, Jan 19, 2020 at 10:24:19PM -0500, Laine Stump wrote:
> > > > Current virtio-net
On Tue, Jan 21, 2020 at 12:46:38PM +0200, Dan Kenigsberg wrote:
> On Mon, Jan 20, 2020 at 8:33 PM Daniel P. Berrangé
> wrote:
> >
> > On Sun, Jan 19, 2020 at 10:24:19PM -0500, Laine Stump wrote:
> > > Current virtio-net drivers that support the failover feature match up
> > > the virtio backup
On Mon, Jan 20, 2020 at 8:33 PM Daniel P. Berrangé wrote:
>
> On Sun, Jan 19, 2020 at 10:24:19PM -0500, Laine Stump wrote:
> > Current virtio-net drivers that support the failover feature match up
> > the virtio backup device with its corresponding hostdev device by
> > looking for an interface
On Sun, Jan 19, 2020 at 10:24:19PM -0500, Laine Stump wrote:
> Current virtio-net drivers that support the failover feature match up
> the virtio backup device with its corresponding hostdev device by
> looking for an interface with a matching MAC address. Since libvirt
> will assign a different
Current virtio-net drivers that support the failover feature match up
the virtio backup device with its corresponding hostdev device by
looking for an interface with a matching MAC address. Since libvirt
will assign a different random MAC address to each interface that
isn't given an explicit MAC
