From: Christopher Allan Webber <cwebber@dustycloud.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22633@debbugs.gnu.org
Subject: bug#22633: Provide a kvm-less qemu / guix system vm
Date: Mon, 22 Feb 2016 10:56:02 -0800 [thread overview]
Message-ID: <87si0k8th9.fsf@dustycloud.org> (raw)
In-Reply-To: <87twl2xo6c.fsf@gnu.org>
Ludovic Courtès writes:
> Libkmod honors ‘modprobe.blacklist’ (in ‘kcmdline_parse_result’ in
> libkmod-config.c) and eudev passes KMOD_PROBE_APPLY_BLACKLIST
> unconditionally in udev-builtin-kmod.c (meaning it honors it too.)
>
> However, there’s a hyphen-vs-underscore issue, I think. Namely, the
> file is called ‘kvm-intel.ko’, but the normalized module name is
> ‘kvm_intel’, and this is what libkmod expects (commit 5c7dd5a changes
> our code to normalize module names similarly.)
>
> Could you try with “modprobe.blacklist=kvm_intel”?
I tried it, and it works! This does mean that /dev/kvm doesn't exist,
so I should be able to write a patch to Guix that disables kvm for qemu
when /dev/kvm is absent. Great! :)
next prev parent reply other threads:[~2016-02-22 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 17:26 bug#22633: Provide a kvm-less qemu / guix system vm Christopher Allan Webber
2016-02-11 22:50 ` Jookia
2016-02-12 0:49 ` Leo Famulari
2016-02-12 18:04 ` Christopher Allan Webber
2016-02-13 0:47 ` Leo Famulari
2016-02-12 9:02 ` Ludovic Courtès
2016-02-12 17:47 ` Christopher Allan Webber
2016-02-13 19:10 ` Alex Kost
2016-02-21 12:09 ` Ludovic Courtès
2016-02-23 8:08 ` Alex Kost
2016-02-21 12:06 ` Ludovic Courtès
2016-02-22 18:56 ` Christopher Allan Webber [this message]
2016-02-22 19:35 ` Christopher Allan Webber
2016-02-22 19:43 ` Jookia
2016-02-22 21:27 ` Christopher Allan Webber
2016-02-22 21:09 ` Ludovic Courtès
2016-02-22 21:30 ` Christopher Allan Webber
2016-02-23 16:13 ` Ludovic Courtès
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=87si0k8th9.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=22633@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).