All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm list <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: PCI hotplug broken?
Date: Mon, 1 Mar 2010 14:51:51 -0300	[thread overview]
Message-ID: <20100301175151.GB10096@amt.cnet> (raw)
In-Reply-To: <FD6E800A-2145-40D4-932D-9FBC421AF2BB@suse.de>

On Fri, Feb 26, 2010 at 03:53:48PM +0100, Alexander Graf wrote:
> 
> On 26.02.2010, at 15:12, Alexander Graf wrote:
> 
> > Hi list,
> > 
> > While trying to upgrade some internal infrastructure to qemu-kvm-0.12 I stumbled across this really weird problem that I see with current qemu-kvm git too:
> > 
> > I start qemu-kvm using:
> > 
> > ./qemu-system-x86_64 -L ../pc-bios/ -m 512 -net nic,model=virtio -net tap,ifname=tap0,script=/bin/true -snapshot sles11.qcow2 -vnc :0 -monitor stdio
> > 
> > The system boots up just fine, networking works.
> > 
> > On the qemu monitor I then issue:
> > 
> > (qemu) pci_add auto storage file=/tmp/image.raw,if=virtio
> > 
> > after which I get a fully functional virtio block device, but the network stops sending/receiving packets.
> > 
> > The same thing with qemu-kvm-0.10 works just fine. Has anyone seen this before?
> 
> Same thing happens when hotplug only:
> 
> pci_add auto nic model=virtio,vlan=0
> 
> -> network works
> 
> pci_add auto storage file=/tmp/image.raw,if=virtio
> 
> -> network stops working
> 
> pci_add auto nic model=virtio,vlan=0
> 
> -> network works again on the new device

Can reproduce it. "info pci" shows IRQ0 assigned to virtio-blk.
Did you try, say, e1000 and SCSI ?


  reply	other threads:[~2010-03-01 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 14:12 PCI hotplug broken? Alexander Graf
2010-02-26 14:53 ` Alexander Graf
2010-03-01 17:51   ` Marcelo Tosatti [this message]
2010-03-01 17:53     ` Alexander Graf

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=20100301175151.GB10096@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=agraf@suse.de \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.