From: Valery Ushakov <u...@stderr.spb.ru> Subject: Re: i386 on VirturalBox boot failed Date: Wed, 30 Nov 2016 17:42:43 +0300
>> > On Wed, Nov 30, 2016 at 08:53:02 +0900, Jun Ebihara wrote: >> > > VirtualBox 5.0.30 on CentOS6.8: >> > > use nyftp iso image: >> > > NetBSD 7.99.42 GENERIC.201611131540Z ... boot fine. >> > > dmesg: >> > > https://github.com/ebijun/NetBSD/blob/master/dmesg/i386/VirtualBox >> > > NetBSD 7.99.42 GENERIC.201611271450Z: ... stucked. >> > > NetBSD 7.99.43 GENERIC.201611291610Z: ... stucked. >> > > kernel: supervisor trap page fault, code=0 >> > > uvm_fault(0xc12bc400,0xc153000,1) -> 0xe >> > > fatal page fault in supervisor mode >> > > trap type 6 code 0 eip c0153468 cs 8 eflags 10282 cr2 c153300 ilevel 8 >> > > esp c0f41cfd >> > > curlwp 0xc1228720 pid 0 lid 1 lowest kstack 0xc14c92c0 >> > > kernel: supervisor trap page fault, code=0 >> > > : >> > > >> > > and stucked. > I guess that change exposed an old bug. Previously, the lapic page > was statically pre-allocated and so it was always there. Even if > lapic wasn't initialized, we could still read (garbage) from that > page. Now the page is allocated dynamically, so when we try to read > uninitialized data, we get a fault. > A quick workaround for now is to check "Enable I/O APIC" in VM's > preferences in the System settings. Thanx for your great anlyze and advice! with "Enable I/O APIC" option,VirtualBox works well again and now I back to my living atomosphre with i386 pkgsrc. https://github.com/ebijun/NetBSD/blob/master/dmesg/i386/VirtualBox -- Jun Ebihara
