On 12/19/2011 12:26 PM, Peter Feiner wrote:
Hi,
Is there any interest in this feature?
BTW, as far as I can tell, on qemu-devel I'm not supposed to re-post
the patch or post a v2 if there haven't been any specific requests for
changes to v1. Please let me know if you'd like me to submit a new
p
Hi,
Is there any interest in this feature?
BTW, as far as I can tell, on qemu-devel I'm not supposed to re-post
the patch or post a v2 if there haven't been any specific requests for
changes to v1. Please let me know if you'd like me to submit a new
patch!
Thanks,
Peter Feiner
>> Do you have any performance number for this? And examples on how your
>> are using it?
> Our principal use case is implementing VM migration techniques.
There are other uses of a RAM file interface that I can imagine:
- debugging, e.g., inspecting the memory of a VM after it has crashed
- se
> Hi
Hi Juan,
Sorry for taking so long to reply -- my email filters apparently
aren't setup correctly!
> Do you have any performance number for this? And examples on how your
> are using it?
The performance should depend only on the VMA backing the file, in
addition to any indirect overhead ca
Peter Feiner wrote:
> Enables providing a backing file for the PC's ram. The file is specified by
> the
> new -pcram-file option. The file is mmap'd shared, so the RAMBlock that it
> backs
> doesn't need to be saved by vm_save / migration.
>
> Signed-off-by: Peter Feiner
Hi
Do you have any pe
Enables providing a backing file for the PC's ram. The file is specified by the
new -pcram-file option. The file is mmap'd shared, so the RAMBlock that it backs
doesn't need to be saved by vm_save / migration.
Signed-off-by: Peter Feiner
---
We have found this small feature very useful for expe
