search for: virio_net

...rstanding that right? The problem with the team/bond%d approach is that it creates a new netdevice and so it would require guest configuration changes. > IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > link is quite neat. I agree. For non-"backup" virio_net devices would it be okay for us to just return -EOPNOTSUPP? I assume it would be and that way the legacy behavior could be maintained although the function still exists. >> - When the 'active' netdev is unplugged OR not present on a destination >> system after live migration,...

...rstanding that right? The problem with the team/bond%d approach is that it creates a new netdevice and so it would require guest configuration changes. > IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > link is quite neat. I agree. For non-"backup" virio_net devices would it be okay for us to just return -EOPNOTSUPP? I assume it would be and that way the legacy behavior could be maintained although the function still exists. >> - When the 'active' netdev is unplugged OR not present on a destination >> system after live migration,...

...ond%d approach is that it creates a new >> netdevice and so it would require guest configuration changes. >> >>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>> link is quite neat. >> >> I agree. For non-"backup" virio_net devices would it be okay for us to >> just return -EOPNOTSUPP? I assume it would be and that way the legacy >> behavior could be maintained although the function still exists. >> >>>> - When the 'active' netdev is unplugged OR not present on a destination >&...

...ond%d approach is that it creates a new >> netdevice and so it would require guest configuration changes. >> >>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>> link is quite neat. >> >> I agree. For non-"backup" virio_net devices would it be okay for us to >> just return -EOPNOTSUPP? I assume it would be and that way the legacy >> behavior could be maintained although the function still exists. >> >>>> - When the 'active' netdev is unplugged OR not present on a destination >&...

...lem with the team/bond%d approach is that it creates a new > netdevice and so it would require guest configuration changes. > > > IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > > link is quite neat. > > I agree. For non-"backup" virio_net devices would it be okay for us to > just return -EOPNOTSUPP? I assume it would be and that way the legacy > behavior could be maintained although the function still exists. That's my understanding too.

...a new > >> netdevice and so it would require guest configuration changes. > >> > >>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio > >>> link is quite neat. > >> > >> I agree. For non-"backup" virio_net devices would it be okay for us to > >> just return -EOPNOTSUPP? I assume it would be and that way the legacy > >> behavior could be maintained although the function still exists. > >> > >>>> - When the 'active' netdev is unplugged OR not present...

...problem with the team/bond%d approach is that it creates a new > netdevice and so it would require guest configuration changes. > >> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >> link is quite neat. > > I agree. For non-"backup" virio_net devices would it be okay for us to > just return -EOPNOTSUPP? I assume it would be and that way the legacy > behavior could be maintained although the function still exists. > >>> - When the 'active' netdev is unplugged OR not present on a destination >>> system...

...es a new >>>> netdevice and so it would require guest configuration changes. >>>> >>>>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>>>> link is quite neat. >>>> I agree. For non-"backup" virio_net devices would it be okay for us to >>>> just return -EOPNOTSUPP? I assume it would be and that way the legacy >>>> behavior could be maintained although the function still exists. >>>> >>>>>> - When the 'active' netdev is unplugged OR no...

...es a new >>>> netdevice and so it would require guest configuration changes. >>>> >>>>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>>>> link is quite neat. >>>> I agree. For non-"backup" virio_net devices would it be okay for us to >>>> just return -EOPNOTSUPP? I assume it would be and that way the legacy >>>> behavior could be maintained although the function still exists. >>>> >>>>>> - When the 'active' netdev is unplugged OR no...

...t creates a new >>> netdevice and so it would require guest configuration changes. >>> >>>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>>> link is quite neat. >>> >>> I agree. For non-"backup" virio_net devices would it be okay for us to >>> just return -EOPNOTSUPP? I assume it would be and that way the legacy >>> behavior could be maintained although the function still exists. >>> >>>>> - When the 'active' netdev is unplugged OR not present on a d...

...nd so it would require guest configuration changes. >>>>> >>>>>> IMHO phys_port_name == "backup" if BACKUP bit is set on slave virtio >>>>>> link is quite neat. >>>>> >>>>> I agree. For non-"backup" virio_net devices would it be okay for us to >>>>> just return -EOPNOTSUPP? I assume it would be and that way the legacy >>>>> behavior could be maintained although the function still exists. >>>>> >>>>>>> - When the 'active' netdev is...

Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be used by hypervisor to indicate that virtio_net interface should act as a backup for another device with the same MAC address. Ppatch 2 is in response to the community request for a 3 netdev solution. However, it creates some issues we'll get into in a moment. It extends virtio_net to use alternate datapath when available

Patch 1 introduces a new feature bit VIRTIO_NET_F_BACKUP that can be used by hypervisor to indicate that virtio_net interface should act as a backup for another device with the same MAC address. Ppatch 2 is in response to the community request for a 3 netdev solution. However, it creates some issues we'll get into in a moment. It extends virtio_net to use alternate datapath when available