[From nobody Wed Nov  4 04:07:06 2026
Received: (at submit) by bugs.debian.org; 8 May 2024 15:59:42 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
 (2021-04-09) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-12.0 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,HAS_PACKAGE,SPF_HELO_NONE,SPF_NONE autolearn=ham
 autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 17; hammy, 91; neutral, 43; spammy, 0.
 spammytokens: hammytokens:0.000-+--H*F:U*helmut,
 0.000-+--H*F:D*subdivi.de, 0.000-+--H*RU:sk:helmut@,
 0.000-+--H*rp:U*helmut, 0.000-+--H*rp:D*subdivi.de
Return-path: <helmut@subdivi.de>
Received: from isilmar-4.linta.de ([136.243.71.142]:37042)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from <helmut@subdivi.de>) id 1s4jhn-002b8J-0z
 for submit@bugs.debian.org; Wed, 08 May 2024 15:59:41 +0000
Received: from isilmar-4.linta.de (isilmar.linta [10.0.0.1])
 by isilmar-4.linta.de (Postfix) with ESMTP id 58E0D200056
 for <submit@bugs.debian.org>; Wed,  8 May 2024 15:59:37 +0000 (UTC)
Date: Wed, 8 May 2024 17:59:08 +0200
From: Helmut Grohne <helmut@subdivi.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: debos: unhelpful error message "Modules path couldn't be determined"
Message-ID: <20240508155908.GA2893757@subdivi.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 13.0.1
Delivered-To: submit@bugs.debian.org

Package: debos
Version: 1.1.1-2.1+b1

Hi,

I was trying to use debos and all that it told me was:

| Modules path couldn't be determined

This is not helpful. After digging into code I eventually figured that
when it says "modules" it measn "Linux kernel modules". This is not
evident from the context. Moreoever, it eventually became clear that the
module it was missing was 9pnet_virtio. If that name had been included
in the error message, it would have been immediately obvious to me that
the cause was using a -cloud kernel as -cloud kernels lack 9p
functionality (see #955232). While debos recommends a non-cloud kernel
and the non-cloud kernel even got installed, the additional presence of
a -cloud kernel image meant that grub would prefer booting that.

I hope this is sufficient reason to improve the error message. Thanks
for considering.

Helmut
]