Windows Server TechCenter > Windows Server Forums > Hyper-V > how to change the .bin file location for a Virtual Machine in hyper-v without changing the VHD location?
Ask a questionAsk a question
 

Answerhow to change the .bin file location for a Virtual Machine in hyper-v without changing the VHD location?

  • Wednesday, September 16, 2009 11:26 AMRamy.eg Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    i'm using hyper-v R2, the bin file that the hyper-v create for VM memory contents takes a lot of space equal to the memory of the virtual machine.  i need to change the location of that file without changing the location of the VHD as it consume the free space which make the Virtual machine down.

Answers

  • Wednesday, September 16, 2009 1:04 PMDavid Bermingham Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Export the virtual machine, import it to the location where you want the configuration files (including the bin file), copy the VHD file back to the original location, edit the VM and browse to the location of the original hard disk.

    You should now have you bin file on one volume and your VHD on another.
    David A. Bermingham, Director of Product Management, SteelEye Technology
    • Proposed As Answer byDavid Bermingham Wednesday, September 16, 2009 4:00 PM
    • Marked As Answer byRamy.eg Thursday, September 17, 2009 5:43 PM
    •  

All Replies

  • Wednesday, September 16, 2009 1:04 PMDavid Bermingham Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Export the virtual machine, import it to the location where you want the configuration files (including the bin file), copy the VHD file back to the original location, edit the VM and browse to the location of the original hard disk.

    You should now have you bin file on one volume and your VHD on another.
    David A. Bermingham, Director of Product Management, SteelEye Technology
    • Proposed As Answer byDavid Bermingham Wednesday, September 16, 2009 4:00 PM
    • Marked As Answer byRamy.eg Thursday, September 17, 2009 5:43 PM
    •  
  • Wednesday, September 16, 2009 2:52 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    As David mentions - Export and import is the easiest way of moving all elements of a VM.

    There are two reasons for having a .bin - one is saved states or snapshots that are taken when a VM is running (yes, these can consume considerable amounts of space).  Another is possible runtime pauses, saves, etc.

    If you are taking a number of running snapshots, then you will always have the memory state files being saved - the only way to reduce the size of these files if to reduce the RAM of the VM.
    As a sideline, many VMs run better with reduced RAM (less than you would give it if you were specificying hardware).


    Brian Ehlert (hopefully you have found this useful)
  • Thursday, September 17, 2009 6:17 PMRamy.eg Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thankx David, thats a good workaroud ... i'll go with it