docs: Remove one example from pci-addresses.rst

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@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>

diff --git a/docs/pci-addresses.rst b/docs/pci-addresses.rst
index 86a41df6cec9c7778e438bcf78b438acaa4e0eb7..1d2dc8e5fc25ebc390dd209bf2b12b089dd11f7d 100644 (file)
--- 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
 =================