Perryg wrote:Seems to me that would change things that the encryption software would deem as suspicious.
AIUI, VirtualBox encrypts the image, not the VDI (or other) headers. If you enlarge the disk then I expect you'd end up with an image, some of which is encrypted and some not. However... would VirtualBox encrypt zero blocks? ISTM that would waste a lot of disk space. If not then all it sees is some extra zero blocks.
I'd guess that it takes more than a resize to screw things up.
mpack wrote:However... would VirtualBox encrypt zero blocks?
It would seem to me that it doesn't. In my quick and dirty test, the size on disk before and after the resize were almost the same. Definitely not enough to justify encrypting the zero-blocks.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
So I've just had this problem - trying to add a copied VM (folder with disk image, vbox file et al) to a totally fresh VirtualBox install and getting the DEK file missing error. I was tearing my hair out until I went into the VM settings, to General > Disk Encryption and tried to Enable Disk Encryption and only there did it flash up a warning to tell me to install the Extension Pack (which I had forgotten to do up until that point) and that encryption wouldn't work without it.
Maybe the error in the log could be a bit more helpful in this instance? Like "you're trying to load a VM with disk encryption but you haven't installed the Extension Pack yet, you fool".
Let us leave this 6 year old topic to rest. If you have a problem with VirtualBox today then start your own topic and provide a VM log, see what others do for example.
Then I also don't know whats going on here.