public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Dor Laor <dor.laor@qumranet.com>,
	lkml <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: open /dev/kvm: No such file or directory
Date: Thu, 28 Dec 2006 17:51:07 +0200	[thread overview]
Message-ID: <4593E7EB.7070801@argo.co.il> (raw)
In-Reply-To: <b6a2187b0612280742x1b613849ye23aca38c71a5871@mail.gmail.com>

Jeff Chua wrote:
> On 12/28/06, Avi Kivity <avi@argo.co.il> wrote:
>
>> udev is the best solution here.  It works with read-only root as it
>> mounts tmpfs on /dev.
>
> Thanks for the suggestion and I'll look into it. As for now, my system
> works well without udev, and I just wanted to test kvm without the
> "dynamic" /dev/kvm feature if possible.
>
> Would it be possible to create /dev/kvm once and let it stay there
> permanently? How about a switch for non-udev system?

[cc'ing udev guru]

Greg, /dev/kvm is a MISC_DYNAMIC_MINOR device.  Is there any way of 
using it without udev?  Should I allocate a static number?


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2006-12-28 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 13:08 open /dev/kvm: No such file or directory Jeff Chua
2006-12-28 13:29 ` Dor Laor
2006-12-28 14:38   ` Jeff Chua
2006-12-28 14:51     ` Avi Kivity
2006-12-28 15:42       ` Jeff Chua
2006-12-28 15:51         ` Avi Kivity [this message]
2006-12-29  5:50           ` Arnd Bergmann
2006-12-29  8:48             ` Jeff Chua
2006-12-30  0:59           ` H. Peter Anvin
2006-12-29  4:37     ` Jeff Chua

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4593E7EB.7070801@argo.co.il \
    --to=avi@argo.co.il \
    --cc=dor.laor@qumranet.com \
    --cc=greg@kroah.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox