Forgot to cc list, forwarding. > In this case, I think you're going to want to send your patch to the > qemu-devel (on CC) mailing list (perhaps in addition to sending it > here, to the kvm list).
Will do, thanks for the pointer. Before I do so, I'd like to bring up one thing that comes to mind. 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. If the change ends up being permanent, then I would hope it would be a large enough value to provide a degree of extensibility and prevent the necessity of bumping it up again later when someone else comes along with even greater bandwidth requirements. Perhaps someone could provide some guidance as to a sane, higher number, as opposed to an arbitrary '65000' which would surely prevent this from happening again (knock on wood). For the time being I still have to find something to help learn how to implement the change locally. I rarely have to compile let alone deal with patches, so to me at least this is a considerable obstacle. -Thanks On Tue, 05 Oct 2010 08:24 -0700, "Dustin Kirkland" <kirkl...@canonical.com> wrote: > 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 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-kvm";>qemu-kvm/+bug/595873/+attachment/1429544/+files/max_nics.patch > > > > In my case I want to attach 29, and have simply changed line 8 to 30 > > from 24. > > > > This will be the first patch I've ever had to do, and so far my internet > > search yields results that don't seem to apply. > > > > Would someone like to recommend a pertinent tutorial? > > Hi there, > > I commented on the original bug in Launchpad. We're willing and able > to carry the patch against qemu-kvm in Ubuntu, I just asked that the > reporter at least submit the patch upstream for discussion. I don't > see where that has happened yet. It's a trivial patch to submit. > Please note in that bug a pointer to the mailing list thread, if you > start one. > > To your specific question, different communities have different > requirements on patch submission, so you do need to consult each > community. A good place to start might be the > Documentation/SubmittingPatches how-to in the kernel tree: > * > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/SubmittingPatches;hb=HEAD > > In this case, I think you're going to want to send your patch to the > qemu-devel (on CC) mailing list (perhaps in addition to sending it > here, to the kvm list). > > :-Dustin > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
