From: ludo@gnu.org (Ludovic Courtès)
To: Taylan Kammer <taylanbayirli@gmail.com>
Cc: 31887@debbugs.gnu.org
Subject: bug#31887: Modules missing to boot on VMWare
Date: Thu, 21 Jun 2018 22:52:03 +0200 [thread overview]
Message-ID: <87o9g36ex8.fsf@gnu.org> (raw)
In-Reply-To: <87in6c9f57.fsf@gmail.com> (Taylan Kammer's message of "Thu, 21 Jun 2018 20:19:00 +0200")
Taylan Kammer <taylanbayirli@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hello Taylan,
>>
>> Taylan Ulrich "Bayırlı/Kammer" <taylanbayirli@gmail.com> skribis:
>>
>>> Although we don't want to support non-free software, perhaps it would
>>> be nice to support booting Guix on VMWare without the user needing to
>>> do anything extra.
>>>
>>> While experimenting, I found out that if we just add the following
>>> three Linux modules to the standard initrd, Guix can boot on VMWare
>>> just fine: mptbase, mptscsih, mptspi
>>>
>>> mptspi depends on mptscsih, and both depend on mptbase, so if
>>> dependencies are handled automatically, declaring mptspi should be
>>> enough.
>>
>> Currently every module we add to the initrd is actually loaded, so we
>> have to think twice before adding more. In this case I’d rather punt.
>>
>> Danny and I started work a while back to load modules on demand à la
>> udev, so we could revisit that decision when this is implemented. Now,
>> if that only benefits VMWare, it’s low-priority for me.
>
> Understood and agreed. :-)
>
> Should this bug remain open as a reminder?
Yes, I think so.
Ludo’.
prev parent reply other threads:[~2018-06-21 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 20:58 bug#31887: Modules missing to boot on VMWare Taylan Ulrich Bayırlı/Kammer
2018-06-20 21:14 ` Ludovic Courtès
2018-06-21 18:19 ` Taylan Kammer
2018-06-21 20:52 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9g36ex8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31887@debbugs.gnu.org \
--cc=taylanbayirli@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).