I'm developing my own OS and want to test it with VirtualBox. All stuff (kernel, driver, user-apps, ...) is stored on a hard disk image that is generated by me. So as soon as any of these change the disk image has to be changed, too. As soon as the disk image changed VirtualBox complains about it with something like:
In the long run it is a little bit annoying that I have to release and remove the disk, add it again and assign it to my VM everytime to be able to start it again.VirtualBox wrote:VM cannot start because the hard disk '/home/hrniels/escape/source/vmware/vmwarehddimg.vmdk' is not accessible (Actual UUID {6967a079-685d-4a98-894c-74d8058715b3} of the hard disk image '/home/hrniels/escape/source/vmware/vmwarehddimg.vmdk' doesn't match UUID {c66e84ad-1ca2-4c7e-9307-4bc63ccb9a46} stored in the registry).
So my question is: Is there a way to tell VirtualBox that it should ignore it and simply use the image although it has changed? Or is it possible (not too complicated) to generate the UUID on my own from the disk image and change it in the config so that VirtualBox doesn't notice the change? Or any other way to automate it?
Thanks!
hrniels