From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Bharata B Rao <bharata.rao@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Unable to add ram object with same ID after addition, migration and removal at the target
Date: Fri, 2 Dec 2016 18:16:32 +0000 [thread overview]
Message-ID: <20161202181631.GH15373@work-vm> (raw)
In-Reply-To: <CAGZKiBoidWDhW6Pp-iQVNWJEkAJjpapAoEJmxA+b7_yf4y58Cw@mail.gmail.com>
* Bharata B Rao (bharata.rao@gmail.com) wrote:
> Hi,
>
> - Add ram object and dimm device at the source
>
> (qemu) object_add memory-backend-ram,id=ram0,size=128M
> (qemu) device_add pc-dimm,id=dimm0,memdev=ram0
>
> - Migrate the VM and remove the dimm device and ram object at the target
>
> (qemu) device_del dimm0
> (qemu) object_del ram0
>
> - Adding the ram object with same id now at the target fails like this:
>
> (qemu) info memdev
>
> (qemu) object_add memory-backend-ram,id=ram0,size=128M
> Duplicate ID 'ram0' for object
>
> Same behaviour is seen on x86 and Power. The problem isn't seen if
> migration isn't involved (add, remove, add at the source itself).
Is this the same as the one Michael Roth posted a fix for a few days
back; 'monitor: fix object_del for command-line-created objects'
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg05479.html
Dave
> Regards,
> Bharata.
> --
> http://raobharata.wordpress.com/
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-12-02 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 3:25 [Qemu-devel] Unable to add ram object with same ID after addition, migration and removal at the target Bharata B Rao
2016-12-02 18:16 ` Dr. David Alan Gilbert [this message]
2016-12-05 3:51 ` Bharata B Rao
2016-12-05 6:44 ` Michael Roth
2016-12-05 23:02 ` David Gibson
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=20161202181631.GH15373@work-vm \
--to=dgilbert@redhat.com \
--cc=bharata.rao@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.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 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.