proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-05-03 15:21:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

qm: fix two grammar issues

Browse Source 
Fixed two small grammar errors in the qm chapter. Rephrased a
sentence before the fixed sentence so that it would be more legible.

Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
 [ T: resolve context merge conflict on current master ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Noel Ullreich 2022-12-02 12:52:00 +01:00 committed by Thomas Lamprecht
parent 067d9c3dba
commit 58e695ca6a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
qm.adoc
View File

@ -252,7 +252,7 @@ IO Thread
The option *IO Thread* can only be used when using a disk with the *VirtIO* The option *IO Thread* can only be used when using a disk with the *VirtIO*
controller, or with the *SCSI* controller, when the emulated controller type is controller, or with the *SCSI* controller, when the emulated controller type is
*VirtIO SCSI single*. With *IO Thread* enabled, QEMU creates one I/O thread per *VirtIO SCSI single*. With *IO Thread* enabled, QEMU creates one I/O thread per
storage controller, rather than handling all I/O in the main event loop or vCPU storage controller rather than handling all I/O in the main event loop or vCPU
threads. One benefit is better work distribution and utilization of the threads. One benefit is better work distribution and utilization of the
underlying storage. Another benefit is reduced latency (hangs) in the guest for underlying storage. Another benefit is reduced latency (hangs) in the guest for
very I/O-intensive host workloads, since neither the main thread nor a vCPU very I/O-intensive host workloads, since neither the main thread nor a vCPU
@ -765,7 +765,7 @@ open-source, x86 BIOS implementation. SeaBIOS is a good choice for most
standard setups. standard setups.
Some operating systems (such as Windows 11) may require use of an UEFI Some operating systems (such as Windows 11) may require use of an UEFI
compatible implementation instead. In such cases, you must rather use *OVMF*, compatible implementation. In such cases, you must use *OVMF* instead,
which is an open-source UEFI implementation. footnote:[See the OVMF Project https://github.com/tianocore/tianocore.github.io/wiki/OVMF] which is an open-source UEFI implementation. footnote:[See the OVMF Project https://github.com/tianocore/tianocore.github.io/wiki/OVMF]
There are other scenarios in which the SeaBIOS may not be the ideal firmware to There are other scenarios in which the SeaBIOS may not be the ideal firmware to