From: Avi Kivity <avi@redhat.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: sharing a (mostly) read-only virtual block device
Date: Sun, 18 Oct 2009 16:02:20 +0900 [thread overview]
Message-ID: <4ADABD7C.50803@redhat.com> (raw)
In-Reply-To: <4AD84EB5.5070200@nagafix.co.uk>
On 10/16/2009 07:45 PM, Antoine Martin wrote:
> Hi,
>
> Is there an easy way that I have missed to share a virtual disk
> read-only between many guests whilst still having the ability to update
> it occasionally from the host?
>
>
That's very fragile, since the guest won't expect the disk to change
under its feet. Expect oopses.
> I was hoping I could use a shared image file, and occasionally replace
> it with an updated version (move old copy to disk_image.bak, copy new
> image to disk_image), then the guests could umount/mount the drive and
> get access to the new disk image.
>
> Unfortunately qemu opens the virtual disk as soon as the guest boots, so
> the file descriptor still points to the old image.
> Note: I do not want to use the qemu monitor from the host as I want the
> guests to be in charge of when/if they get the new disk image.
>
>
I suggest using a monitor, and have the host and guest coordinate the
change (guest unmounts, host modifies, guest mounts).
Alternatively, export the disk from the host using nfs.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-10-18 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 10:45 sharing a (mostly) read-only virtual block device Antoine Martin
2009-10-18 7:02 ` Avi Kivity [this message]
2009-10-18 8:32 ` Michael Tokarev
2009-10-18 12:25 ` Antoine Martin
2009-10-19 1:51 ` Avi Kivity
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=4ADABD7C.50803@redhat.com \
--to=avi@redhat.com \
--cc=antoine@nagafix.co.uk \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.