![]() ![]() It’s a roll of the dice based on that, but since I don’t have anything invested in CML as yet, I’ve got nothing to lose. Cisco’s documentation is a bit sparse, but the release notes for CML 2.1 say to not go to Big Sur.īut then in the 2.1.1 release notes, the supposed issue from CML 2.1 was fixed, although Cisco doesn’t say to charge ahead with a Big Sur upgrade. I am hoping to get Cisco Modeling Labs 2.1.1 fired up on this new machine, although I think there’s a good chance CML won’t work right on Big Sur. And I’ll take being able to run GNS3 labs without kernel panics as a big win. Big Sur is not a flawless experience for me yet, but I have hope it will become so as software makers have time to adjust to all of Apple’s changes. In order to continue to operate in this model, we’ve re-architected our hypervisor stack to leverage Apple’s native hypervisor APIs, allowing us to run VMs without any kernel extensions.Įven with minor caveats, I seem to be in a better place with macOS 11.1 Big Sur versus macOS 10.15.7 Catalina. For instance, Apple has been progressively deprecating 3rd party Kernel Extensions or “kexts” which Fusion needs to run VMs and containers. VMware in the Fusion Blog reports the following.īig Sur brings with it some really big visual changes, but also major changes under the hood. This isn’t entirely shocking, since Apple has re-architected the virtualization subsystem. ![]() No kernel panics since the move to Big Sur 11.1. Not only have they been running fine, but the system seems stable. All of my Linux VMs, including the GNS3 VM, were running fine. ![]() After that, VMs were usable for me, except for a Win10 VM with display problems. But I initially ran into slow VM performance until I disabled side channel mitigations per VM. I’m not sure how the experiences might differ between the two. ![]() I am using the paid, full version, and not the free Player. But aside from that, upgrade drama was otherwise minimal. There was the holding down of power buttons for several seconds, kicking cats, and yelling out of a window while shirtless, if I recall correctly. I usually take the Tour, but only if no one else is around to witness my shame as I allow myself to be indoctrinated by Uncle Tim.)Īs my iMac has a T2 security chip, I ran into a known issue where my valid password on an admin-equivalent account was not honored while trying to tweak System Preferences, forcing me to reset the SMC. And take the inevitable “Tour”, Apple’s release notes for normies. Etc.Įventually, you back to the familiar login prompt, type your password, wait for the Bluetooth keyboard to connect, delete whatever few characters made it through while the keyboard was waking up, re-type your password, close your eyes, sigh heavily, open your eyes, and behold the fresh UI Apple has decided is best for you. Read the lies about estimated time the progress bar tells you. I didn’t time it, but if you’re a Mac owner, you know the process. I followed the typical Apple upgrade process, and it took as long as these things usually do–perhaps an hour or so. All of them gave a (qualified) thumbs up to macOS 11, so I decided to take the plunge on my iMac Retina 5K, 27-inch, 2020–the last of the Intel iMacs. I’d finally had enough of the panics, so I did some crawling around vendor sites who make the the audio gear I rely on. So, I put off Big Sur, living with the Catalina kernel panics…until yesterday. Major version upgrades to macOS are usually traumatic in the early days, especially for folks like me that do a lot of audio recording and processing. Pretty annoying if you’re in the middle of a larger lab and need to let it go overnight so you can, I dunno, sleep.Ĭatalina’s successor Big Sur aka macOS 11 has been out for some time, but I’d been putting the upgrade off…because I know better. That meant I’d been unable to get labs setup and leave them running for more than a few hours without the system blowing up. Supposedly, a supplemental update to macOS 10.15.6 fixed this issue, but not for me. Typically, I’d be running the GNS3 VM, and this would cause the system to hard crash after a few hours. On macOS Catalina since 10.15.6, I’ve been fighting kernel panics when running VMs in VMware Fusion. ![]()
0 Comments
Leave a Reply. |