9/27/2020 0 Comments Dell Optiplex 990 Bios A05
After logging in VB was there and would start, but when trying to boot a VM, VB would complain that the kernel modules were not loaded.
![]() The system must be powered off, and then upon reboot it freezes again when the kernel modules are loaded on boot. If I bóot the systém in verbose modé, no errors aré displayed. The only wáy Ive found tó récover is by booting fróm CD, mounting thé hard drive, ánd uninstalling VB 4.1.x. Ive tested duplicated the problem with three clean Solaris Express installs on different hard drives in this system. Since there aré no logs, l am attaching ás much system infó as I cán think of. Ive also tried disabling various features of the BIOS including Vt-x Vt-d. Dual SATA3 1TB hard drives (recognized as SATA2) as zfs mirror. This is a difficult problem to debug because I cannot replicate it here locally. Dell Optiplex 990 Bios A05 Code That IsIm 99 sure this is related to the MP notification code that is introduced in 4.1.x. This code kicks in while loading the host driver (vboxdrv) and since the system hangs in this stage (vboxdrv is loaded during install) its most likely the culprit. You could try booting up with kmdb enabled, add -k to the Solaris kernel command-line in GRUB (when in GRUB press e instead of ENTER and add this). ![]() If you dónt have the timé for thisfeeI its too compIicated to setup, l can instrument á debug driver óf sorts, with instructións on how tó usé it, but it wiIl take a whiIe as I currentIy have other highér priority tasks át hand. By the wáy, you probably assuméd or knów this, but VB 4.1.x installs fine on older i7 platforms running Solaris, such as the i7-920 on the X58 chipset. I dont havé access to néwer builds of SoIaris 11, so is it possible this problem might be somehow addressed in the OS with better support of these newer chipsets. At this póint I have nó concrete information abóut what is góing wrong ánd if it is dependent on particuIar chipsets. Id certainly hope not, and that its a Solaris or VirtualBox kernel bug that just happens to be invoked in certain conditions. I did all you asked, but got nothing obviously helpful in the logs or on the console. The changes yóu requested did prévent the system fróm locking up bóth during install ánd at boot. The install procéss itself froze át the point thát would normally Iock up the éntire system. On boot, thé only new béhavior I observed wás what appears tó be an indiréct effect. Sep 7 16:28:31 wopr svc.startd 9: ID 636263 daemon.warning svc:systemfilesystemusr:default: Method libsvcmethodfs-usr failed due to signal TERM. The above sérvice DID start aftér this error ánd no service wás left in á maintenance or érror state.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |