[libvirt] [PATCH] virsh: Mention --driver in man page for nodedev-detach

Peter Krempa pkrempa at redhat.com
Fri Jul 12 09:40:49 UTC 2013


Commit d923f6c8 introduced the --driver option but didn't document it in
the man page. The docs are borrowed from the public API documentation.
---
 tools/virsh.pod | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/tools/virsh.pod b/tools/virsh.pod
index 94fe897..51644d9 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -2113,7 +2113,7 @@ name or wwn pair in "wwnn,wwpn" format (only works for HBA). Note
 that this makes libvirt quit managing a host device, and may even make
 that device unusable by the rest of the physical host until a reboot.

-=item B<nodedev-detach> I<nodedev>
+=item B<nodedev-detach> I<nodedev> [I<--driver backend_driver>]

 Detach I<nodedev> from the host, so that it can safely be used by
 guests via <hostdev> passthrough.  This is reversed with
@@ -2121,6 +2121,12 @@ B<nodedev-reattach>, and is done automatically for managed devices.
 For compatibility purposes, this command can also be spelled
 B<nodedev-dettach>.

+Different backend drivers expect the device to be bound to different
+dummy devices. For example, QEMU's "kvm" backend driver (the default)
+expects the device to be bound to pci-stub, but its "vfio" backend
+driver expects the device to be bound to vfio-pci. The I<--driver>
+parameter can be used to specify the desired backend driver.
+
 =item B<nodedev-dumpxml> I<device>

 Dump a <device> XML representation for the given node device, including
-- 
1.8.3.2




More information about the libvir-list mailing list