[fedora-arm] Write-back vs. write-through for VMs

[Sean Omalley]

I -think- a big part of the issue was syncing with the qcow file format for the vm containers. There were two major issues.
I don't know if I can find the page again where is stated the issues. However, that isn't really relevent to the sd card filesystem which the armv7 image uses.

Is there an armv5 image on the way???

Also the new version of libvirt/virt manager in F18 x86 doesn't list the arm cpu's like it did in F17.. I was trying to "create" a vm using the existing/provided disk image that works with virt manager. which is kind of where pci, and ide, and all that stuff comes in handy. Given there is no sd card drive type in libvirt or at least that shows up in virtmanager. 






----- Original Message -----
> From: Daniel Veillard <veillard at redhat.com>
> To: Sean Omalley <omalley_s at rocketmail.com>
> Cc: Jonathan Masters <jcm at redhat.com>; Jerry James <loganjerry at gmail.com>; Fedora ARM <arm at lists.fedoraproject.org>
> Sent: Friday, January 11, 2013 11:58 PM
> Subject: Re: [fedora-arm] Write-back vs. write-through for VMs
> 
> On Fri, Jan 11, 2013 at 11:48:41AM -0800, Sean Omalley wrote:
>>  They switched the default cache to writeback in qemu 1.2 which is shipped 
> with F18.
>>  http://wiki.qemu.org/ChangeLog/1.2
>> 
>>  F17 shipped with qemu version 1.0.1 which I think defaults to writethrough. 
> 
>> 
>>  If you don't change the command I'd think you should get writeback 
> automatically after the upgrade. 
> 
>   Indeed, I would suggest to go with QEmu defaults there and not try to
> override. I/O and consistency there are very complex issues, I would say
> don't try to change the default unless you really know the issues at
> hand and the specifics of the target system :-)
> 
> Daniel
> 
> -- 
> Daniel Veillard      | Open Source and Standards, Red Hat
> veillard at redhat.com  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
> http://veillard.com/ | virtualization library  http://libvirt.org/
>