From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Benjamin Budts <benjamin.budts-rJAIWvhRp0CZIoH1IeqzKA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Benjamin Budts <ben-FwLs51Cl57fY4EFHVxF16w@public.gmane.org>
Subject: Re: could not open /dev/kvm
Date: Sun, 22 Apr 2007 12:07:33 +0300 [thread overview]
Message-ID: <462B25D5.7040200@qumranet.com> (raw)
In-Reply-To: <462ADDD7.4080704-rJAIWvhRp0CZIoH1IeqzKA@public.gmane.org>
Benjamin Budts wrote:
> Hi,
>
> I made an mknod myself now, did a cat of /sys/class/misc/kvm/dev
> 18 64
>
> and did a
> mknod /dev/kvm c 18 64
>
> everything OK now
>
> how come I dont have the /dev automatically ?
>
> udevtrigger didn't help, pgrep udevd showed the pid of udevd... so it
> was alive and kicking.
> even recompiled the whole thing with modules loaded and had the same
> problem. recreated it manually with mknod...
>
> i'm running the latest stable debian etch kernel 2.6.20.7
>
>
Sorry, no idea. Maybe as the debian people?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
prev parent reply other threads:[~2007-04-22 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 18:29 could not open /dev/kvm Benjamin Budts
[not found] ` <4626638D.8080709-FwLs51Cl57fY4EFHVxF16w@public.gmane.org>
2007-04-19 6:09 ` Avi Kivity
[not found] ` <462707A0.40907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-22 4:00 ` Benjamin Budts
[not found] ` <462ADDD7.4080704-rJAIWvhRp0CZIoH1IeqzKA@public.gmane.org>
2007-04-22 9:07 ` Avi Kivity [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462B25D5.7040200@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ben-FwLs51Cl57fY4EFHVxF16w@public.gmane.org \
--cc=benjamin.budts-rJAIWvhRp0CZIoH1IeqzKA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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