| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Added a ``disk_geometry`` configuration option to volume drivers that |
| 5 |
advertises each volume's ``logical_block_size`` and ``physical_block_size`` |
| 6 |
to the guest. By default the option is unset which means that the block |
| 7 |
sizes are not set hinted to the guest. The recommended value for HDDs is |
| 8 |
``512e`` (logical 512, physical 4096) which hints that 4k-aligned I/O is |
| 9 |
optimal while remaining compatible with older operating systems. This has |
| 10 |
the most visible impact for Windows guests that would otherwise submit |
| 11 |
512-byte I/O, while Linux typically aligns to 4k already. On back ends such |
| 12 |
as Ceph, aligned 4k requests prevent extra read-modify-update cycles and can |
| 13 |
noticeably improve HDD-backed pool performance. Note that guests need a |
| 14 |
VirtIO driver that includes the fix from |
| 15 |
https://bugzilla.redhat.com/show_bug.cgi?id=1428641 to use this feature |
| 16 |
(2019 or newer). upgrade: |
| 17 |
- | |
| 18 |
A new volume driver configuration option ``disk_geometry`` has been |
| 19 |
introduced, which controls the ``logical_block_size`` and |
| 20 |
``physical_block_size`` advertised to the guest. By default this option is |
| 21 |
unset which is equivalent to the behavior of previous releases. However, the |
| 22 |
recommended value for HDDs ``512e`` (logical 512, physical 4096) which hints |
| 23 |
that 4k-aligned I/O is optimal while remaining compatible with older |
| 24 |
operating systems. The current configuration value is used immediately |
| 25 |
whenever a volume is attached, however existing libvirt VMs won't be updated |
| 26 |
unless their configuration file is re-generated such as by |
| 27 |
detaching/attaching the volume, cold migrating the VM to another host or |
| 28 |
both live migrating (to update the configuration) and then later rebooting |
| 29 |
the guest (so that the guest re-reads the information from the hardware). |
| 30 |
Environments with Windows guests wanting to take advantage of this |
| 31 |
optimization may want to consider intentionally performing such operations |
| 32 |
to update the configuration of those guests and also ensure the guest VirtIO |
| 33 |
drivers are updated to a version from 2019 or later. |