Avi Kivity wrote: > nadim khemir wrote: > >> Hi, great work. >> >> While playing with kvm-qemu I noticed a few points that might be of >> interrest: >> >> 1/ -loadvm and -snapshot don't work together. It works as if -loadvm wasn't >> passed as argument >> >> 2/ two instances of kvm can be passed the same -hda. There is no locking >> whatsoever. This messes up things seriously. >> >> >> > > These two are upstream qemu problems. Copying qemu-devel. > > I guess using file locking by default would improve the situation, and > we can add a -drive ...,exclusive=no option for people playing with > cluster filesystems. >
This is not a situation where the user has a reasonable expectation of what will happen that we violate. If the user is unhappy with the results, it's because the user made a mistake. FWIW, the whole override thing for Xen has been an endless source of pain. It's very difficult (if not impossible) to accurately determine if someone else is using the disk. Also, it tends to confuse people trying to do something legitimate more often than helping someone doing something stupid. I very frequently run multiple VMs with the same disk. I do it strictly for the purposes of benchmarking. There are ways to share a disk without using a clustered filesystem. If a higher level management tool wants to enforce a policy (like libvirt), then let it. We should not be enforcing policies within QEMU though. Regards, Anthony Liguori ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
