Windows 10 guest on raw disk vmdk on macOS Host 10.13.1 accesses invalid memory when over 2GB ram alloc'ed

[Marco Antonio Mauro]

The VM crashes a few seconds after bootup with a -1618 Guru Meditation preceded by a -1639 error.

Logs are attached.

Log 1 is an ok boot with 2GB ram to guest. Log 2 and 3 with screenshot are crashes with 3GB and more ram to guest.

[Marco Antonio Mauro]

Log 1

[Marco Antonio Mauro]

Log 2

[Marco Antonio Mauro]

Log 2 Screenshot

[Marco Antonio Mauro]

Log 3

[Marco Antonio Mauro]

Log 3 Screenshot

[Socratis]

Just FYI, I too have a Win10-x64 guest running as a rawdisk guest VM, as well as boot my MBPr from. It's an external USB3 device, but it shouldn't matter, the logic is exactly the same. Mine doesn't crash.

A major difference that I have is that my VM is set to boot using EFI, not the traditional BIOS. It *does* need EFI to boot in real life after all. Another small difference is that I don't use VirtIO and I have assigned 2 vCPUs. Oh, and I have USB3 enabled.

I usually have it running with 3 GB assigned, but just for kicks I assigned 4 GB to the VM and run it. No problemo.

EDIT: I forgot to mention that the host is a MBPr 15", mid-2015 (MacBookPro11,5). Running OSX 10.11.6.

[Marco Antonio Mauro]

Sorry for the late reply, I didn't get the notification.

My Windows installation is not EFI, it's an older E2011 15" MBP with macOS 10.13.2 (now .3) and W10 in Boot Camp. About the other factors I have tried toggling them also, but there was no difference.

I have tried with the latest version and it exposes the same defect. The EFI *could* be a fix but not for me; I think either the e820 memory map in the VB bios is wrong or an indirection table somewhere went FUBAR in some way.

It is sad as it could replace Parallels this way.

[aeichner]

Please reopen if still an issue with a recent VirtualBox release.