On (Thu) 14 Apr 2016 [12:48:59], Paul Bolle wrote:
> Ever since v2.6.36 there's a conflict between OLPC support and Lguest
> guest support: a kernel image can't both support booting OLPC x86
> hardware and booting as an Lguest guest. Booting a kernel image that
> tries to do both as an Lguest guest will fail with
>     lguest: Reinjecting trap 13 for fault at 0x1000062: Invalid argument
> 
> This means that people wanting to boot an Lguest guest on 32 bits x86
> needed to build their own kernel image without OLPC support since, it
> seems, Fedora 15. So let's stop pretending to support being an Lguest
> guest. People wanting to have that will now not only have to disable
> CONFIG_OLPC but also enable CONFIG_LGUEST_GUEST.
> 
> (A second order effect is that both CONFIG_VIRTIO and
> CONFIG_VIRTIO_CONSOLE will change from 'y' to 'm' in our builds.
> Assuming a sane build system no one should notice. We'll see.)

CONFIG_VIRTIO_CONSOLE was =y because anaconda couldn't load the module
at startup (but I think it's been fixed since a while now).  It
doesn't make sense to keep this at =y, so even explicitly marking both
VIRTIO and VIRTIO_CONSOLE to =m is advised.

                Amit
-- 
http://log.amitshah.net/
_______________________________________________
kernel mailing list
[email protected]
http://lists.fedoraproject.org/admin/lists/[email protected]

Reply via email to