public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Anjali Kulkarni <anjali@juniper.net>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hitting 29 NIC limit
Date: Thu, 14 Oct 2010 13:10:47 +0100	[thread overview]
Message-ID: <20101014121047.GN11403@redhat.com> (raw)
In-Reply-To: <4CB6F275.2060204@redhat.com>

On Thu, Oct 14, 2010 at 02:07:17PM +0200, Avi Kivity wrote:
>  On 10/14/2010 12:54 AM, Anthony Liguori wrote:
> >On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
> >>
> >>Hi,
> >>
> >>Using the legacy way of starting up NICs, I am hitting a limitation 
> >>after 29
> >>NICs ie no more than 29 are detected (that's because of the 32 PCI slot
> >>limit on a single bus- 3 are already taken up)
> >>I had initially increased the MAX_NICS to 48, just on my tree, to get to
> >>more, but ofcource that wont work.
> >>Is there any way to go beyond 29 NICs the legacy way?  What is the 
> >>maximum
> >>that can be supported by the qdev mothod?
> >
> >I got up to 104 without trying very hard using the following script:
> >
> >args=""
> >for slot in 5 6 7 8 9 10 11 12 13 14 15 16 17; do
> >for fn in 0 1 2 3 4 5 6 7; do
> >    args="$args -netdev user,id=eth${slot}_${fn}"
> >    args="$args -device 
> >virtio-net-pci,addr=${slot}.${fn},netdev=eth${slot}_${fn},multifunction=on,romfile="
> >done
> >done
> >
> >x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img ${args} 
> >-enable-kvm
> >
> >The key is to make the virtio-net devices multifunction and to fill 
> >out all 8 functions for each slot.
> 
> This is unlikely to work right wrt pci hotplug.  If we want to support a 
> large number of interfaces, we need true multiport cards.

Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.

Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2010-10-14 12:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C8DB7E5F.2FEA4%anjali@juniper.net>
2010-10-13 22:32 ` Hitting 29 NIC limit Anjali Kulkarni
2010-10-13 22:54   ` [Qemu-devel] " Anthony Liguori
2010-10-14 12:07     ` Avi Kivity
2010-10-14 12:10       ` Daniel P. Berrange [this message]
2010-10-14 12:57         ` Anthony Liguori
2010-10-18 20:07           ` H. Peter Anvin
2010-10-14 21:42         ` Richard W.M. Jones
2010-10-14 21:57           ` Anthony Liguori
2010-10-14 22:00             ` Anjali Kulkarni
2010-10-14 22:09               ` Anthony Liguori
2010-10-14 22:12                 ` Anjali Kulkarni
2010-10-14 22:17                   ` Anthony Liguori
2010-11-16 17:23                     ` Michael S. Tsirkin
2010-11-16 19:00                       ` Anthony Liguori
2010-10-14 22:08             ` [Qemu-devel] " Richard W.M. Jones
2010-10-14 12:36       ` Markus Armbruster
2010-10-14 12:59         ` Anthony Liguori
2010-10-15  9:11           ` Markus Armbruster
2010-10-15 18:49             ` Passing in additional info to guest OS and e1000 test suite? Anjali Kulkarni
2010-10-15 20:02               ` Anthony Liguori
2010-10-14 12:54       ` [Qemu-devel] Hitting 29 NIC limit Anthony Liguori
2010-10-14 13:23         ` Avi Kivity
2010-10-14 14:11           ` Anthony Liguori
2010-10-14 14:53             ` Avi Kivity
2010-10-28 20:52       ` [Qemu-devel] Hitting 29 NIC limit (+Intel VT-c) linux_kvm
2010-11-16 17:21       ` Hitting 29 NIC limit Michael S. Tsirkin

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=20101014121047.GN11403@redhat.com \
    --to=berrange@redhat.com \
    --cc=anjali@juniper.net \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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