Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1342626

Summary:	[Docs][VMM]Explain viodiskcache writeback/writethrough options and the supportability on file and block-based domains (currently works on file based only)
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gordon Watson <gwatson>
Component:	Documentation	Assignee:	rhev-docs <rhev-docs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	rhev-docs <rhev-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.5	CC:	acanan, gwatson, lbopf, lsurette, mkalinin, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone:	ovirt-4.1.11	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-29 05:22:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Docs	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gordon Watson 2016-06-03 17:32:08 UTC

Description of problem:

Via 'Custom Properties', a VM can be edited and the 'viodiskcache' property set. If this is set to either 'writeback' or 'writethrough', this will only apply to file-based storage volumes.

For block-based storage, if 'virtio' is used, the VM will fail to start, reporting "unsupported configuration: native I/O needs either no disk cache or directsync cache mode, QEMU will fallback to aio=threads".

If 'virtio-scsi' is used, the VM will start but the block-based disk will resort to 'cache=none' and 'aio=native'. Any file-based volumes will in this case be set to 'cache=writeback' and 'aio=threads'.

The reason for this is that 'aio=threads' needs to be set for block-based storage and there is no way to set this in the RHEV Admin Portal.



Version-Release number of selected component (if applicable):

RHEV 3.x


How reproducible:

Every time.



Steps to Reproduce:
1. Create VM with a block-based 'virtio' or 'virtio-scsi' disk.
2. Set 'viodiskcache' to 'writeback'.
3. Start VM.


Actual results:


Expected results:


Additional info:

Comment 11 Yaniv Lavi 2016-12-14 14:02:45 UTC

Can you please open a bug on RHEL to block this one to support caching on io native?

Comment 14 Yaniv Kaul 2017-10-20 16:22:15 UTC

This is targeted to 4.1.6 which was already released?

Comment 26 Lucy Bopf 2018-06-14 00:40:25 UTC

PM has confirmed that the content of the KCS referenced from the docs is accurate.

The KCS is published, and is referenced in the following places:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/virtual_machine_management_guide/#Virtual_Machine_Custom_Properties_settings_explained

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/virtual_machine_management_guide/#Virtual_Machine_Run_Once_settings_explained

I can't see any other pending updates, so if there are no further requirements for updating the documentation here, we will close this BZ. Gordon, can you take a look and confirm that this satisfies your original request?

Comment 27 Gordon Watson 2018-06-15 13:57:11 UTC

Lucy,

As long as the information in the KCS is valid, as has been confirmed, and as long as this is now referenced in the Docs, which it is, then you can close this bug.

Thanks, GFW.

Comment 28 Lucy Bopf 2018-06-29 05:22:44 UTC

Thanks for confirming!

Moving this one to CLOSED.