public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Will Trives <will@trivescon.com.au>
Cc: kvm-devel@lists.sourceforge.net, Dor Laor <dor.laor@gmail.com>,
	Avi Kivity <avi@qumranet.com>
Subject: Re: Virtio with multiple devices of the same type
Date: Tue, 12 Feb 2008 23:17:06 -0600	[thread overview]
Message-ID: <47B27D52.7070809@codemonkey.ws> (raw)
In-Reply-To: <1202873568.3319.280.camel@athas>

Hi Will,

> Example command line: 
>
> This is observed :
>
> * On a 64 bit host with an Intel Q6600 cpu
> * Host is 64 bit, guest 64 bit.
> * latest Linux git kernel (which has the new virtio code in it from Rusty) both for host and guest
> * the latest KVM userspace (with --with-patched-kernel or by syncing to the latest kvm git tree)
> * the behaviour with the network devices is observed regardless of whether the network drive is compiled in or modular.
>
> I was wondering if this is helpful or can be replicated, if not perhaps my guest which is running Archlinux64 is doing something strange.
>   

Here's what I'm observing:

 * I can create two block devices just fine.
 * There are IRQ routing issues when I try to create 3 block devices, if 
I pass -no-acpi when starting the guest, I can use 24 virtio block 
devices without a problem
 * hw/virtio-net.c needs to be aware of reset to cancel any pending tx 
timers.  I have a patch that fixes this.  I'll send it out tomorrow 
after more testing
 * I can't seem to use more than two virtio_net devices when using -net 
tap.  When using -net user, I can create up to 8 virtio network devices 
(and they seem to work).
 * QEMU has a hard limit of 32 PCI devices.  Right now, we just get a 
SEGV when we exceed this.

So I think our problems are:

 * Something is goofy with ACPI and PCI interrupt routing.  
-no-kvm-irqchip does not help the situation
 * I need to send out a patch to make virtio_net reset aware
 * -net tap is broken for more than 1 network device (at least with virtio)
 * QEMU should allow more than 32 PCI devices.

Please try your tests again with -no-acpi and -net user and let me know 
if that prevents the problem.  Thanks for testing!

Regards,

Anthony Liguori

> Regards,
>
> Will Trives
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-13  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  3:32 Virtio with multiple devices of the same type Will Trives
2008-02-13  5:17 ` Anthony Liguori [this message]
2008-02-13  7:24 ` Avi Kivity

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=47B27D52.7070809@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=dor.laor@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=will@trivescon.com.au \
    /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