From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Wu, Jiaxin" <jiaxin.wu@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] The maximum limit of virtual network device
Date: Thu, 6 Jul 2017 09:11:17 +0100 [thread overview]
Message-ID: <20170706081117.GC3988@redhat.com> (raw)
In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274162E2512@SHSMSX103.ccr.corp.intel.com>
On Thu, Jul 06, 2017 at 06:20:54AM +0000, Wu, Jiaxin wrote:
> Hello experts,
>
> We know QEMU has the capability to create the multiple network devices in one QEMU guest with the -device syntax. But I met the below failure when I'm trying to create more than 30 virtual devices with the each TAP backend:
>
> qemu-system-x86_64: -device e1000: PCI: no slot/function available for e1000, all in use.
>
> The corresponding QEMU command shows as following:
[snip]
> From above, the max limit of virtual network device in one guest is about
> 29? If not, how can I avoid such failure? My use case is to create more than
> 150 network devices in one guest. Please provide your comments on this.
As the error message above shows, you have run out of PCI slots on the default
PCI bus. There are two ways to get around this. The first is to make use of
multifunction=on and specify individual PCI functions. There are 7 functions
per slot, so that would take you to 203 devices. The downside of multifunction
is that you can't hotplug individual functions. The second approach is to
just add a bunch of PCI bridges, so that you have more slots available.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-06 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 6:20 [Qemu-devel] The maximum limit of virtual network device Wu, Jiaxin
2017-07-06 8:11 ` Daniel P. Berrange [this message]
2017-07-06 8:31 ` Laszlo Ersek
2017-07-06 9:24 ` Marcel Apfelbaum
2017-07-06 9:46 ` Laszlo Ersek
2017-07-06 14:49 ` Wu, Jiaxin
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=20170706081117.GC3988@redhat.com \
--to=berrange@redhat.com \
--cc=jiaxin.wu@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).