I have a CentOS VM that I have been using regularly for years. I was forced to switch to a new Macbook and my VM will not start on it. Both Macbooks are on Mojave 10.14.6. The old Macbook is a Mid 2015 model and the new Macbook is 2018. The VM fails at the same point in the boot sequence every time. Logs are attached. Ay help is greatly appreciated.
I initially saw this issue using VirtualBox version 6.0.14. I uninstalled and tried 6.0.0 to match the older Macbook and the result is the same.
VM won't start on new Macbook Pro
VM won't start on new Macbook Pro
- Attachments
-
- VBox.log.zip
- (83.32 KiB) Downloaded 12 times
-
- VBox.png.zip
- (18.42 KiB) Downloaded 12 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: VM won't start on new Macbook Pro
1) The HD controller points to an imported VM.00:00:00.864694 [/Devices/lsilogicscsi/0/LUN#0/AttachedDriver/Config/] (level 6) 00:00:00.864695 BlockCache <integer> = 0x0000000000000001 (1) 00:00:00.864695 Format <string> = "VMDK" (cb=5) 00:00:00.864696 Mountable <integer> = 0x0000000000000000 (0) 00:00:00.864696 Path <string> = "/Users/mparham/VirtualBox VMs/ eBay_S1PEER1/S1PEER1/IT-vPAS5.4RC4-disk1.vmdk" (cb=76)
2) There is the VM name "S1PEER1", that doesn't match the default location, it was moved, plus the VDI VMDK name don't quite match, some magic dust has been applied. Can you explain what's going on here?
And that is your real crash, your guest did something really nasty in there.00:00:27.844655 !! VCPU2: Guru Meditation -5300 (VERR_IEM_INSTR_NOT_IMPLEMENTED)
Do you know what this specific guest was doing? I can't tell how the guest was built or what it was running at the time...
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.
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.