Reset immutable disks at "Restoring virtual machine" is erroneous

[FelixG]

When an saved stated (frozen machine) is resumed, virtualbox reset inmutable disks.

This is wrong because it causes an inestable status in the virtual machine. Inmutable disks only must be reset with a cold start.

(Host and guest are Windows S.O. The inmutable disk is used to contain temporal directories and pagefile.sys, preventing the growth of the primary disk)

Other issues:

• Immutable mark is lost when cloning or importing virtual machines. (https://www.virtualbox.org/ticket/13079)

• With "--autoreset off", an inmmutable disk is equal to a multiattach disk. It would be interesting to have a manual reset option.

[FelixG]

Restoring virtual machine

[FelixG]

Release 4.3.28 continues with the same problem.

Please solve this problem in the next release, it's easy to correct!

[FelixG]

Release 5.0.0 also has the same problem.

Reset the disk when the machine is resumed, causes an inestable status!!!!

Immutable disks only must be reset with a cold start.

Please, change it.

[Flow86]

ran into same problem.

please, change this soon!

it renders whole disks unusable, since the filesystem is cached in ram on most operating systems!

[Klaus Espenlaub]

Gah. Your attachment made me believe you're talking about starting a VM from a restored snapshot (which works perfectly!). Now the problem is clear, and it's a bug which existed for many many years. Clearly no one thought of this case, and as there are only very few users of immutable disks in general (and most use it in very specific ways, apparently not touching saved state) it's not a code which gets touched or changed.

[Frank Mehnert]

Fix committed to VBox 5.0.x, please try a recent test build from here (revision >= 101939).

[Frank Mehnert]

The latest 4.3.x builds contain the fix as well.

[Frank Mehnert]

Fix is part of VBox 5.0.2.