On Thu, 2017-01-19 at 14:10 +0100, Patrick Ohly wrote:
> In a nutshell, enabling "qemuall" seems to mean "this *will* run under
> runqemu", and not "this *might* run under runqemu".
>
> I'll change the meta-intel patch so that it does something useful for
> running under qemu without the qemuall
On Mon, 2017-01-16 at 12:05 +0100, Patrick Ohly wrote:
> I was wondering where virtio in Poky came from and thus had a second
> look. It's from OE-core's
> meta/recipes-kernel/linux/linux-yocto_4.8.bb:
> KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
>
> It's a bit surprising that the "qemuall"
On Mon, 2017-01-16 at 09:45 +0100, Patrick Ohly wrote:
> On Fri, 2017-01-13 at 16:11 -0800, Cal Sullivan wrote:
> > Our kernel's .config has the following, will this cause any issues?
> >
> > #
> > # Virtio drivers
> > #
> > # CONFIG_VIRTIO_PCI is not set
> > # CONFIG_VIRTIO_MMIO is not set
>
>
On 01/12/2017 06:19 AM, Patrick Ohly wrote:
Although the machines definitions in meta-intel are meant to target
real hardware, begin able to start the resulting images under qemu is
nevertheless useful for testing.
Doing that via runqemu depends on a per-image runqemu.conf that
describes how
Although the machines definitions in meta-intel are meant to target
real hardware, begin able to start the resulting images under qemu is
nevertheless useful for testing.
Doing that via runqemu depends on a per-image runqemu.conf that
describes how to run qemu for the image. Ineriting
