From: linux_kvm@proinbox.com
To: "Markus Armbruster" <armbru@redhat.com>
Cc: "KVM mailing list" <kvm@vger.kernel.org>
Subject: Re: 8 NIC limit
Date: Tue, 05 Oct 2010 12:20:00 -0400 [thread overview]
Message-ID: <1286295600.14135.1398492979@webmail.messagingengine.com> (raw)
In-Reply-To: <m3tyl0aaz2.fsf@blackfin.pond.sub.org>
> Have you tried creating NICs with -device?
I'm not sure what that is, will look into it, thanks.
I'm using ProxmoxVE, and currently add them via a web interface.
Someone happens to host a screenshot of that part here:
http://c-nergy.be/blog/wp-content/uploads/Proxmox_Net2.png
On Tue, 05 Oct 2010 17:57 +0200, "Markus Armbruster" <armbru@redhat.com>
wrote:
> linux_kvm@proinbox.com writes:
>
> > Hello list:
> >
> > I'm working on a project that calls for the creation of a firewall in
> > KVM.
> > While adding a 20-interface trunk of virtio adapters to bring in a dual
> > 10GB bond, I've discovered an 8 NIC limit in QEMU.
>
> Have you tried creating NICs with -device? The limit shouldn't apply
> there.
>
next prev parent reply other threads:[~2010-10-05 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 14:48 8 NIC limit linux_kvm
2010-10-05 15:24 ` Dustin Kirkland
[not found] ` <1286294888.11462.1398488135@webmail.messagingengine.com>
[not found] ` <1286295603.7731.28.camel@x200>
2010-10-06 5:46 ` 8 NIC limit - patch - places limit at 32 linux_kvm
[not found] ` <4CAC719E.6060004@codemonkey.ws>
2010-10-06 17:11 ` linux_kvm
2010-10-07 1:39 ` Chris Wright
2010-10-05 15:57 ` 8 NIC limit Markus Armbruster
2010-10-05 16:20 ` linux_kvm [this message]
2010-10-05 16:43 ` Brian Jackson
-- strict thread matches above, loose matches on Subject: below --
2010-10-05 16:19 Fwd: " linux_kvm
2010-10-05 18:39 ` Chris Wright
2011-09-03 11:54 8 nic limit Richard Weinberger
2011-09-05 6:58 ` Jan Kiszka
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=1286295600.14135.1398492979@webmail.messagingengine.com \
--to=linux_kvm@proinbox.com \
--cc=armbru@redhat.com \
--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