qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: nadim khemir <nadim@khemir.net>,
	kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] Feedback and errors
Date: Fri, 02 May 2008 09:32:35 -0500	[thread overview]
Message-ID: <481B2603.3050800@codemonkey.ws> (raw)
In-Reply-To: <481AF262.4080305@qumranet.com>

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

  reply	other threads:[~2008-05-02 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804282258.08426.nadim@khemir.net>
2008-05-02 10:52 ` [Qemu-devel] Re: [kvm-devel] Feedback and errors Avi Kivity
2008-05-02 14:32   ` Anthony Liguori [this message]
2008-05-02 15:00     ` Avi Kivity
2008-05-02 15:21       ` Anthony Liguori
2008-05-04 11:19         ` Avi Kivity
2008-05-04 22:52           ` nadim khemir
2008-05-04 12:39         ` Javier Guerra Giraldez
2008-05-02 14:45   ` Daniel P. Berrange
2008-05-02 15:02     ` Avi Kivity
2008-05-02 15:23     ` Jamie Lokier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=481B2603.3050800@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=nadim@khemir.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).