![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Are the .bin and .vsv files static, or constanly being updated while a vm client is running?
When I "save state", I would like to save state to a mlc ssd. But if the vsv and bin files are constanly being written to, I would probabaly burn up the ssd pretty quickly.
When a hyper-v client is created, there is a xml file for the config, and a vhd for the disk.
When that client is running, a .bin and .vsv are also created. The vsv is 20MB, the .bin is equal to the amount of memory configured for the client.
The docs that I have found say that the vsv is the hardware device state of the hardware in the vm. The .bin holds the memory state, in case of snapshot or "save state". The way I am reading that is: Files are created at vm startup and are static, on a "save state" the contents of ram and device state are dumped to the files.
Let's say I am running 24 vm's with 2GB ram each, and I want to save state on all of them at host shutdown, and do it quickly. I would think that dumping the state to a decent ssd would work well.
But I am concerned that the .bin and .vsv files are not static. I'm wondering if the .bin file acts sort of like a swap file or as some kind of ram shadow, that is constantly being updated while the vm is running. Same with the vsv. Maybe it is being constantly updated with the hardware state, to help with abrupt shutdown recovery.
Does anyone know if the vsv and bin files are truely static or not?
When I "save state", I would like to save state to a mlc ssd. But if the vsv and bin files are constanly being written to, I would probabaly burn up the ssd pretty quickly.
When a hyper-v client is created, there is a xml file for the config, and a vhd for the disk.
When that client is running, a .bin and .vsv are also created. The vsv is 20MB, the .bin is equal to the amount of memory configured for the client.
The docs that I have found say that the vsv is the hardware device state of the hardware in the vm. The .bin holds the memory state, in case of snapshot or "save state". The way I am reading that is: Files are created at vm startup and are static, on a "save state" the contents of ram and device state are dumped to the files.
Let's say I am running 24 vm's with 2GB ram each, and I want to save state on all of them at host shutdown, and do it quickly. I would think that dumping the state to a decent ssd would work well.
But I am concerned that the .bin and .vsv files are not static. I'm wondering if the .bin file acts sort of like a swap file or as some kind of ram shadow, that is constantly being updated while the vm is running. Same with the vsv. Maybe it is being constantly updated with the hardware state, to help with abrupt shutdown recovery.
Does anyone know if the vsv and bin files are truely static or not?