Maybe the hardware the kernel uses to warn is reconfigured (Probing EDD, which is display info) but in the middle it panics because it can't write to the hardware.
Not a kernel developer, just a generic thought. On Wed, May 24, 2017 at 9:16 AM, Hans de Goede <[email protected]> wrote: > Hi, > > I cannot get a Fedora 26 guest to boot with either distro-provided or > self-built 4.12-rc# kernels, the distro-provided 4.11 kernel works fine. > > After selecting a 4.12# kernel in the grub menu the vm shows an empty text > screen with a cursor in the top left corner and then just hangs. > > Anyone know how to fix this ? This is with VirtualBox 5.1.22 on a Fedora > host. > > Regards, > > Hans > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev >
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
