From: Eric Blake <eblake@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: Yanqiangjun <yanqiangjun@huawei.com>,
Luonengjun <luonengjun@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangweidong (Hardware)" <huangweidong@huawei.com>
Subject: Re: [Qemu-devel] "virsh edit" failed to take effect on KVM
Date: Thu, 09 May 2013 08:11:19 -0600 [thread overview]
Message-ID: <518BAE87.2000208@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF190205369B2BE@szxeml538-mbx.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On 05/09/2013 05:42 AM, Gonglei (Arei) wrote:
> Hi all,
> we use the command "virsh edit" to modify the VM configuration information online on KVM Platform(libvirt-1.0.0 and qemu-1.4),
> but it does not take effect after reboot. However, it works fine on Xen Platform.
This sort of question belongs best on libvirt-users@redhat.com
(libvirt-list-request is not the right list address, and your question
isn't quite relevant to qemu-devel).
> With the changing, the VM is expected to start from cdrom, when execute the command "virsh reboot".
'virsh reboot' triggers a software reboot (reusing the same existing
qemu process); but 'virsh edit' only affects what will take place on a
hard boot (creation of a new qemu process).
> But the fact is that the modify does not take effect, the VM is still start from hd.
> Well, it will take effect if I use command "virsh shutdown" and "virsh start" instesad of "virsh reboot".
Correct, because that sequence spawns a new qemu process.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-05-09 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 11:42 [Qemu-devel] "virsh edit" failed to take effect on KVM Gonglei (Arei)
2013-05-09 12:58 ` Laszlo Ersek
2013-05-09 14:11 ` Eric Blake [this message]
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=518BAE87.2000208@redhat.com \
--to=eblake@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=huangweidong@huawei.com \
--cc=luonengjun@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=yanqiangjun@huawei.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 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).