回答：这个bin文件，及其附近的vsv文件，都是VM必须的文件。bin文件，是VM的内存文件，一般会和内存差不多大。vsv是saved状态时的文件。
bin文件，对于cluster里failover时也是有用的。当live migration时，这个也是要传输的。这个文件不可删除。
您如果觉得这个文件太大，则您必须调整VM的存储位置，把VM export/import到一个较大的分区。
另外，为了您能更好的理解这些文件类型，您可以参考：
Hyper-V: How to Find VM Files http://social.technet.microsoft. ... -find-vm-files.aspx
Virtual Machine Snapshots with Hyper-V http://blogs.technet.com/b/robla ... s-with-hyper-v.aspx
另外，这些文件包括vsv，一般都是不可以删除。如果一个VM被save了，那save状态的文件自然是不可以删除的了。而且，很多时候，这些文件，都是由系统自己创建的。删了，那这个VM可能就报废了。作者: shillan 时间: 2017-8-24 08:05
What you are talking about is a normal behavior in Hyper-V.
A .VSV file is Virtual machine saved state files, a .BIN file is Virtual machine memory contents.
The virtual machine save state file (*.vsv) and the virtual machine memory contents (*.bin) file are only created if a snapshot is taken of a running or saved virtual machine. These files are not created if the virtual machine is turned off and a snapshot is taken.
Meanwhile, the .vsv and .bin file will be created under X:\XXX\VM-Name\Virtual Machines\GUID if the VM is running, no matter the VM has snapshot or not. In other words, if you have a running VM with snapshots, there should be two .vsv and .bin files under the VM’s folder.
I understand that the .bin file cost lots of space on your system drive. General speaking, we don’t recommend that you keep the VM in the system drive. You can change the location of the VM(include settings and VHD file) to another drive when you create the VM. For your environment, you can export the VM to another drive which has enough room and then import it to the Hyper-V Manager. (You can delete the previous VM if desired) http://social.technet.microsoft. ... -bb44-2fc7e8323ab9/
