+=head2 E<lt>drive_mappingsE<gt>
+
+For operating systems like Windows which use drive letters,
+virt-inspector is able to find out how drive letters map to
+filesystems.
+
+ <operatingsystems>
+ <operatingsystem>
+ ...
+ <drive_mappings>
+ <drive_mapping name="C">/dev/sda2</drive_mapping>
+ <drive_mapping name="E">/dev/sdb1</drive_mapping>
+ </drive_mappings>
+
+In the example above, drive C maps to the filesystem on the second
+partition on the first disk, and drive E maps to the filesystem on the
+first partition on the second disk.
+
+Note that this only covers permanent local filesystem mappings, not
+things like network shares. Furthermore NTFS volume mount points may
+not be listed here.
+
+=head2 E<lt>iconE<gt>
+
+Virt-inspector is sometimes able to extract an icon or logo for the
+guest. The icon is returned as base64-encoded PNG data. Note that
+the icon can be very large and high quality.
+
+ <operatingsystems>
+ <operatingsystem>
+ ...
+ <icon>
+ iVBORw0KGgoAAAANSUhEUgAAAGAAAABg[.......]
+ [... many lines of base64 data ...]
+ </icon>
+
+To display the icon, you have to extract it and convert the base64
+data back to a binary file. Use an XPath query or simply an editor to
+extract the data, then use the coreutils L<base64(1)> program to do
+the conversion back to a PNG file:
+
+ base64 -i -d < icon.data > icon.png
+
+=head2 INSPECTING INSTALL DISKS, LIVE CDs
+
+Virt-inspector can detect some operating system installers on
+install disks, live CDs, bootable USB keys and more.
+
+In this case the E<lt>formatE<gt> tag will contain C<installer>
+and other fields may be present to indicate a live CD, network
+installer, or one part of a multipart CD. For example:
+
+ <operatingsystems>
+ <operatingsystem>
+ <root>/dev/sda</root>
+ <name>linux</name>
+ <arch>i386</arch>
+ <distro>ubuntu</distro>
+ <product_name>Ubuntu 10.10 "Maverick Meerkat"</product_name>
+ <major_version>10</major_version>
+ <minor_version>10</minor_version>
+ <format>installer</format>
+ <live/>
+