How do I use VMDKs with VirtualBox?












1














I've got a backup of my VM's old VMWare folder including the VMDK files. It looks like VirtualBox should be able to handle VMDKs, but it's telling me it can't. Googling about it everything just talks about one VMDK file, but I've actually got 3 and suspect that may be the issue. This VM just had a single drive, yet I've got "computer_2.vmdk" (only 1 KB), "computer_2-ctk.vmdk" (8MB), and "computer_2-flat.vmdk" which is the full 250GB that my VM takes.



Is there something special I need to do to consolidate or prep these VMDKs for VirtualBox usage?










share|improve this question






















  • What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
    – HackSlash
    Dec 14 '18 at 17:24










  • "Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
    – Brian Knoblauch
    Dec 14 '18 at 17:43






  • 1




    Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
    – Austin Hemmelgarn
    Dec 14 '18 at 19:10










  • Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
    – essjae
    Dec 14 '18 at 23:26










  • What version of VMWare was used to make these disks?
    – HackSlash
    Dec 14 '18 at 23:27
















1














I've got a backup of my VM's old VMWare folder including the VMDK files. It looks like VirtualBox should be able to handle VMDKs, but it's telling me it can't. Googling about it everything just talks about one VMDK file, but I've actually got 3 and suspect that may be the issue. This VM just had a single drive, yet I've got "computer_2.vmdk" (only 1 KB), "computer_2-ctk.vmdk" (8MB), and "computer_2-flat.vmdk" which is the full 250GB that my VM takes.



Is there something special I need to do to consolidate or prep these VMDKs for VirtualBox usage?










share|improve this question






















  • What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
    – HackSlash
    Dec 14 '18 at 17:24










  • "Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
    – Brian Knoblauch
    Dec 14 '18 at 17:43






  • 1




    Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
    – Austin Hemmelgarn
    Dec 14 '18 at 19:10










  • Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
    – essjae
    Dec 14 '18 at 23:26










  • What version of VMWare was used to make these disks?
    – HackSlash
    Dec 14 '18 at 23:27














1












1








1







I've got a backup of my VM's old VMWare folder including the VMDK files. It looks like VirtualBox should be able to handle VMDKs, but it's telling me it can't. Googling about it everything just talks about one VMDK file, but I've actually got 3 and suspect that may be the issue. This VM just had a single drive, yet I've got "computer_2.vmdk" (only 1 KB), "computer_2-ctk.vmdk" (8MB), and "computer_2-flat.vmdk" which is the full 250GB that my VM takes.



Is there something special I need to do to consolidate or prep these VMDKs for VirtualBox usage?










share|improve this question













I've got a backup of my VM's old VMWare folder including the VMDK files. It looks like VirtualBox should be able to handle VMDKs, but it's telling me it can't. Googling about it everything just talks about one VMDK file, but I've actually got 3 and suspect that may be the issue. This VM just had a single drive, yet I've got "computer_2.vmdk" (only 1 KB), "computer_2-ctk.vmdk" (8MB), and "computer_2-flat.vmdk" which is the full 250GB that my VM takes.



Is there something special I need to do to consolidate or prep these VMDKs for VirtualBox usage?







virtualbox virtual-machine vmware






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 14 '18 at 17:20









Brian Knoblauch

3,60193150




3,60193150












  • What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
    – HackSlash
    Dec 14 '18 at 17:24










  • "Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
    – Brian Knoblauch
    Dec 14 '18 at 17:43






  • 1




    Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
    – Austin Hemmelgarn
    Dec 14 '18 at 19:10










  • Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
    – essjae
    Dec 14 '18 at 23:26










  • What version of VMWare was used to make these disks?
    – HackSlash
    Dec 14 '18 at 23:27


















  • What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
    – HackSlash
    Dec 14 '18 at 17:24










  • "Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
    – Brian Knoblauch
    Dec 14 '18 at 17:43






  • 1




    Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
    – Austin Hemmelgarn
    Dec 14 '18 at 19:10










  • Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
    – essjae
    Dec 14 '18 at 23:26










  • What version of VMWare was used to make these disks?
    – HackSlash
    Dec 14 '18 at 23:27
















What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
– HackSlash
Dec 14 '18 at 17:24




What happens when you attach the big one as an "Existing Virtual Hard Disk" on a new VM?
– HackSlash
Dec 14 '18 at 17:24












"Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
– Brian Knoblauch
Dec 14 '18 at 17:43




"Could not get the storage format of the medium … (VERR_NOT_SUPPORTED)" with a Result Code of VBOX_E_IPRT_ERROR (0x80BB0005) and a CalleeRC:of VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) for any of the 3 VMDKs.
– Brian Knoblauch
Dec 14 '18 at 17:43




1




1




Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
– Austin Hemmelgarn
Dec 14 '18 at 19:10




Most likely the VMDK files are using a revision of the VMDK format that is unsupported by VirtualBox.
– Austin Hemmelgarn
Dec 14 '18 at 19:10












Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
– essjae
Dec 14 '18 at 23:26




Which one are you trying to mount? The "-flat" shouldn't be mounted, you should mount the 1KB file, that's the one with the configuration info, "-flat" vmdks are data only, and generally can't be mounted directly.
– essjae
Dec 14 '18 at 23:26












What version of VMWare was used to make these disks?
– HackSlash
Dec 14 '18 at 23:27




What version of VMWare was used to make these disks?
– HackSlash
Dec 14 '18 at 23:27










2 Answers
2






active

oldest

votes


















3














You can also use free V2V Converter from StarWind. It has user-friendly GUI and supports VMDK, VHD/VHDX, QCOW2, physical drives:
https://www.starwindsoftware.com/starwind-v2v-converter






share|improve this answer





























    2














    A quick internet search of the term "ctk.vmdk" got me to This VMware forum thread, and it seems the virtual disk was created with changed block tracking enabled, and such feature is likely to be unsupported by Virtualbox, (or at least not in same format as VMware).



    If you still have access to your VMware software, you can try with the following steps. (make sure you delete (or apply) any snapshots in this machine)




    1. Power off your virtual machine. (if it's running)

    2. Right click the VM, click “Edit settings”, find the “Options” tab and click “Configuration Parameters”

    3. Set the “ctkEnabled” value to false

    4. Set the “scsi0:x.ctkEnabled” value to false for each disk of the VM in question

    5. Open the source folder and remove any -CTK.VMDK files

    6. Power on the VM

    7. Power off the VM (this is needed to update the CTK table)


    then the site mentions a few further steps which might be unnecessary in your case.




    1. Power on the VM

    2. Rerun Backup program


    the instructions are taken from this thread



    Hope it Helps!






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      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',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383644%2fhow-do-i-use-vmdks-with-virtualbox%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3














      You can also use free V2V Converter from StarWind. It has user-friendly GUI and supports VMDK, VHD/VHDX, QCOW2, physical drives:
      https://www.starwindsoftware.com/starwind-v2v-converter






      share|improve this answer


























        3














        You can also use free V2V Converter from StarWind. It has user-friendly GUI and supports VMDK, VHD/VHDX, QCOW2, physical drives:
        https://www.starwindsoftware.com/starwind-v2v-converter






        share|improve this answer
























          3












          3








          3






          You can also use free V2V Converter from StarWind. It has user-friendly GUI and supports VMDK, VHD/VHDX, QCOW2, physical drives:
          https://www.starwindsoftware.com/starwind-v2v-converter






          share|improve this answer












          You can also use free V2V Converter from StarWind. It has user-friendly GUI and supports VMDK, VHD/VHDX, QCOW2, physical drives:
          https://www.starwindsoftware.com/starwind-v2v-converter







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 17 '18 at 16:14









          batistuta09

          22815




          22815

























              2














              A quick internet search of the term "ctk.vmdk" got me to This VMware forum thread, and it seems the virtual disk was created with changed block tracking enabled, and such feature is likely to be unsupported by Virtualbox, (or at least not in same format as VMware).



              If you still have access to your VMware software, you can try with the following steps. (make sure you delete (or apply) any snapshots in this machine)




              1. Power off your virtual machine. (if it's running)

              2. Right click the VM, click “Edit settings”, find the “Options” tab and click “Configuration Parameters”

              3. Set the “ctkEnabled” value to false

              4. Set the “scsi0:x.ctkEnabled” value to false for each disk of the VM in question

              5. Open the source folder and remove any -CTK.VMDK files

              6. Power on the VM

              7. Power off the VM (this is needed to update the CTK table)


              then the site mentions a few further steps which might be unnecessary in your case.




              1. Power on the VM

              2. Rerun Backup program


              the instructions are taken from this thread



              Hope it Helps!






              share|improve this answer




























                2














                A quick internet search of the term "ctk.vmdk" got me to This VMware forum thread, and it seems the virtual disk was created with changed block tracking enabled, and such feature is likely to be unsupported by Virtualbox, (or at least not in same format as VMware).



                If you still have access to your VMware software, you can try with the following steps. (make sure you delete (or apply) any snapshots in this machine)




                1. Power off your virtual machine. (if it's running)

                2. Right click the VM, click “Edit settings”, find the “Options” tab and click “Configuration Parameters”

                3. Set the “ctkEnabled” value to false

                4. Set the “scsi0:x.ctkEnabled” value to false for each disk of the VM in question

                5. Open the source folder and remove any -CTK.VMDK files

                6. Power on the VM

                7. Power off the VM (this is needed to update the CTK table)


                then the site mentions a few further steps which might be unnecessary in your case.




                1. Power on the VM

                2. Rerun Backup program


                the instructions are taken from this thread



                Hope it Helps!






                share|improve this answer


























                  2












                  2








                  2






                  A quick internet search of the term "ctk.vmdk" got me to This VMware forum thread, and it seems the virtual disk was created with changed block tracking enabled, and such feature is likely to be unsupported by Virtualbox, (or at least not in same format as VMware).



                  If you still have access to your VMware software, you can try with the following steps. (make sure you delete (or apply) any snapshots in this machine)




                  1. Power off your virtual machine. (if it's running)

                  2. Right click the VM, click “Edit settings”, find the “Options” tab and click “Configuration Parameters”

                  3. Set the “ctkEnabled” value to false

                  4. Set the “scsi0:x.ctkEnabled” value to false for each disk of the VM in question

                  5. Open the source folder and remove any -CTK.VMDK files

                  6. Power on the VM

                  7. Power off the VM (this is needed to update the CTK table)


                  then the site mentions a few further steps which might be unnecessary in your case.




                  1. Power on the VM

                  2. Rerun Backup program


                  the instructions are taken from this thread



                  Hope it Helps!






                  share|improve this answer














                  A quick internet search of the term "ctk.vmdk" got me to This VMware forum thread, and it seems the virtual disk was created with changed block tracking enabled, and such feature is likely to be unsupported by Virtualbox, (or at least not in same format as VMware).



                  If you still have access to your VMware software, you can try with the following steps. (make sure you delete (or apply) any snapshots in this machine)




                  1. Power off your virtual machine. (if it's running)

                  2. Right click the VM, click “Edit settings”, find the “Options” tab and click “Configuration Parameters”

                  3. Set the “ctkEnabled” value to false

                  4. Set the “scsi0:x.ctkEnabled” value to false for each disk of the VM in question

                  5. Open the source folder and remove any -CTK.VMDK files

                  6. Power on the VM

                  7. Power off the VM (this is needed to update the CTK table)


                  then the site mentions a few further steps which might be unnecessary in your case.




                  1. Power on the VM

                  2. Rerun Backup program


                  the instructions are taken from this thread



                  Hope it Helps!







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Dec 15 '18 at 2:06

























                  answered Dec 15 '18 at 2:01









                  Jenny T-Type

                  1215




                  1215






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383644%2fhow-do-i-use-vmdks-with-virtualbox%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                      Alcedinidae

                      RAC Tourist Trophy