Date: Mon, 08 Dec 2014 23:48:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193672] FreeBSD UEFI boot panics with VirtualBox UEFI loader Message-ID: <bug-193672-8-nXe0DfMSoH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193672-8@https.bugs.freebsd.org/bugzilla/> References: <bug-193672-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193672 lidl@pix.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lidl@pix.net --- Comment #5 from lidl@pix.net --- I just tried to get this to work today. Here are my notes. I prepared a fresh image this morning (Last Changed Rev: 275104), and attempted to boot it on VirtualBox 4.3.20 r96996 (on a Mac), with the VirtualBox extensions installed. It does work, if you give enough memory to the client VM. With 3072MB of memory for the virtualbox instance, FreeBSD panics before the kernel's autoconfiguration takes place. With 3073MB..3090MB of memory, the FreeBSD boot hangs right after it prints out the "EFI framebuffer information:" table, but before any of the autoconfiguration happens. With 3091MB (or more) of memory, the FreeBSD boot completes successfully. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193672-8-nXe0DfMSoH>