public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Khaled El Mously <khaled@fuzzbuzz.org>
Cc: haishan <haishan.bai@gmail.com>, kvm@vger.kernel.org
Subject: Re: kvm unhandled exit 4400
Date: Sat, 06 Nov 2010 01:32:20 +0300	[thread overview]
Message-ID: <4CD485F4.4020401@msgid.tls.msk.ru> (raw)
In-Reply-To: <4CD1D116.1080908@msgid.tls.msk.ru>

[Replying to my own email]
04.11.2010 00:16, Michael Tokarev wrote:
> 03.11.2010 22:44, Khaled El Mously wrote:
>> The host kernel is on Ubuntu: 2.6.32-25-generic
>>
>> The guest kernel is 2.6.34-something.
>>
>> I have figured out what the problem is. When I first attempted to run kvm, it said access to /dev/kvm was denied. So I did "chmod o+rw /dev/kvm" and reloaded. It stopped complaining about permissions, but apparently it won't work unless you have the +x as well (i.e. need to do "chmod o+rwx /dev/kvm" ). Perhaps that should be documented somewhere. Or maybe kvm should specifically check for that and complain early.
> 
> Um.  Please excuse me but this is a complete bullshit.

As others pointed out, this is too harsh.  It wasn't
intentional to be extra harsh here, it was just me
not realizing how harsh such a statement is, as
English is not my native language and I dont use it
much.  Far more appropriate word for this context
is "nonsense".  I apologize for using inappropriate
words.

> qemu opens /dev/kvm in O_RDWR mode.  It does not
> execute that file, execute bit is not needed.

/mjt

  reply	other threads:[~2010-11-05 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 21:01 kvm unhandled exit 4400 Khaled El Mously
2010-11-03  9:14 ` haishan
2010-11-03  9:32 ` haishan
2010-11-03 19:44   ` Khaled El Mously
2010-11-03 21:16     ` Michael Tokarev
2010-11-05 22:32       ` Michael Tokarev [this message]
2010-11-06  4:38         ` Khaled El Mously
2010-11-06 17:35         ` Avi Kivity

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=4CD485F4.4020401@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=haishan.bai@gmail.com \
    --cc=khaled@fuzzbuzz.org \
    --cc=kvm@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