xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: hxkhust  <hxkhust@126.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A Problem with Page Cache in Xen
Date: Tue, 31 Jan 2012 03:30:01 +0800 (CST)	[thread overview]
Message-ID: <33c61cf2.5e8.13530186d2c.Coremail.hxkhust@126.com> (raw)
In-Reply-To: <1327940330.26983.257.camel@zakaz.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1428 bytes --]

In the situation I consider here,the VM C won't be running again after it's set up.The existence of VM C is  only for VM A and VM B's running.If VM A or VM B change some blocks in its file system,the change will only be stored in its own virtual disk image whose format is QCOW2.That's meaning which I would like to express.However I cannot find the solution to my problem temporarily.Your further suggest is helpful for me.





At 2012-01-31 00:18:58,"Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>On Mon, 2012-01-30 at 08:11 +0000, hxkhust wrote:
>> Hi,
>>  
>> Recently I'm dong some reserch on xen and encounter a problem that I
>> cannot solve temporarily.I need your help very much and the following
>> is the question I would like to ask:
>> On a physical machine with xen virtualization platform installed ,VM
>> A,VM B are VM C's virtual disks are all image files,among which VM A
>> and VM B's virtual disks are QCOW2 format and VM C's disk is RAW
>> format. And VM A and VM B's virtual disk image files are based on VM
>> C's virtual disk image file.Now these three VMs are running on the
>> same physical machine with xen installed.
>
>This is an invalid/dangerous configuration. You can't really safely
>write to the backing file (C's raw disk) while there are active users (A
>and B's qcow2 images) of it. Imagine e.g. that all three change the same
>bit of filesystem metadata in different ways...
>
>Ian.
>
>

[-- Attachment #1.2: Type: text/html, Size: 2615 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2012-01-30 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30  8:11 A Problem with Page Cache in Xen hxkhust
2012-01-30  9:47 ` Tim Deegan
2012-01-30 16:18 ` Ian Campbell
2012-01-30 19:30 ` hxkhust [this message]
2012-01-31  7:01 ` hxkhust
2012-02-02 11:01   ` Tim Deegan

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=33c61cf2.5e8.13530186d2c.Coremail.hxkhust@126.com \
    --to=hxkhust@126.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xensource.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).