From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: kvm@vger.kernel.org
Cc: Jean-Philippe MENIL <Jean-Philippe.Menil@univ-nantes.fr>,
RESEAUCRI <reseau@cri.univ-nantes.fr>
Subject: 8 nics limits on KVM ??
Date: Thu, 29 Jan 2009 15:24:46 +0100 [thread overview]
Message-ID: <4981BC2E.1010902@univ-nantes.fr> (raw)
Hello,
we are using kvm for wifidog, a wifi portal. In our case, we have lots
of VLANS, and those vlans are connected on separate bridges on the
host. So, for the kvm machine running wifidog, we're having lots of
virtual nics (more than 10). Launching kvm, we had this error mesage :
Too many nics.
The limit seems hardcoded in qemu (in qemu/net.h), I've changed MAX_NICS
from 8 to 24, and this seems to do the trick.
Is there any adverse effects doing this ? Is the limit arbitrary , or
there for a good reason ?
Cheers,
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.51.12.53.91 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
next reply other threads:[~2009-01-29 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:24 Yann Dupont [this message]
2009-02-02 16:25 ` 8 nics limits on KVM ?? 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=4981BC2E.1010902@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=Jean-Philippe.Menil@univ-nantes.fr \
--cc=kvm@vger.kernel.org \
--cc=reseau@cri.univ-nantes.fr \
/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