After looking the logs in Console.app for Crash reports, where I found [code]Exception Type: EXC_CRASH (Code Signature Invalid)[/code], yet all seemed fine on Systems Preferences settings.
It seems that: [code]sudo kextcache --clear-staging[/code] did the trick, now my VM at least starts and Windows is trying to repair itself. My Ubuntu is back at least. On Thu, 11 Jun 2020 at 22:06, Alan <alanwil...@gmail.com> wrote: > Hi there, > > A couple of days ago all was working fine on my macOS 10.15.5 with > VirtualBox 6.0.20. > > I have Windows10 and Ubuntu. Today I needed Windows and when it started I > got the Windows "blue" screen saying that some critical system files were > not found and it tried to repair itself, for no avail. > > Then I tried Ubuntu, which simply didn't start and its status turned to > "Aborted" > > Making a long story short. I did a clean install of VirtualBox 6.1.10, > used new and backed up VDI files for Windows and Linux. Created a new VM > re-using my VDI disks and tested, trying to look at the logs. > > It's simply getting aborted whatever I try. I have no idea of what's going > on. Looking at my log at ~/VirtualBox VMs/Ubuntu_old/Logs/VBox.log, the > only things I found suspicious were: > > ... > 00:00:01.897119 Firmware type: failed - VERR_NOT_SUPPORTED > ... > # the end of my log > 00:00:02.211154 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 > LCHS=1024/255/63 0x0000000001000000 sectors > 00:00:02.212571 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0) > 00:00:02.229405 Display::i_handleDisplayResize: uScreenId=0 > pvVRAM=0000000116cf5000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0 > 00:00:02.692486 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest > size-hint for screen 0 to 800x600 > 00:00:02.700394 GUI: 2D video acceleration is disabled > 00:00:02.700470 GUI: HID LEDs sync is enabled > 00:00:02.738224 GUI: > UIMachineLogicNormal::sltCheckForRequestedVisualStateType: > Requested-state=0, Machine-state=5 > 00:00:04.694171 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) > 00:00:04.695038 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231 > 00:00:04.695713 VMMDev: Guest Log: BIOS: Boot from Floppy 0 failed > 00:00:04.696378 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023 > 00:00:04.697268 VMMDev: Guest Log: BIOS: CDROM boot failure code : 0003 > 00:00:04.697644 VMMDev: Guest Log: BIOS: Boot from CD-ROM failed > 00:00:04.698085 VMMDev: Guest Log: BIOS: Boot : bseqnr=3, bootseq=0002 > 00:00:04.698938 VMMDev: Guest Log: BIOS: Booting from Hard Disk... > 00:00:04.749144 Display::i_handleDisplayResize: uScreenId=0 > pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0 > 00:00:05.353478 Display::i_handleDisplayResize: uScreenId=0 > pvVRAM=0000000116e21000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0 > > I can run Ubuntu memory test from the Grub option and start the VM in > headless mode. The status shows "running" and that's all. > > I Continued with my investigations, yet with problems. > > I've tried to create a fresh Linux, using lubuntu-20.04-desktop-amd64.iso. > Following all the basic and default steps, when it boots from the iso, > Lubuntu asks me the Language to use and then goes to boot the system to, > immediately, fail, showing the Aborted status. > > I can send the logs from, if asked: > ~/VirtualBox\ VMs/Lubuntu_fresh/Logs/VBox.log > ~/Library/VirtualBox/VBoxSVC.log > > Further on my investigations, I've been reading other posts like: > > 1) VirtualBox crashes after upgrading to macOS Catalina (#18990) > https://forums.virtualbox.org/viewtopic.php?f=8&t=95041 > > 2) Virtualbox crashes when selecting another window. > https://forums.virtualbox.org/viewtopic.php?f=39&t=93419 > > I've tried almost everything I saw there, I've tried even with another > fresh user account on my mac, tried 6.0.22 (as it was working a few days > ago), tried with and without System permissions, tried headless, > detachable. All with a fresh Lubuntu iso. I even tried VB v. 5.2.42, which > does start but then soon is plagued with errors on terminal (kernel panic) > or frozen. > > The best I got so far was, with 5.2.42, that I could get the Lunbuntu > installation screen, navigate but then it froze during installation. Now > with 6.0 or 6.1 I don't even get to pass the selection of starting > Lunbuntu. It's really annoying as it is not deterministic, it happens in > different stages. > > In all cases I am using default options to create the Lunbutu. > > Any help would be very appreciated. > > Thanks in advance, > > Alan > -- Alan Silva 🚲🏊♂🏃♂🇧🇷🇫🇷🇬🇧
_______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
