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

The name of the pictureThe name of the pictureThe name of the pictureClash 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?










share|improve this question



























    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?










    share|improve this question

























      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?










      share|improve this question















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 13 at 4:36









      Rui F Ribeiro

      36.8k1273117




      36.8k1273117










      asked Sep 13 at 3:38









      yayaya

      346




      346

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          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



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          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













































































          Popular posts from this blog

          Peggy Mitchell

          Palaiologos

          The Forum (Inglewood, California)