From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51488) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eECOS-0004M8-O2 for guix-patches@gnu.org; Mon, 13 Nov 2017 05:55:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eECON-0003Ju-5w for guix-patches@gnu.org; Mon, 13 Nov 2017 05:55:08 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57305) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eECON-0003Jo-2I for guix-patches@gnu.org; Mon, 13 Nov 2017 05:55:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eECOM-0008In-Jy for guix-patches@gnu.org; Mon, 13 Nov 2017 05:55:02 -0500 Subject: [bug#29281] [PATCH] system: vm: Use linux-libre for system-disk-image. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20171113072236.13270-1-m.othacehe@gmail.com> <87o9o6bjsw.fsf@gnu.org> <87lgjazex2.fsf@gmail.com> <87vaiev5mu.fsf@gnu.org> Date: Mon, 13 Nov 2017 11:54:30 +0100 In-Reply-To: (Mathieu Othacehe's message of "Mon, 13 Nov 2017 11:47:19 +0100") Message-ID: <8760aev47t.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: Mathieu Othacehe Cc: 29281@debbugs.gnu.org Mathieu Othacehe skribis: >> >> 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 :( So the kernel you built doesn=E2=80=99t boot at all in =E2=80=9Cqemu-system= -arm -M virt=E2=80=9D? > 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) ... OK. > However, I don't think qemu virt machine will boot with every specific arm > kernel a user might end up using > on his target. I see. > 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? >> > > That would be an option for the initrd, but the kernel problem above > remains :) Right. I can=E2=80=99t think of a good solution right now. Perhaps we could simply hard-code ARM-specific code? (operating-system (inherit os) (kernel (if targeting-arm? linux-libre-arm (operating-system-kernel os))) ;; =E2=80=A6 ) In practice =E2=80=98targeting-arm?=E2=80=99 could be checking (%current-sy= stem) and (%current-target-system), which is not entirely correct but good enough, or, better yet, use that =E2=80=98let-system=E2=80=99 construct I sent you = recently to determine the actual target system. Thoughts? Ludo=E2=80=99.