You are talking about QEMU or AQEMU?
In AQEMU on storage device settings caching policy not assigned by default.
Do you offer always send "writeback" option to QEMU that it used instead of the default?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What ever default is assigned to (witethrough?) it should be writeback (don't know who handles the default alias).
In case of adding a storage to an vm i always had to change the cache option.
I think it would be better if the default is an more useful one. Useful with the meaning of time consuming and data integrety.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By default, the cache=writeback mode is used. It will report data writes as completed as soon as
the data is present in the host page cache. This is safe as long as your guest OS makes sure to
correctly flush disk caches where needed. If your guest OS does not handle volatile disk write
caches correctly and your host crashes or loses power, then the guest may experience data
corruption.
Since cache=writeback is the default in the latest qemu, I think I can close this.
You are talking about QEMU or AQEMU?
In AQEMU on storage device settings caching policy not assigned by default.
Do you offer always send "writeback" option to QEMU that it used instead of the default?
i'm talking about aqemu.
What ever default is assigned to (witethrough?) it should be writeback (don't know who handles the default alias).
In case of adding a storage to an vm i always had to change the cache option.
I think it would be better if the default is an more useful one. Useful with the meaning of time consuming and data integrety.
Here's a quote from the qemu 2.6 man page:
By default, the cache=writeback mode is used. It will report data writes as completed as soon as
the data is present in the host page cache. This is safe as long as your guest OS makes sure to
correctly flush disk caches where needed. If your guest OS does not handle volatile disk write
caches correctly and your host crashes or loses power, then the guest may experience data
corruption.
Since cache=writeback is the default in the latest qemu, I think I can close this.
If you have any other issues, https://github.com/tobimensch/aqemu/issues is now
the recommended place to file them.
AQEMU version 0.9.2 was released yesterday.