qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>,
	Hani Benhabiles <kroosec@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Crucial bug] Qemu-2.0.0 do not support virtio-net hot plug/unplug exceed two times
Date: Tue, 06 May 2014 15:36:38 +0200	[thread overview]
Message-ID: <5368E566.7070900@suse.de> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020815E61A2@SZXEMA503-MBS.china.huawei.com>

Hi Gonglei,

Am 06.05.2014 14:52, schrieb Gonglei (Arei):
> Step 1: I executed "device_add virtio-net-pci,id=net1"
> with "info pci", I found the net1, showing as below:
> Bus  0, device   4, function 0:
>     Ethernet controller: PCI device 1af4:1000
>       IRQ 0.
>       BAR0: I/O at 0xffffffffffffffff [0x001e].
>       BAR1: 32 bit memory at 0xffffffffffffffff [0x00000ffe].
>       BAR6: 32 bit memory at 0xffffffffffffffff [0x0003fffe].
>       id "net1"
> Step 2: I executed " device_del net1", but the net1 still existed.
> 
>> In QMP, you get a DEVICE_DELETED event when the unplug completes.  See
>> qmp/qmp-events.txt. 
> Actually, I don't get the event, as the net1 can't be unplug. 
> 
> BTW, when I execute step 1 "device_add virtio-net-pci,id=net1", I don't find the 
> Ethernet controller of virtio-net by "lspci " in the guest OS. 
> TBH, the command execution failed despite we can see net1 with "info pci".

Sounds like the acpiphp kernel module is not loaded inside the guest?

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-05-06 13:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <33183CC9F5247A488A2544077AF19020815E2DF1@SZXEMA503-MBS.china.huawei.com>
     [not found] ` <535BA2E4.4040202@redhat.com>
     [not found]   ` <33183CC9F5247A488A2544077AF19020815E2FE4@SZXEMA503-MBS.china.huawei.com>
     [not found]     ` <20140430000103.GA7429@Inspiron-3521>
2014-05-06  8:04       ` [Qemu-devel] [Crucial bug] Qemu-2.0.0 do not support virtio-net hot plug/unplug exceed two times Gonglei (Arei)
2014-05-06  9:47         ` Markus Armbruster
2014-05-06 12:52           ` Gonglei (Arei)
2014-05-06 13:36             ` Andreas Färber [this message]
2014-05-06 13:41               ` Gonglei (Arei)
2014-05-06 13:58                 ` Andreas Färber
2014-05-06 14:08                   ` Gonglei (Arei)
2014-05-06 15:02                     ` Andreas Färber
2014-05-12  7:08                       ` Andreas Färber
2014-05-12  8:06                         ` Gonglei (Arei)
2014-05-12  8:54                           ` Andreas Färber

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=5368E566.7070900@suse.de \
    --to=afaerber@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=armbru@redhat.com \
    --cc=kroosec@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).