Re: Live migration with non-shared storage leads to corrupted file system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the comments. Forgot to mention it but yes, I do have
"cache=none" configured for the migrated domain, as

     <driver name='qemu' type='raw' cache='none'/>

in my XML file, and doubled-checked before and after the migration. In
fact, if cache is not set to "none", virsh will issue a warning and
refuse to do the live migration.

Brett

On Sun, Nov 25, 2012 at 7:12 PM, Henrik Ahlgren <pablo@xxxxxxxxxxxxx> wrote:
> On Sun, Nov 25, 2012 at 06:57:19PM +0800, Xinglong Wu wrote:
>> Is there anybody having the similiar experience with live migration on
>> non-shared storage? It apparently leads to failed migrations in
>> libvirt but no cirtical errors ever reported.
>
> Make sure you have your driver cache set to "none". I've seen similar
> things happen with other cache settings, but with "none" it works just
> fine (but of course that might impose an i/o performance penalty in
> some cases?). I think the default is "unsafe" in 0.9.7 and later? It
> would be nice if the cache settings were documented more clearly.
>

_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users


[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux