[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] early_savevm
From: |
Stefano Stabellini |
Subject: |
Re: [Qemu-devel] early_savevm |
Date: |
Tue, 13 Dec 2011 13:59:33 +0000 |
User-agent: |
Alpine 2.00 (DEB 1167 2008-08-23) |
On Tue, 13 Dec 2011, Jan Kiszka wrote:
> On 2011-12-13 12:55, Stefano Stabellini wrote:
> > On Mon, 12 Dec 2011, Stefano Stabellini wrote:
> >>> Really, I think this is something inherently incompatible with the
> >>> current memory API. If Xen has this unfixable special "requirement"
> >>> (it's rather a design issue IMHO), adjust the API and adapt all devices.
> >>> Hot-fixing only a single one this way is no good idea long term.
> >>
> >> Fair enough.
> >> What about introducing a type of savevm state that is going to be
> >> restored before machine->init?
> >> This way we could save and restore our physmap and we could handle
> >> memory maps and allocations transparently.
> >>
> >
> > A bit more context to my suggestion:
> >
> > - we open the save state file and check the magic number and the
> > version number before machine->init();
> >
> > - we add a new set of entries to the save state file that contains
> > early_savevm functions: they are called before machine->init();
> >
> > - after reaching the end of the early_savevm functions we stop parsing
> > the save state file and we call machine->init();
> >
> > - after machine->init() is completed we continue parsing the save state
> > file as usual.
>
> Hmm, just wondering if another use case for this early incoming
> migration step is transferring the machine configuration so that the
> receiver need not worry about synchronizing it out of band. That may
> help motivating this likely not trivial change.
Actually I was thinking the same thing. I am sure that if we had such a
thing as early_savevm, a few other use cases will certainly show up.
- Re: [Qemu-devel] [PATCH V2 4/5] xen: Change memory access behavior during migration., (continued)
- [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Anthony PERARD, 2011/12/09
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Jan Kiszka, 2011/12/10
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Stefano Stabellini, 2011/12/12
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Jan Kiszka, 2011/12/12
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Stefano Stabellini, 2011/12/12
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Jan Kiszka, 2011/12/12
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Stefano Stabellini, 2011/12/12
- [Qemu-devel] early_savevm (was: [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen.), Stefano Stabellini, 2011/12/13
- Re: [Qemu-devel] early_savevm, Jan Kiszka, 2011/12/13
- Re: [Qemu-devel] early_savevm,
Stefano Stabellini <=
- Re: [Qemu-devel] early_savevm, Avi Kivity, 2011/12/18
- Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Avi Kivity, 2011/12/18
Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen., Stefano Stabellini, 2011/12/12
[Qemu-devel] [PATCH V2 2/5] xen mapcache: Check if a memory space has moved., Anthony PERARD, 2011/12/09