VirtualBox: 5.2.18 r124319 (Qt5.6.3)
O/S: Mac OS X El Capitan 10.11.6 (15G22010)
Guest O/S: CentOS 7.5
I've been using VirtualBox for a number of years and this is the first time I have experienced a Guru Meditation. I note from the Changelog that a fix was applied to VirtualBox 5.1.22 however the issue has reoccurred in the environment as stated above. As reported in the forum, disabling "Nested Paging" is a temporary workaround
You are assigning memory to your guest, that you do not have available. Close some applications on the host, or reduce the amount of RAM assigned to the guest. At the same time, your VRAM is way too low, you should increase it to 32 or 64 MB at least.
What was the guest doing at the time of the crash? And more importantly, is it repeatable?
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.
Yes, the issue is reproducible even after rebooting my Mac. I have reduced RamSize to 512MB and increased the VRamSize to 64MB as you suggest. The problem still persists.
You didn't answer a very important question: what was the guest doing at the time of the crash? Can I try it here?
Because I do have a MBP and a CentOS 7.5 VM ready to test...
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.
Apologies for missing your question. The guest O/S was booting to either multiuser mode or into recovery mode. The crash occurred just before the login prompt. See attached screenshot.
Attachments
Screen Shot 2018-09-18 at 13.30.32.png (100.52 KiB) Viewed 4704 times
It doesn't make too much sense, honestly. You can't have built this VM yourself, because you ... wouldn't be able to build it, you wouldn't be able to boot from the CD! Where did you get this "es400" VM from?
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, wait a minute... If you have nested paging disabled you do not get the crash?
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.
Hmm... I don't know how the VM was created, actually I don't know the options chosen for CentOS. What I do know is that a standard CentOS installation works with and without Nested Paging. Maybe you have the "Alternative Architecture Special Interest Group (AltArch SIG)"?
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.
The VM was created using VirtualBox defaults (with nested paging enabled) and O/S installed from an ISO with a modified kickstart file (not the RHEL7 supplied version).
rmansfield wrote:with a modified kickstart file (not the RHEL7 supplied version)
What's that? And is this thing something that you could divulge information about? If not to me, then to the developers?
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.
The kickstart is relative simple but basically install some specific package and kernel modules, enables/disables some services, configures custom partitions sizes and recompiles the kernel.
i'm happy to share the ISO with one of your developers.
OK, in that case you should head to the bug tracker and open a ticket. Even sharing it with me wouldn't help you, because the only thing I can do is to verify the crash or not.
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.