From: Ashijeet Acharya <ashijeetacharya@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>, jsnow@redhat.com
Subject: Re: [Qemu-devel] Dangling change state handler while hot unplugging ahci adapter
Date: Tue, 9 Aug 2016 22:46:51 +0530 [thread overview]
Message-ID: <CAC2QTZZM0vcm48tCfvosH+kFuscV7UMVMNDyzkEMvF5dm+2shg@mail.gmail.com> (raw)
In-Reply-To: <CAC2QTZaeboA=HZ49irTjCfcYAjp80JiaTX3E=mOd8WZ3scADdA@mail.gmail.com>
Hi again,
I am still waiting for some guidance...Can I please get some help with this?
Also.. I tried hotplugging an AHCI adapter but got the following error:
Bus 'ahci.0' does not support hotplugging
Steps I followed:
1. launch vm with ahci enabled
2. (qemu) drive_add 0 file=test.qcow2,cache=none,if=none,id=disk2,format=qcow2
OK
3. (qemu) device_add ide-hd,bus=ahci.0,id=ahci-disk,drive=disk2
Bus 'ahci.0' does not support hotplugging
What am I doing wrong?
Thanks
Ashijeet
On Sat, Aug 6, 2016 at 11:21 PM, Ashijeet Acharya
<ashijeetacharya@gmail.com> wrote:
> Hi,
>
> I was working on a patch regarding a device lifecycle bitesize task
> and I wanted to clear my queries about what the task is exactly.
>
> Do I need to create a new function ahci_unrealize() in the
> hw/ide/ahci.c file which calls for qemu_del_vm_change_state_handler()
> to free the handler at the time of ahci hot unplug.
>
> Please tell me if I am on the right path and correct me if I am wrong.
>
> Thanks
> Ashijeet
next prev parent reply other threads:[~2016-08-09 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 17:51 [Qemu-devel] Dangling change state handler while hot unplugging ahci adapter Ashijeet Acharya
2016-08-09 17:16 ` Ashijeet Acharya [this message]
2016-08-09 18:18 ` John Snow
2016-08-10 5:42 ` Ashijeet Acharya
2016-08-11 8:20 ` Ashijeet Acharya
2016-08-11 16:20 ` Ashijeet Acharya
2016-08-11 16:34 ` Paolo Bonzini
2016-08-11 16:40 ` Ashijeet Acharya
2016-08-11 18:45 ` [Qemu-devel] [PATCH] Fix memory leak in ide_register_restart_cb() Ashijeet Acharya
2016-08-12 9:58 ` Paolo Bonzini
2016-08-16 13:55 ` Ashijeet Acharya
2016-08-16 17:08 ` John Snow
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=CAC2QTZZM0vcm48tCfvosH+kFuscV7UMVMNDyzkEMvF5dm+2shg@mail.gmail.com \
--to=ashijeetacharya@gmail.com \
--cc=jsnow@redhat.com \
--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).