On 8 January 2013 19:04, Anthony Liguori wrote:
> This is an internal detail between Xen and QEMU. That doesn't mean it's
> a general public API.
>
> I'm fairly certain that Xen does not support arbitrary versions of QEMU
> to be used as qemu-dm.
I would have thought that would be a large part o
Peter Feiner writes:
>> This is not reasonable IMHO.
>>
>> I was okay with sticking a name on a ramblock, but encoding a guest PA
>> offset turns this into a supported ABI which I'm not willing to do.
>>
>> A one line change is one thing, but not a complex new option that
>> introduces an ABI onl
> This is not reasonable IMHO.
>
> I was okay with sticking a name on a ramblock, but encoding a guest PA
> offset turns this into a supported ABI which I'm not willing to do.
>
> A one line change is one thing, but not a complex new option that
> introduces an ABI only for a proprietary product th
Peter Feiner writes:
> This patch makes the -mem-path filenames deterministic and allows some control
> over how QEMU mmaps the files. Given this control, QEMU can be used to
> implement
> exogenous memory management techniques quite simply. Two examples follow:
>
> 1. Post-copy migration (m
Ping?
P.S. Please note a typo in the cover letter: when I referred to KSM, I
meant "kernel samepage merging", not "kernel shared memory" :-)
On Tue, Nov 20, 2012 at 7:10 AM, Peter Feiner wrote:
> This patch makes the -mem-path filenames deterministic and allows some
> control
> over how QEMU m
This patch makes the -mem-path filenames deterministic and allows some control
over how QEMU mmaps the files. Given this control, QEMU can be used to implement
exogenous memory management techniques quite simply. Two examples follow:
1. Post-copy migration (mmap=shared for origin, save device
