On 2011-09-03 13:54, Richard Weinberger wrote:
Hi!
qemu-kvm seems to support only 8 network interfaces.
I found this posting from 2009:
http://www.mail-archive.com/kvm@vger.kernel.org/msg10104.html
Why is MAX_NICS still only 8?
Please raise this limit in future releases.
I have some
Hi!
qemu-kvm seems to support only 8 network interfaces.
I found this posting from 2009:
http://www.mail-archive.com/kvm@vger.kernel.org/msg10104.html
Why is MAX_NICS still only 8?
Please raise this limit in future releases.
I have some use cases where much more than 8 nics are needed.
(Lot's
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
On Thu, Oct 14, 2010 at 05:17:36PM -0500, Anthony Liguori wrote:
On 10/14/2010 05:12 PM, Anjali Kulkarni wrote:
Thanks. Does this work for e1000 as well?
Haven't tried. I don't know how various e1000 drivers would react.
Also, does it support pci hotplug?
No, but that's fixable down
On 11/16/2010 11:23 AM, Michael S. Tsirkin wrote:
On Thu, Oct 14, 2010 at 05:17:36PM -0500, Anthony Liguori wrote:
On 10/14/2010 05:12 PM, Anjali Kulkarni wrote:
Thanks. Does this work for e1000 as well?
Haven't tried. I don't know how various e1000 drivers would react.
On Thu, 14 Oct 2010 14:07 +0200, Avi Kivity a...@redhat.com wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
What's the motivation for such a huge number of interfaces?
Ultimately to bring multiple 10Gb bonds into a Vyatta guest.
---
On 10/14/2010 05:57 AM, Anthony Liguori wrote:
I've always been sceptical of this. When physical systems have a large
number of NICs, it's via multiple functions, not a bunch of PCI bridges.
Actually a lot of multiport PCI cards are in fact single or dual NICs
behind PCI bridges.
Anthony Liguori anth...@codemonkey.ws writes:
On 10/14/2010 07:36 AM, Markus Armbruster wrote:
Avi Kivitya...@redhat.com writes:
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
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
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
Avi Kivity a...@redhat.com writes:
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 10/14/2010 07:07 AM, 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
On 10/14/2010 07:10 AM, Daniel P. Berrange wrote:
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
On 10/14/2010 07:36 AM, Markus Armbruster wrote:
Avi Kivitya...@redhat.com writes:
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
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
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.
Yes. Our hotplug design is based on devices.. This is wrong, it
should be based on
On 10/14/2010 08:23 AM, Avi Kivity wrote:
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
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.
Yes. Our hotplug design is based on devices..
On 10/14/2010 04:11 PM, Anthony Liguori wrote:
On 10/14/2010 08:23 AM, Avi Kivity wrote:
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
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.
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break the 29/30/31 virtio-blk limit ... please!
Rich.
--
Richard Jones, Virtualization Group, Red Hat
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
Anjali
On 10/14/10 2:57 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel
On Thu, Oct 14, 2010 at 04:57:36PM -0500, Anthony Liguori wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break
On 10/14/2010 05:00 PM, Anjali Kulkarni wrote:
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
It's all below. You just have to create a PCI device and mark the
multifunction flag to on and then assign it a PCI
Thanks. Does this work for e1000 as well?
Also, does it support pci hotplug?
Anjali
On 10/14/10 3:09 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 05:00 PM, Anjali Kulkarni wrote:
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale
On 10/14/2010 05:12 PM, Anjali Kulkarni wrote:
Thanks. Does this work for e1000 as well?
Haven't tried. I don't know how various e1000 drivers would react.
Also, does it support pci hotplug?
No, but that's fixable down the road.
Regards,
Anthony Liguori
Anjali
On 10/14/10
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
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,
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?
No, not sure.
Apparently my statement was based on an uninformed assumption.
I tested using a VM that had 30
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.
For future reference the .deb is here:
It's 8 otherwise- and after the patch is applied, it still only goes to
28 for some reason.
28's acceptable for my needs, so I'll step aside from here leave it to
the experts.
As for the new -device method, that's all fine good but AFAIK it's not
implemented on my platform, so this was the
* linux_...@proinbox.com (linux_...@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
* Anthony Liguori (anth...@codemonkey.ws) wrote:
BTW, using -device, it should be possible to add a very high number of
nics because you can specify the PCI address including a function. If
this doesn't Just Work today, we should make it work.
Should work...test...mostly[1], but I don't
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.
I found the following thread in the list archives detailing a similar
problem:
http
On Tue, Oct 5, 2010 at 7:48 AM, linux_...@proinbox.com wrote:
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.
I found
linux_...@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
discovered an 8 NIC limit in QEMU.
I found the following thread in the list archives detailing a similar
problem:
http://kerneltrap.org/mailarchive/linux-kvm/2009/1/29/4848304
It includes a patch for the file qemu/net.h to allow 24 NICs:
https://bugs.launchpad.net/ubuntu/+source/qemu
2010 17:57 +0200, Markus Armbruster arm...@redhat.com
wrote:
linux_...@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
On 10/5/2010 9:48 AM, linux_...@proinbox.com wrote:
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.
I found the following thread
* linux_...@proinbox.com (linux_...@proinbox.com) wrote:
I don't know how to make the determination, but it makes sense to me for
the limit defined here to be indicitive of an actual limitation, rather
than what seems an arbitrary best-guess as to the most someone might
need.
The actual
Attached is a patch that allows qemu to have up to 32 NICs, without
using the qdev -device method.
max_nics.patch
Description: Binary data
38 matches
Mail list logo
