From: Avi Kivity <avi@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: KVM General <kvm@vger.kernel.org>
Subject: Re: device limit for kvm_io_bus
Date: Wed, 31 Mar 2010 09:14:50 +0300 [thread overview]
Message-ID: <4BB2E85A.7050202@redhat.com> (raw)
In-Reply-To: <8286e4ee1003300856u77cbce04o77c9cebfc2fd2729@mail.gmail.com>
On 03/30/2010 06:56 PM, Cam Macdonell wrote:
> Hi,
>
> I'm trying to use ioeventfds for notification between guests. After
> assigning a handful of ioeventfds I was getting a "no space left on
> device error". The culprit seems to be that only 6 devices are
> allowed for a guest on the kvm IO bus. The comment indicates a
> somewhat low number was chosen. Can the limit be increased to
> something on the order of the number of file descriptors a process
> could have?
>
There's in fact a patch on the list to do just that, at least three
people have been hitting it simultaneously.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-03-31 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 15:56 device limit for kvm_io_bus Cam Macdonell
2010-03-31 6:14 ` 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=4BB2E85A.7050202@redhat.com \
--to=avi@redhat.com \
--cc=cam@cs.ualberta.ca \
--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