shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 17:34:18 +03:00
Code Releases Activity

virsh: Remove any reference of KVM device assignment

Browse Source 
The KVM device assignment was removed in v5.7.0-rc1~103 but virsh
and its manpage still mention it. Don't do that.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
Michal Privoznik 2022-04-05 10:38:47 +02:00
parent e53c02ea20
commit 5e9d8f094c
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/manpages/virsh.rst
View File

@ -5198,10 +5198,9 @@ guests via <hostdev> passthrough. This is reversed with
``nodedev-reattach``, and is done automatically for managed devices.
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 *--driver*
parameter can be used to specify the desired backend driver.
dummy devices. For example, QEMU's "vfio" backend driver expects the
device to be bound to vfio-pci. The *--driver* parameter can be used
to specify the desired backend driver.
nodedev-dumpxml

2
tools/virsh-nodedev.c
View File

@ -615,7 +615,7 @@ static const vshCmdOptDef opts_node_device_detach[] = {
{.name = "driver",
.type = VSH_OT_STRING,
.completer = virshNodeDevicePCIBackendCompleter,
.help = N_("pci device assignment backend driver (e.g. 'vfio' or 'kvm')")
.help = N_("pci device assignment backend driver (e.g. 'vfio' or 'xen')")
},
{.name = NULL}
};