From: Antoine Martin Subject: sharing a (mostly) read-only virtual block device Date: Fri, 16 Oct 2009 17:45:09 +0700 Message-ID: <4AD84EB5.5070200@nagafix.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: "kvm@vger.kernel.org" Return-path: Received: from mamba.nagafix.co.uk ([194.145.196.68]:51795 "EHLO mail.nagafix.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755706AbZJPKxB (ORCPT ); Fri, 16 Oct 2009 06:53:01 -0400 Received: (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: antoine@nagafix.co.uk) by mail.nagafix.co.uk (Postfix) with ESMTPSA id D59D5666D for ; Fri, 16 Oct 2009 11:45:11 +0100 (BST) Sender: kvm-owner@vger.kernel.org List-ID: 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? 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. Any suggestions / other ways of doing this? Thanks Antoine