[libvirt] [PATCH 06/12] virInterface: Expose link state & speed

Daniel P. Berrange berrange at redhat.com
Fri May 30 08:56:39 UTC 2014


On Thu, May 29, 2014 at 10:32:40AM +0200, Michal Privoznik wrote:
> Currently it is not possible to determine the speed of an interface
> and whether a link is actually detected from the API. Orchestrating
> platforms want to be able to determine when the link has failed and
> where multiple speeds may be available which one the interface is
> actually connected at. This commit introduces an extension to our
> interface XML (without implementation to interface driver backends):
> 
>   <interface type='ethernet' name='eth0'>
>     <start mode='none'/>
>     <mac address='aa:bb:cc:dd:ee:ff'/>
>     <link speed='1000' state='up'/>
>     <mtu size='1492'/>
>     ...
>   </interface>
> 
> Where @speed is negotiated link speed in Mbits per second, and state
> is the current NIC state (can be one of the following:  "unknown",
> "notpresent", "down", "lowerlayerdown","testing", "dormant", "up").

This is fine for the the <interface> objects, but it is limited
in usefulness for SRIOV use cases. The <interface> objects only
exist for interfaces which are configured for the host. With
SRIOV passthrough some of the interfaces we're interested in
are not going to be configured - they're just bare devices
waiting to be given to a guest.

To deal with that, we need report all this info on the node device
APIs which let us list all NICs, regardless of whether they are
configured on the host or not.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|




More information about the libvir-list mailing list