Comment 2 for bug 1535618

Really, the only repro instruction we have are to "fire up a small VM" ?

For starters - what's "small" mean? What CPU, what OS (I'll assume Linux), what distro, what kernel, what modules ...
And what SBCL revision, what build features, what heap size?
What's in SBCL's sysinit file? Were the sources pristine?
And since this is a VM - what hypervisor/virtualizer/simulator/emulator?
What physical CPU is that running on? What options were given to the VM?

Were all that information supplied, it might be possible for a developer to confirm the problem.
Even then it's likely to just say this is infeasible.