Can I only commit from part data of active image to corresponding range of its backing files by qemu cmd?

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
split data to 3 chunks and save it in 3 independent backing files like below:
img.000 <-- img.001 <-- img.002
img.000 is the backing file of img.001 and 001 is the backing file of 002.
img.000 saves the 1st chunk of data and img.001 saves the 2nd chunk of data, and img.002 saves the 3rd chunk of data.
Now I have new image img.003 stores cow data of 1st chunk and img.002 is the backing file of img.003.
The backing chain is like this:
img.000 <-- img.001 <-- img.002 <-- img.003
So that means the data of img.003 saves the same range with img.000 but different data.
I know I can use qemu-img commit but it only commit the data from img.003 to img.002.
If I use qemu-img rebase -b img.000 img.003, the data of img.001 and img.002 will merge into img.003.
What I want is only commit the data from img.003 into img.000 because the data of the two image are the same range(1st chunk)
Is there anyway to commit(or merge) data of active image into corresponding backing files?
linux virtual-machine qemu
add a comment |Â
up vote
0
down vote
favorite
split data to 3 chunks and save it in 3 independent backing files like below:
img.000 <-- img.001 <-- img.002
img.000 is the backing file of img.001 and 001 is the backing file of 002.
img.000 saves the 1st chunk of data and img.001 saves the 2nd chunk of data, and img.002 saves the 3rd chunk of data.
Now I have new image img.003 stores cow data of 1st chunk and img.002 is the backing file of img.003.
The backing chain is like this:
img.000 <-- img.001 <-- img.002 <-- img.003
So that means the data of img.003 saves the same range with img.000 but different data.
I know I can use qemu-img commit but it only commit the data from img.003 to img.002.
If I use qemu-img rebase -b img.000 img.003, the data of img.001 and img.002 will merge into img.003.
What I want is only commit the data from img.003 into img.000 because the data of the two image are the same range(1st chunk)
Is there anyway to commit(or merge) data of active image into corresponding backing files?
linux virtual-machine qemu
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
split data to 3 chunks and save it in 3 independent backing files like below:
img.000 <-- img.001 <-- img.002
img.000 is the backing file of img.001 and 001 is the backing file of 002.
img.000 saves the 1st chunk of data and img.001 saves the 2nd chunk of data, and img.002 saves the 3rd chunk of data.
Now I have new image img.003 stores cow data of 1st chunk and img.002 is the backing file of img.003.
The backing chain is like this:
img.000 <-- img.001 <-- img.002 <-- img.003
So that means the data of img.003 saves the same range with img.000 but different data.
I know I can use qemu-img commit but it only commit the data from img.003 to img.002.
If I use qemu-img rebase -b img.000 img.003, the data of img.001 and img.002 will merge into img.003.
What I want is only commit the data from img.003 into img.000 because the data of the two image are the same range(1st chunk)
Is there anyway to commit(or merge) data of active image into corresponding backing files?
linux virtual-machine qemu
split data to 3 chunks and save it in 3 independent backing files like below:
img.000 <-- img.001 <-- img.002
img.000 is the backing file of img.001 and 001 is the backing file of 002.
img.000 saves the 1st chunk of data and img.001 saves the 2nd chunk of data, and img.002 saves the 3rd chunk of data.
Now I have new image img.003 stores cow data of 1st chunk and img.002 is the backing file of img.003.
The backing chain is like this:
img.000 <-- img.001 <-- img.002 <-- img.003
So that means the data of img.003 saves the same range with img.000 but different data.
I know I can use qemu-img commit but it only commit the data from img.003 to img.002.
If I use qemu-img rebase -b img.000 img.003, the data of img.001 and img.002 will merge into img.003.
What I want is only commit the data from img.003 into img.000 because the data of the two image are the same range(1st chunk)
Is there anyway to commit(or merge) data of active image into corresponding backing files?
linux virtual-machine qemu
linux virtual-machine qemu
edited Sep 13 at 4:36
Rui F Ribeiro
36.8k1273117
36.8k1273117
asked Sep 13 at 3:38
yayaya
346
346
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468687%2fcan-i-only-commit-from-part-data-of-active-image-to-corresponding-range-of-its-b%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password