unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27636@debbugs.gnu.org
Subject: bug#27636: /dev/kvm went missing on i686, Linux 4.12
Date: Tue, 18 Jul 2017 16:02:06 -0400	[thread overview]
Message-ID: <878tjlzf7l.fsf@netris.org> (raw)
In-Reply-To: <878tjmhlqm.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 17 Jul 2017 22:06:09 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Since the update to Linux 4.12 my i686 machine no longer has /dev/kvm.
>>> I ran “modprobe kvm” successfully, and “lsmod” shows “kvm”, but the
>>> device node does not exist.
>>>
>>> Running “modprobe kvm-intel” prints:
>>>
>>>     modprobe: ERROR: could not insert 'kvm_intel': Input/output error
>>
>> Does the kernel message buffer mention anything about "kvm" or "KVM"?
>>
>>   dmesg | grep -i kvm
>
> No, there is no mention of “kvm” or “KVM” in the kernel messages.

When you looked for "kvm" or "KVM", did your kernel message buffer still
include the initial boot messages?  The kernel message buffer is of a
fixed size, so eventually the early messages are lost.

The reason I ask is because I did some web searches looking for other
people with the same problem, and what I found was that there was
typically a kernel message at boot time explaining why KVM was disabled.

In my case, on my Thinkpad X200 (which I'm sorry to say is running a
proprietary BIOS for now, because I had to replace the motherboard
recently and haven't yet gotten around to buying the needed clip to
reflash) I see the message "kvm: disabled by bios".

I'm fairly sure that I've seen /dev/kvm on this machine in the past.  It
might be that in earlier versions of Linux, /dev/kvm was created even
when it couldn't be used, and now it's created only conditionally, but
that's only a guess.

I haven't made any changes to the kernel configuration except to add
support for new modules and features as they become available, and as
far as I can see, the relevant KVM options are enabled just as they have
been in the past.

If all else fails, you could try using the 4.9 or 4.4 kernel and see if
that makes any difference.

       Mark

  reply	other threads:[~2017-07-18 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  5:40 bug#27636: /dev/kvm went missing on i686, Linux 4.12 Ricardo Wurmus
2017-07-10 15:52 ` Leo Famulari
2017-07-10 17:29 ` Mark H Weaver
2017-07-17 20:06   ` Ricardo Wurmus
2017-07-18 20:02     ` Mark H Weaver [this message]
2017-07-18 20:09       ` Ricardo Wurmus
2019-06-23  4:13 ` Chris Marusich
2020-03-22 20:34   ` Leo Famulari

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=878tjlzf7l.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=27636@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).