public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: linux_kvm@proinbox.com
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: NIC limit
Date: Wed, 6 Oct 2010 10:18:17 -0700	[thread overview]
Message-ID: <20101006171817.GE18885@sequoia.sous-sol.org> (raw)
In-Reply-To: <1286360484.21399.1398635889@webmail.messagingengine.com>

* linux_kvm@proinbox.com (linux_kvm@proinbox.com) wrote:
> Hi again everybody,
>  
> One of the admins at the ProxmoxVE project was gracious enough to
> quickly release a package including the previously discussed change to
> allow up to 32 NICs in qemu.

You mean they patched qemu to increase the MAX_NICS constant?  Nice to
get the quick turn around.

Te better choice is to use a newer command line.  Not only does it avoid
the MAX_NICS limitation, but it also enables standard virtio-net offload
accelerations.

> For future reference the .deb is here:
> ftp://download.proxmox.com/debian/dists/lenny/pvetest/binary-amd64/pve-qemu-kvm_0.12.5-2_amd64.deb
>  
> Upon creating & running the VM with the newly patched qemu-kvm app
> installed, I found a NIC limitation remained in place, presumably
> imposed by some other aspect of the environment.
>  
> The machine would start when it had 33 PCI devices, as long as no more
> than 28 of them were NICs.

The PCI bus has only 32 slots (devices), 3 taken by chipset + vga, and
a 4th if you have, for example, a virtio disk.  Are you sure these are
33 PCI devices and not 33 PCI functions?

thanks,
-chris

  reply	other threads:[~2010-10-06 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101006101931.0DFC04B2@gateway1.messagingengine.com>
2010-10-06 10:21 ` NIC limit linux_kvm
2010-10-06 17:18   ` Chris Wright [this message]
2010-10-07 18:03     ` linux_kvm

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=20101006171817.GE18885@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux_kvm@proinbox.com \
    /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