proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-07-16 09:40:57 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

qm mappings: stylistic fixes

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2023-06-19 08:41:02 +02:00
parent e2a867b28e
commit d772991e62
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
qm.adoc
View File

@ -1538,11 +1538,11 @@ Creating such a mapping can be done with the {pve} web GUI under `Datacenter`
in the relevant tab in the `Resource Mappings` category, or on the cli with in the relevant tab in the `Resource Mappings` category, or on the cli with
---- ----
# pvesh create /cluster/mapping/TYPE OPTIONS # pvesh create /cluster/mapping/<type> <options>
---- ----
Where `TYPE` is the hardware type (currently either `pci` or `usb`) and Where `<type>` is the hardware type (currently either `pci` or `usb`) and
`OPTIONS` are the device mappings and other configuration parameters. `<options>` are the device mappings and other configuration parameters.
Note that the options must include a map property with all identifying Note that the options must include a map property with all identifying
properties of that hardware, so that it's possible to verify the hardware did properties of that hardware, so that it's possible to verify the hardware did
@ -1577,26 +1577,26 @@ which exact virtual function is passed through.
You can assign such a device to a guest either with the GUI or with You can assign such a device to a guest either with the GUI or with
---- ----
# qm set ID -hostpci0 NAME # qm set ID -hostpci0 <name>
---- ----
for PCI devices, or for PCI devices, or
---- ----
# qm set ID -usb0 NAME # qm set <vmid> -usb0 <name>
---- ----
for USB devices. for USB devices.
Where `ID` is the guests id and `NAME` is the chosen name for the created Where `<vmid>` is the guests id and `<name>` is the chosen name for the created
mapping. All usual options for passing through the devices are allowed, such as mapping. All usual options for passing through the devices are allowed, such as
`mdev`. `mdev`.
To create mappings `Mapping.Modify` on `/mapping/TYPE/NAME` is necessary To create mappings `Mapping.Modify` on `/mapping/<type>/<name>` is necessary
(where `TYPE` is the device type and `NAME` is the name of the mapping). (where `<type>` is the device type and `<name>` is the name of the mapping).
To use these mappings, `Mapping.Use` on `/mapping/TYPE/NAME` is necessary (in To use these mappings, `Mapping.Use` on `/mapping/<type>/<name>` is necessary
addition to the normal guest privileges to edit the configuration). (in addition to the normal guest privileges to edit the configuration).
Managing Virtual Machines with `qm` Managing Virtual Machines with `qm`
------------------------------------ ------------------------------------