virtualbox.org

Yes, going to 10.14 is not an option at this point. Unless someone magically points me in the right direction I'm going to have to take larger steps (likely exporting those machines to a larger box/HD so I don't need to save the .vdi/disks through the thunderbolt cable).

Unfortunately, heading back to 5.2.18 VirtualBox continues to have this panic. I booted into Recovery so I could get the kernel backtrace symbolicated. Full one is attached, but here's the relevant top chunk. Does anyone have any suggestions at all? Seriously I'd take anything. *** Panic Report *** ...

No dice - kernel panic again, and the last loaded/unloaded kexts are STILL the "com.apple.filesystems.msdosfs": last loaded kext at 245299630143: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f9cfcf000, size 69632) last unloaded kext at 306028564078: com.apple.filesystems.msdosfs 1.10 ...

Yeah, great question @socratis - downgrading will definitely be my next step if this removal of msdosfs.kext doesn't make it stable. So far, so good (86 min). Definitely updating here tomorrow morning. Thanks for fixing my link too.

Whelp. Clean OSX High Sierra boxes also appear to have /System/Library/Extensions/msdosfs.kext too. So - trying out the full Command-R reboot into recovery, Terminal, "csrutil disable", reboot, move msdosfs.kext somewhere else (as a backup), reboot again with Command-R, "csrutil enabl...

Hey @pietpatat - was your system upgraded to High Sierra 10.13 from 10.12? My system certainly was, and upon reading this link, I'm wondering if the plethora of kernel panics out there in the wild that show com.apple.filesystems.msdosfs are due to the fact that this kext was there before and is thus...

I'm also seeing Kernel panics and need to sort it out. Not sure if it's a regression, as I did update to 5.2.20 r125813, but believe I was seeing it earlier (think I was at 5.2.16). * Host is OSX 10.13.6, has 16 GB RAM * Running 3 separate Ubuntu 16.04 instances, each with 4GB RAM * VM disk location...