Opened 6 years ago
Last modified 6 years ago
#17442 new defect
Mac OS High Sierra VM crash
| Reported by: | luca.b | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Mac OS X |
Description
The VM keeps crashing when I run the Daedalus Wallet application (https://daedaluswallet.io/). It does not happen immediately but after a few minutes. I am running VirtualBox on a Mac OS High Sierra fully patched. The very same version is running on the VM.
Attachments (3)
Change History (12)
by , 6 years ago
comment:1 by , 6 years ago
The VM that you have is not your typical OSX guest one. Did you change some things? What and more importantly, why?
I know for example that you've changed the network card type, and it's funny that the "Connecting to network.." is the last thing that you see before the crash.
Also a disabled sound card, and an encrypted VDI, who's DEK is missing BTW. Can you explain the situation a little bit better?
comment:2 by , 6 years ago
Actually I have made some changes, guessing the problem was associated with the network configuration. The application that causes the crash is very network intensive. The original build/configuration comes from this site: http://tobiwashere.de/2017/10/virtualbox-how-to-create-a-macos-high-sierra-vm-to-run-on-a-mac-host-system/ Any changes I applied to that configuration are just tests to identify the cause of the problem.
comment:3 by , 6 years ago
Based on what you said in your previous message I created an empty VM for High Sierra and copied the default settings to my VM. Now it looks fine and the application does not crash the system any longer. Unfortunately I cannot say which parameter was causing the issue but I have attached the new VM log in case you would like to find out. Thanks for the support.
comment:4 by , 6 years ago
Replying to luca.b:
The original build/configuration comes from this site...
Oh yeah? So you din't like my instructions? :D
(I'm only joking, they're exactly the same, independently home-brewed)
I was editing the following when your post came in... Since it's generic advice, I'll leave it.
When your "(anything)" crashes, you provide a log from the crash. There's absolutely no point in providing a "generic" log, it doesn't contain information about the crash, and it may actually be misleading. So, please repeat the process, but with the actual log from the actual crash this time...
PS. The network card that you chose cannot be seen from an OSX guest. Only the "IntelPRO-MT Server" has built-in drivers.
Now, it seems that the issue got fixed. I'll take a look at your logs and see what's different, although you should know what you've changed in the "recipe".
comment:5 by , 6 years ago
Unfortunately I cannot say which parameter was causing the issue
Nothing more than what I told you to change:
- You enabled the Audio.
- You changed the NIC from "IntelPRO-MT Desktop" to "IntelPRO-MT Server".
That's all. I don't know why any of these would cause a Guru Meditation (GM), but I suspect it might be the NIC.
So it may be wise to leave the ticket open until we check what's going on here. There shouldn't be a need for a GM in the case that an unknown NIC is present. Or the audio is not...
comment:6 by , 6 years ago
I do not think it is the NIC because initially it was set to Server. I then changed to Desktop to see if that specific setting was causing the issue.
VM log file