Page 1 of 1

DiskCryptor on Windows 8 guest causes Guru Meditation

Posted: 16. Apr 2015, 20:01
by tommyj27
I am using one of my Windows guests to proof-of-concept DiskCryptor. After encrypting the C: drive, I reboot the guest. On reboot, I am prompted for the encryption password, and I see the Windows splash screen for about a half-second. VirtualBox then throws a Guru Meditation exception, stopping the guest. I have not seen this type of exception before, hoping someone can point me in the right direction.

By comparison, DiskCryptor on real hardware works just fine.

VBox (gzipped) log file is attached.

Thanks!

Re: DiskCryptor on Windows 8 guest causes Guru Meditation

Posted: 13. May 2015, 12:51
by PCFreak
Hi,

I have exactly the same problem. Windows 8.1 x86 Enterprise.
Installed DiskCryptor, rebooted - Boom!

I wanted to test DiskCryptor in a VM before trying it on a real machine, so I am not sure if I should go that way.

Just an idea (which I have not tested yet), I use dynamically allocated disk so maybe that is the problem. If I have time I will try it with a fixed disk size and post my results here.
If you could test this earlier than me, please also post here.

Kind regards

PCFreak

Re: DiskCryptor on Windows 8 guest causes Guru Meditation

Posted: 15. May 2015, 15:04
by PCFreak
Hi,

I retried with a fixed disk, still no luck. It looks, that it does not work with VirtualBox at the moment.

I use VirtualBox 4.3.28 r100309 on Windows 8.1 enterprise 64bit. The virtual operating system is Windows 8.1 enterprise 64bit fresh installed without activation or additional updates. I used the latest DiskCryptor for Windows.

Cheers

PCFreak

Re: DiskCryptor on Windows 8 guest causes Guru Meditation

Posted: 15. May 2015, 15:07
by mpack
PCFreak wrote:I retried with a fixed disk, still no luck.
:?: I'm curious.... What difference did you think that might make?

To be clear, the only difference between a "fixed VDI" and a "dynamic VDI" is in choosing the moment when host disk space is allocated. There is no other difference on the host side, and the guest can't even tell the difference between VDI/VHD/VMDK, never mind act differently with different flavors of VDI.