From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50172) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eECHh-0002nD-2E for guix-patches@gnu.org; Mon, 13 Nov 2017 05:48:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eECHa-000055-JH for guix-patches@gnu.org; Mon, 13 Nov 2017 05:48:09 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57299) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eECHa-00004z-Fk for guix-patches@gnu.org; Mon, 13 Nov 2017 05:48:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eECHa-00089M-6W for guix-patches@gnu.org; Mon, 13 Nov 2017 05:48:02 -0500 Subject: [bug#29281] [PATCH] system: vm: Use linux-libre for system-disk-image. Resent-Message-ID: MIME-Version: 1.0 In-Reply-To: <87vaiev5mu.fsf@gnu.org> References: <20171113072236.13270-1-m.othacehe@gmail.com> <87o9o6bjsw.fsf@gnu.org> <87lgjazex2.fsf@gmail.com> <87vaiev5mu.fsf@gnu.org> From: Mathieu Othacehe Date: Mon, 13 Nov 2017 11:47:19 +0100 Message-ID: Content-Type: multipart/alternative; boundary="001a1143e546a7d037055ddafe3d" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 29281@debbugs.gnu.org --001a1143e546a7d037055ddafe3d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > Oh, why is that? You mean qemu-system-arm running natively on the BBB, > right? > Yes, when running qemu-system-arm you have only a limited set of available machines (qemu-system-arm -M help). BBB isn't one of them, but as there are only about 50 emulable machines, it will be the case for many other boards :( In a future patch, I'll adapt "load-in-linux-vm" to use "-M virt" for qemu-system-arm because contrary to most boards, it works well with linux-libre, allows up to 8 CPU, virtio (see https://wiki.qemu.org/Documentation/Platforms/ARM) ... However, I don't think qemu virt machine will boot with every specific arm kernel a user might end up using on his target. Perhaps we should change =E2=80=98system-disk-image=E2=80=99 to use a more = minimalistic > initrd since all it needs is those virtio* drivers? > That would be an option for the initrd, but the kernel problem above remains :) Thanks ! 2017-11-13 11:23 GMT+01:00 Ludovic Court=C3=A8s : > Hello, > > Mathieu Othacehe skribis: > > >> What was the use case and rationale for you? > > > > The problematic use case was to try to produce a GuixSD arm installer > > for beaglebone black. The kernel linux-libre-arm-omap2plus I'm planning > > to use can't be used in qemu. > > Oh, why is that? You mean qemu-system-arm running natively on the BBB, > right? > > > Plus, I'd like to use a raw-initrd because linux-libre-arm-omap2plus is > > quite a light kernel configuration. As system-disk-image asks for > > base-initrd, the required modules won't be find during image > > construction with omap kernel. > > Perhaps we should change =E2=80=98system-disk-image=E2=80=99 to use a mor= e minimalistic > initrd since all it needs is those virtio* drivers? > > Thanks for explaining! > > Ludo=E2=80=99. > --001a1143e546a7d037055ddafe3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Oh, why is that?=C2=A0 You mean qemu-system-arm running na= tively on the BBB,
right?

Yes, when running qemu-system-arm you have= only a limited set of available machines (qemu-system-arm -M help).
BBB isn't one of them, but as there are only about 50 emulable = machines, it will be the case for many other boards :(

In= a future patch, I'll adapt "load-in-linux-vm" to use "-= M virt" for qemu-system-arm because contrary to most boards,
=
it works well with linux-libre, allows up to 8 CPU, virtio (see h= ttps://wiki.qemu.org/Documentation/Platforms/ARM) ...

However, I don't think qemu virt machine will boot with every spe= cific arm kernel a user might end up using
on his target.
=

= Perhaps we should change =E2=80=98system-disk-image=E2=80=99 to use = a more minimalistic
initrd since all it needs is those virtio* drivers?
That would be an option for the initrd, but the kernel = problem above remains :)

Thanks !

2017-11-13 11:23 GMT+01:00 = Ludovic Court=C3=A8s <ludo@gnu.org>:
Hello,

Mathieu Othacehe <m.othacehe@gma= il.com> skribis:

>> What was the use case and rationale for you?
>
> The problematic use case was to try to produce a GuixSD arm installer<= br> > for beaglebone black. The kernel linux-libre-arm-omap2plus I'm pla= nning
> to use can't be used in qemu.

Oh, why is that?=C2=A0 You mean qemu-system-arm running natively on = the BBB,
right?

> Plus, I'd like to use a raw-initrd because linux-libre-arm-omap2pl= us is
> quite a light kernel configuration. As system-disk-image asks for
> base-initrd, the required modules won't be find during image
> construction with omap kernel.

Perhaps we should change =E2=80=98system-disk-image=E2=80=99 to use = a more minimalistic
initrd since all it needs is those virtio* drivers?

Thanks for explaining!

Ludo=E2=80=99.

--001a1143e546a7d037055ddafe3d--