From: Matias Aguirre <maguirre@matware.com.ar>
To: Michael Malone <michael.malone@tait.co.nz>
Cc: kvm@vger.kernel.org
Subject: Re: kvm 76 - open /dev/kvm: No such device or address
Date: Wed, 08 Oct 2008 02:51:18 -0300 [thread overview]
Message-ID: <48EC4A56.4040902@matware.com.ar> (raw)
In-Reply-To: <48EBEE03.8090904@tait.co.nz>
$ groups
audio floppy video cdrom plugdev web kvm
The user have the kvm group. Can be the CPU broke?
Michael Malone wrote:
> Also, you might want to make sure that the user you're using to run
> KVM has been added to the kvm group and make sure that your X-session
> has been restarted since this change, or it will not have taken effect.
>
> Matias Aguirre wrote:
>> Hi all,
>>
>> Im using 2.6.26.5 kernel and slackware-current distribution. I was
>> compiled the latest 76 version of kvm and when i run kvm i return
>> this error:
>>
>> open /dev/kvm: No such device or address
>> Could not initialize KVM, will disable KVM support
>>
>> The module is already loaded:
>>
>> # lsmod
>> Module Size Used by
>> kvm_intel 33984 0
>> kvm 116156 1 kvm_intel
>> nvidia 6886800 26
>>
>> And my CPU have VM support.
>>
>> # cat /proc/cpuinfo | grep vmx
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
>> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
>> pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx
>> smx est tm2 ssse3 cx16 xtpr lahf_lm
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
>> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
>> pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx
>> smx est tm2 ssse3 cx16 xtpr lahf_lm
>>
>> And the file permission:
>>
>> # dir /dev/kvm
>> crw-rwxr-- 1 root kvm 250, 0 2008-10-07 18:22 /dev/kvm
>>
>>
>> Any help?
>>
>> Thanks
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
> =======================================================================
> This email, including any attachments, is only for the intended
> addressee. It is subject to copyright, is confidential and may be
> the subject of legal or other privilege, none of which is waived or
> lost by reason of this transmission.
> If the receiver is not the intended addressee, please accept our
> apologies, notify us by return, delete all copies and perform no
> other act on the email.
> Unfortunately, we cannot warrant that the email has not been
> altered or corrupted during transmission.
> =======================================================================
next prev parent reply other threads:[~2008-10-08 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 22:54 kvm 76 - open /dev/kvm: No such device or address Matias Aguirre
2008-10-07 23:15 ` Dor Laor
2008-10-08 5:49 ` Matias Aguirre
2008-10-08 6:58 ` Ryota OZAKI
2008-10-08 7:03 ` Matias Aguirre
2008-10-07 23:17 ` Michael Malone
2008-10-08 5:51 ` Matias Aguirre [this message]
2008-10-08 19:33 ` Michael Malone
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=48EC4A56.4040902@matware.com.ar \
--to=maguirre@matware.com.ar \
--cc=kvm@vger.kernel.org \
--cc=michael.malone@tait.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).