[libvirt PATCH 4/4] docs: Remove one example from pci-addresses.rst

[Cornelia Huck]

On Wed, 15 Apr 2020 19:31:36 +0200
Andrea Bolognani <abologna at redhat.com> wrote:

> The idea behind this document is to show, with actual examples,
> that users should not expect PCI addresses in the domain XML and
> in the guest OS to match.
> 
> The first zPCI example already serves this purpose perfectly, so
> in the interest of keeping the page as brief and easy to digest
> as possible the second one is removed.
> 
> Signed-off-by: Andrea Bolognani <abologna at redhat.com>
> ---
>  docs/pci-addresses.rst | 19 -------------------
>  1 file changed, 19 deletions(-)
> 
> diff --git a/docs/pci-addresses.rst b/docs/pci-addresses.rst
> index 86a41df6ce..1d2dc8e5fc 100644
> --- a/docs/pci-addresses.rst
> +++ b/docs/pci-addresses.rst
> @@ -204,25 +204,6 @@ will result in the exactly same view in the guest, as the addresses there
>  are generated from the information provided via the ``zpci`` element (in
>  fact, from the ``uid``).
>  
> -Therefore, replacing the virtio-net device definition with the following XML
> -snippet
> -
> -::
> -
> -  <interface type='bridge'>
> -    <source bridge='virbr0'/>
> -    <model type='virtio'/>
> -    <address type='pci' domain='0x0000' bus='0x01' slot='0x07' function='0x3'>
> -      <zpci uid='0x0007' fid='0x00000003'/>
> -    </address>
> -  </interface>
> -
> -will yield the following result in a Linux guest:
> -
> -::
> -
> -  0007:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device
> -
>  
>  Device assignment
>  =================

Hm, should that rather go somewhere else? What I wanted to show is "you
can have the same PCI address in the XML and still get a different PCI
address in the guest, if you change the zpci values", as that might be
another source of confusion.