* [Qemu-devel] I/O in backing file
@ 2012-03-28 5:17 PANKAJ RAWAT
2012-03-30 4:17 ` PANKAJ RAWAT
0 siblings, 1 reply; 3+ messages in thread
From: PANKAJ RAWAT @ 2012-03-28 5:17 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi all,
I am currently using backing file.The question of my concern is regarding
the I/O operation
Now when we create a external snapshot in qcow2, a new file is created
leaving the original file as backing file
*
Can any one tell,*how the I/O is performed in detail way?.
Means when the new snapshot is booted which refer to the backing file as
original file. *How read operation is performed? how it is decided whether
the file is present in the snapshot image or the backing file.?
when write operation is performed how it is decided whether the file is
already present in backing file or we have to create a new one ?*
[-- Attachment #2: Type: text/html, Size: 681 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Qemu-devel] I/O in backing file
2012-03-28 5:17 [Qemu-devel] I/O in backing file PANKAJ RAWAT
@ 2012-03-30 4:17 ` PANKAJ RAWAT
2012-03-30 7:07 ` Stefan Hajnoczi
0 siblings, 1 reply; 3+ messages in thread
From: PANKAJ RAWAT @ 2012-03-30 4:17 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi all,
I am currently using backing file.The question of my concern is regarding
the I/O operation
Now when we create a external snapshot in qcow2, a new file is created
leaving the original file as backing file
*
Can any one tell,*how the I/O is performed in detail way?.
Means when the new snapshot is booted which refer to the backing file as
original file. *How read operation is performed? how it is decided whether
the file is present in the snapshot image or the backing file.?
when write operation is performed how it is decided whether the file is
already present in backing file or we have to create a new one ?*
[-- Attachment #2: Type: text/html, Size: 712 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] I/O in backing file
2012-03-30 4:17 ` PANKAJ RAWAT
@ 2012-03-30 7:07 ` Stefan Hajnoczi
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Hajnoczi @ 2012-03-30 7:07 UTC (permalink / raw)
To: PANKAJ RAWAT; +Cc: qemu-devel
On Fri, Mar 30, 2012 at 09:47:52AM +0530, PANKAJ RAWAT wrote:
> I am currently using backing file.The question of my concern is regarding
> the I/O operation
> Now when we create a external snapshot in qcow2, a new file is created
> leaving the original file as backing file
> *
> Can any one tell,*how the I/O is performed in detail way?.
>
> Means when the new snapshot is booted which refer to the backing file as
> original file. *How read operation is performed? how it is decided whether
> the file is present in the snapshot image or the backing file.?
> when write operation is performed how it is decided whether the file is
> already present in backing file or we have to create a new one ?*
>From docs/specs/qed_spec.txt:
"Reads to an unallocated area of the image file access the backing file.
If there is no backing file, then zeroes are produced. The backing file
may be smaller than the image file and reads of unallocated areas beyond
the end of the backing file produce zeroes.
Writes to an unallocated area cause a new data clusters to be allocated,
and a new L2 table if that is also unallocated. The new data cluster is
populated with data from the backing file (or zeroes if no backing file)
and the data being written."
It's similar for qcow2 and other formats that support backing files.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-03-30 8:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-28 5:17 [Qemu-devel] I/O in backing file PANKAJ RAWAT
2012-03-30 4:17 ` PANKAJ RAWAT
2012-03-30 7:07 ` Stefan Hajnoczi
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).