The current check uses an alignment of 512 bytes and will fail when the
underlying device has sectors of size 4096 bytes, as is common e.g. for
NVMe disks. So use an alignment of 4096 bytes, which is a multiple of
512 bytes and thus will cover both cases.
Conflicts: nova/privsep/utils.py
- supports_direct_io() is still in nova/virt/libvirt/driver.py for this branch
Change-Id: I5151ae01e90506747860d9780547b0d4ce91d8bc
Closes-Bug: 1801702
Co-Authored-By: Alexandre Arents <email address hidden>
(cherry picked from commit 14d98ef1b48ca7b2ea468a8f1ec967b954955a63)
(cherry picked from commit ba844f2a7c1d4602017bb0fc600a30b150c28dbc)
Reviewed: https:/ /review. openstack. org/631843 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=c77c3eb61ca 7a0da64eed62dea 084ee3df1d0722
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit c77c3eb61ca7a0d a64eed62dea084e e3df1d0722
Author: Jens Harbott <email address hidden>
Date: Thu Nov 8 15:06:26 2018 +0000
Make supports_direct_io work on 4096b sector size
The current check uses an alignment of 512 bytes and will fail when the
underlying device has sectors of size 4096 bytes, as is common e.g. for
NVMe disks. So use an alignment of 4096 bytes, which is a multiple of
512 bytes and thus will cover both cases.
Conflicts:
nova/ privsep/ utils.py direct_ io() is still in
nova/virt/ libvirt/ driver. py for this branch
- supports_
Change-Id: I5151ae01e90506 747860d9780547b 0d4ce91d8bc 2ea468a8f1ec967 b954955a63) 2017bb0fc600a30 b150c28dbc)
Closes-Bug: 1801702
Co-Authored-By: Alexandre Arents <email address hidden>
(cherry picked from commit 14d98ef1b48ca7b
(cherry picked from commit ba844f2a7c1d460