public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Avi Kivity <avi@redhat.com>, Anjali Kulkarni <anjali@juniper.net>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hitting 29 NIC limit
Date: Thu, 14 Oct 2010 16:57:36 -0500	[thread overview]
Message-ID: <4CB77CD0.3030203@codemonkey.ws> (raw)
In-Reply-To: <20101014214205.GA32682@amd.home.annexia.org>

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 the 29/30/31 virtio-blk limit ... please!
>    

It was broken ages ago:

anthony@howler:~$ wc -l /proc/partitions; tail /proc/partitions
422 /proc/partitions
  251     1618          1 vdcx2
  251     1621     489951 vdcx5
  251     1632   10485760 vdcy
  251     1633    9992398 vdcy1
  251     1634          1 vdcy2
  251     1637     489951 vdcy5
  251     1648   10485760 vdcz
  251     1649    9992398 vdcz1
  251     1650          1 vdcz2
  251     1653     489951 vdcz5

This is what makes qdev so useful.

args=""
for slot in 5 6 7 8 9 10 11 12 13 14 15 16 17; do
for fn in 0 1 2 3 4 5 6 7; do
     args="$args -drive 
file=/home/anthony/images/linux.img,if=none,snapshot=on,id=disk${slot}_${fn}"
     args="$args -device 
virtio-blk-pci,addr=${slot}.${fn},drive=disk${slot}_${fn},multifunction=on"
done
done

x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img ${args} 
-enable-kvm -serial stdio

Regards,

Anthony Liguori

> Rich.
>
>    


  reply	other threads:[~2010-10-14 21:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C8DB7E5F.2FEA4%anjali@juniper.net>
2010-10-13 22:32 ` Hitting 29 NIC limit Anjali Kulkarni
2010-10-13 22:54   ` [Qemu-devel] " Anthony Liguori
2010-10-14 12:07     ` Avi Kivity
2010-10-14 12:10       ` Daniel P. Berrange
2010-10-14 12:57         ` Anthony Liguori
2010-10-18 20:07           ` H. Peter Anvin
2010-10-14 21:42         ` Richard W.M. Jones
2010-10-14 21:57           ` Anthony Liguori [this message]
2010-10-14 22:00             ` Anjali Kulkarni
2010-10-14 22:09               ` Anthony Liguori
2010-10-14 22:12                 ` Anjali Kulkarni
2010-10-14 22:17                   ` Anthony Liguori
2010-11-16 17:23                     ` Michael S. Tsirkin
2010-11-16 19:00                       ` Anthony Liguori
2010-10-14 22:08             ` [Qemu-devel] " Richard W.M. Jones
2010-10-14 12:36       ` Markus Armbruster
2010-10-14 12:59         ` Anthony Liguori
2010-10-15  9:11           ` Markus Armbruster
2010-10-15 18:49             ` Passing in additional info to guest OS and e1000 test suite? Anjali Kulkarni
2010-10-15 20:02               ` Anthony Liguori
2010-10-14 12:54       ` [Qemu-devel] Hitting 29 NIC limit Anthony Liguori
2010-10-14 13:23         ` Avi Kivity
2010-10-14 14:11           ` Anthony Liguori
2010-10-14 14:53             ` Avi Kivity
2010-10-28 20:52       ` [Qemu-devel] Hitting 29 NIC limit (+Intel VT-c) linux_kvm
2010-11-16 17:21       ` Hitting 29 NIC limit Michael S. Tsirkin

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=4CB77CD0.3030203@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=anjali@juniper.net \
    --cc=avi@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.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