[libvirt] [PATCH] qemu: Use memory-object-file when needed
Martin Kletzander
mkletzan at redhat.com
Wed Jan 13 09:17:09 UTC 2016
On Wed, Jan 13, 2016 at 02:14:58PM +0530, Shivaprasad bhat wrote:
>Hi Martin,
>
>I see, the memory from the node specified in numatune is used correctly.
>Wit your change memory-backend-file is used to enforce that
>
>But, I see the migrations from old versions(my case, 1.2.5) seems to fail
>as there was no backend-file before and only backend-ram.
>
Oh, you are absolutely right, that's why we kept the code as is, I
totally forgot about the reasoning behind this. If this doesn't affect
guest ABI, then we could use a migration flag for deciding which
approach to take. However, I don't feel strongly for the added
complexity that such change would make. Not in the migration code, but
rather the command-line change.
Anyway, we need to keep doing what we were before, so this patch is a
SNACK. We can decide what to do later on.
>Unknown ramblock "ppc_spapr.ram", cannot accept migration
>2016-01-13T08:16:17.488267Z qemu-system-ppc64-hp: error while loading state
>for instance 0x0 of device 'ram'
>
>Should we be using -mem-path /dev/hugepages/libvirt/qemu along with
>memory-backend-ram instead?
>
Both or none, plus this is not the root cause.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20160113/b1c954e7/attachment-0001.sig>
More information about the libvir-list
mailing list