wqiu wrote:I have a 6-core (12 threads) CPU, so allocating 6 "CPU" to VM is still well within the green zone.
No, it's not, because VirtualBox cares about cores only, not threads. And if you allocate one core to VirtualBox, the host loses one core (and two threads). So, no, 6-cores is the limit and it's not recommended at all.
I can't believe I missed that detail when I first looked at the log!
That would have been my #1 recommendation.
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.
That's why. You have 6 cores (that's where the green stops) and 12 threads (logical processors).
00:00:01.268856 Full Name: "Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz"
Take a look at what Intel has to say about your i7-8850H CPU. Make sure to click on the "?" next to the "# of Cores" and "# of Threads" to see what I'm talking about...
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.
I understand that I have 6 cores, 12 threads on my host.
I guess the confusion is, if I allocate 1 "CPU" for the VM, I loose 1 core on the host, why would Virtualbox even display 12 CPUs in the setting?
My understanding is that, when Virtualbox allocating "CPU"s, it counts 1thread as 1"CPU". To prove that, I allocated 4 "CPU"s for the Win10 VM. After I launched the VM,
within Win10 resource monitor, I see 4 threads CPU0-CPU3, so that's 2-cores (4 threads)
but on my Windows desktop, I have one 4-core (8 threads)CPU, and in the resource monitor, I can see 4-cores (8 CPUs CPU0-CPU7)
Attachments
cpu.jpg (72.82 KiB) Viewed 5102 times
Screen Shot 2018-08-08 at 9.50.55 AM.png (38.41 KiB) Viewed 5103 times
wqiu wrote:
I guess the confusion is, if I allocate 1 "CPU" for the VM, I loose 1 core on the host, why would Virtualbox even display 12 CPUs in the setting?
You are offered up to 12 vCPUs because the host OS is reporting that 12 CPUs are available. However VirtualBox has analyzed the CPU and believes there are only actually 6 cores (hence the red bar), but it will not prevent you from overriding what it thinks, and treating all 12 CPUs as cores.
It is up to you to understand your tools. You know that you only have 6 cores. You know that your host needs a core, or preferably 2. Therefore you also know that you should not allocate more than 4 cores to any VM.
For people who are confused by this I have a basic question I always ask: if threads are as good as cores, why doesn't your CPU have 1 core and 12 threads? That would be much cheaper in silicon terms, so if they are equivalent then that would be the obvious way to go. If you know they are not equivalent then where's the beef?
regardless the number of cores argument, the VB crash is still there. I just experienced another one ( note the number of cores is 4)
Attached is the crash report generated by macOS, and the box.log
Unfortunately the new log is incomplete. However as before there is no sign in the log that the VM crashed, so it looks like some kind of code running on your host is what crashed. Whether that code is part of VirtualBox or something else, I have no idea.
Perhaps it's time to raise a BugTracker ticket, attaching the latest log file and OS X crash report.
At the same Terminal window, and with the VM completely shut down, enter the following command:
VBoxBugReport "<VMname>"
where "<VMname>" is the actual name of the VM that just crashed VirtualBox. This will generate a "YYYY-MM-DD-hh-mm-ss-bugreport.tgz" file in the current directory (most probably your home directory). Attach that file in your response. See the "Upload attachment" tab below the reply form.
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.
Nothing. I get nothing out of the ordinary. Just one last piece of information, to see what apps you've got installed on your OSX. Post the output of:
ls -ale@ /Applications/
ls -ale@ /Applications/Utilities/
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.
From the list of your installed applications, the following are not from Apple:
drwxr-xr-x 3 wqiu staff 96 18 May 2017 Beyond Compare-2.app
drwxrwxr-x@ 3 wqiu admin 96 7 Aug 16:45 Google Chrome.app
drwxr-xr-x 30 wqiu admin 960 6 Aug 09:16 MATLAB_R2018a.app
drwxrwxr-x 3 root wheel 96 3 Aug 08:59 Microsoft Excel.app
drwxrwxr-x 3 root wheel 96 3 Aug 08:59 Microsoft OneNote.app
drwxrwxr-x 3 root wheel 96 3 Aug 08:59 Microsoft Outlook.app
drwxrwxr-x 3 root wheel 96 3 Aug 08:59 Microsoft PowerPoint.app
drwxrwxr-x 3 root wheel 96 3 Aug 08:59 Microsoft Word.app
drwxr-xr-x 3 root wheel 96 3 Aug 08:59 OneDrive.app
drwxr-xr-x 3 root wheel 96 31 Jul 23:09 Skype for Business.app
drwxr-xr-x@ 3 wqiu admin 96 31 Jul 17:33 Skype.app
drwxrwxr-x 3 root wheel 96 2 Aug 14:04 TextWrangler.app
drwxr-xr-x 3 root wheel 96 31 Jul 21:40 The Unarchiver.app
drwxr-xr-x 3 root admin 96 5 Aug 10:41 VirtualBox.app
drwxr-xr-x 3 root wheel 96 31 Jul 23:35 WeChat.app
drwxrwxr-x 3 wqiu admin 96 15 Jul 19:50 zoom.us.app
From these, I'm a little skeptical about "zoom.us.app", mainly because I discovered that they create their own audio device. I can tell you one thing; it was the first app that managed to freeze my OSX 10.11 VM.
Also, I'm not so confident about the "WeChat.app" one either...
Can you do me a favor and uninstall them temporarily, then reboot your OSX and try again?
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.
OK, great. Let us know if you manage to find the solution then. Good luck!
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.