Re: [kvm-devel] Feedback and errors

2008-05-04 Thread nadim khemir
On Sunday 04 May 2008 13.19.30 Avi Kivity wrote: > ... > > > I guess it's usage patterns. I'm pretty religious about using -snapshot > > unless I have a very specific reason not to. I have never encountered > > this problem myself. > > Most users cannot use -snapshot for their workloads. and -s

Re: [kvm-devel] Feedback and errors

2008-05-04 Thread Javier Guerra Giraldez
On Friday 02 May 2008, Anthony Liguori wrote: > What we really need is a global configuration file so that individual > users can select these defaults according to what makes sense for them. i favor the idea of writing parameters into the boot image itself. -- Javier signature.asc Description

Re: [kvm-devel] Feedback and errors

2008-05-04 Thread Avi Kivity
Anthony Liguori wrote: > Avi Kivity wrote: > >> Well, one user (me) has made this mistake, several times. >> > > I guess it's usage patterns. I'm pretty religious about using -snapshot > unless I have a very specific reason not to. I have never encountered > this problem myself. > >

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Anthony Liguori
Avi Kivity wrote: > > Well, one user (me) has made this mistake, several times. I guess it's usage patterns. I'm pretty religious about using -snapshot unless I have a very specific reason not to. I have never encountered this problem myself. >> FWIW, the whole override thing for Xen has been

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Avi Kivity
Daniel P. Berrange wrote: >> 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. >> > > Turning on file locking by default will break existing apps / deployments > using shared d

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Avi Kivity
Anthony Liguori wrote: >>> >>> 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 situ

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Daniel P. Berrange
On Fri, May 02, 2008 at 01:52:18PM +0300, 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 argume

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Anthony Liguori
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 pass

Re: [kvm-devel] Feedback and errors

2008-05-02 Thread Avi Kivity
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

[kvm-devel] Feedback and errors

2008-04-28 Thread nadim khemir
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 thin