qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [question] updating the base image for all clones which havebeen running for months
Date: Mon, 3 Nov 2014 20:37:47 +0800	[thread overview]
Message-ID: <201411032037450771771@sangfor.com> (raw)
In-Reply-To: 20141103121421.GE4437@noname.str.redhat.com

>> Hi, all
>> 
>> I used base image A to clone so many vm, 
>> after running for months, each vm has its own private applications and data,
>> which maybe different from each other.
>> Now, I want to install some applications for all of the clones,
>> what should I do?
>
>Install the applications on each clone separately, or use some other
>method to make it available (like installing on a shared network
>resource).
>
Could you detail "installing on a shared network resource"?

Thanks,
Zhang Haoyu
>> Can I rebase image A to B which have the applications to be installed,
>> then change the base image to B for all clones?
>
>The problem is that rebase works on the block level, not on the file
>system level. 
Yes, this is the point.

>Changing the backing file won't produce a correctly
>working guest, it causes file system corruption.
>
>Kevin

  reply	other threads:[~2014-11-03 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 12:04 [Qemu-devel] [question] updating the base image for all clones which have been running for months Zhang Haoyu
2014-11-03 12:14 ` Kevin Wolf
2014-11-03 12:37   ` Zhang Haoyu [this message]
2014-11-04 13:30     ` [Qemu-devel] [question] updating the base image for all clones which havebeen " Eric Blake
2014-11-07  2:16     ` [Qemu-devel] [question] updating the base image for all clones which have been " Zhang Haoyu

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=201411032037450771771@sangfor.com \
    --to=zhanghy@sangfor.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).