From: Mohsin Kazmi <mohsin.kazmi14@gmail.com>
To: zhugh.fnst@cn.fujitsu.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Unparking vCPU mechanism
Date: Thu, 16 Apr 2015 12:50:37 +0200 [thread overview]
Message-ID: <CAKkt9+KkA=ww-29JAHZ_0Nd6-vTKKzOdxhjWnKZgLhKDzx3U0A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Hi Zhu,
I am testing the hot unplug feature using your github branch
'cpu-hotplug'. It is working fine when first time I added and deleted cpu.
But when I tried to add cpu second time, it showed me the following error:
(qemu) device_add kvm64-x86_64-cpu,apic-id=1,id=cpu1
Duplicate ID 'cpu1' for device
I get from one of your patch (https://patchwork.ozlabs.org/patch/439485/)
commit message that cpu is not literally removed from qemu but guest is
unable to use it anymore. Do you know the way how I can reuse that cpu
which has already added and deleted once. Or unparking the cpu mechanism.
Thanks,
Mohsin Kazmi
[-- Attachment #2: Type: text/html, Size: 835 bytes --]
next reply other threads:[~2015-04-16 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 10:50 Mohsin Kazmi [this message]
2015-04-20 9:19 ` [Qemu-devel] Unparking vCPU mechanism Zhu Guihua
2015-04-20 12:16 ` Mohsin Kazmi
2015-04-20 13:13 ` Mohsin Kazmi
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='CAKkt9+KkA=ww-29JAHZ_0Nd6-vTKKzOdxhjWnKZgLhKDzx3U0A@mail.gmail.com' \
--to=mohsin.kazmi14@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=zhugh.fnst@cn.fujitsu.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.