Hello everyone,
so basically this is a tradeoff between not having a long latency for
the migration to succeed and reducing the total network traffic (and
CPU load) in the migration source and destination and reducing the
memory footprint a bit, by adding an initial latency to the memory
accesses
On 08/09/2011 05:33 AM, Isaku Yamahata wrote:
On Mon, Aug 08, 2011 at 03:38:54PM +0300, Avi Kivity wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to
On Wed, Aug 10, 2011 at 04:55:32PM +0300, Avi Kivity wrote:
On 08/09/2011 05:33 AM, Isaku Yamahata wrote:
On Mon, Aug 08, 2011 at 03:38:54PM +0300, Avi Kivity wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can get better feedback on its design/implementation approach
On Mon, Aug 8, 2011 at 4:24 AM, Isaku Yamahata yamah...@valinux.co.jp wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
I'm curious if this approach is compatible with asynchronous page
faults? The idea there was to tell the guest
On 08/08/2011 12:20, Dor Laor wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can get better feedback on
On Mon, Aug 08, 2011 at 10:38:35AM +0100, Stefan Hajnoczi wrote:
On Mon, Aug 8, 2011 at 4:24 AM, Isaku Yamahata yamah...@valinux.co.jp wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
I'm curious if this approach is compatible
* What's is postcopy livemigration
It is is yet another live migration mechanism for Qemu/KVM, which
implements the migration technique known as postcopy or lazy
migration. Just after the migrate command is invoked, the execution
host of a VM is instantaneously switched to a destination host.
On 08/08/2011 01:59 PM, Nadav Har'El wrote:
* What's is postcopy livemigration
It is is yet another live migration mechanism for Qemu/KVM, which
implements the migration technique known as postcopy or lazy
migration. Just after the migrate command is invoked, the execution
host of a VM is
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can get better feedback on its design/implementation approach
On 08/08/2011 04:20 AM, Dor Laor wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can get better feedback
On 08/08/2011 03:32 PM, Anthony Liguori wrote:
On 08/08/2011 04:20 AM, Dor Laor wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it
On 08/08/2011 10:11 AM, Dor Laor wrote:
On 08/08/2011 03:32 PM, Anthony Liguori wrote:
On 08/08/2011 04:20 AM, Dor Laor wrote:
That's terrific (nice video also)!
Orit and myself had the exact same idea too (now we can't patent it..).
Advantages:
- No down time due to memory copying.
But
On 08/08/2011 06:29 PM, Anthony Liguori wrote:
- Efficient, reduce needed traffic no need to re-send pages.
It's not quite that simple. Post-copy needs to introduce a protocol
capable of requesting pages.
Just another subsection.. (kidding), still it shouldn't be too
complicated, just an
On 08/08/2011 07:47 AM, Dor Laor wrote:
On 08/08/2011 01:59 PM, Nadav Har'El wrote:
* What's is postcopy livemigration
It is is yet another live migration mechanism for Qemu/KVM, which
implements the migration technique known as postcopy or lazy
migration. Just after the migrate command is
On 08/08/2011 11:52 AM, Cleber Rosa wrote:
On 08/08/2011 07:47 AM, Dor Laor wrote:
On 08/08/2011 01:59 PM, Nadav Har'El wrote:
* What's is postcopy livemigration
It is is yet another live migration mechanism for Qemu/KVM, which
implements the migration technique known as postcopy or lazy
On 08/08/2011 10:36 AM, Avi Kivity wrote:
On 08/08/2011 06:29 PM, Anthony Liguori wrote:
- Efficient, reduce needed traffic no need to re-send pages.
It's not quite that simple. Post-copy needs to introduce a protocol
capable of requesting pages.
Just another subsection.. (kidding), still
On 08/08/2011 06:59 PM, Anthony Liguori wrote:
On 08/08/2011 10:36 AM, Avi Kivity wrote:
On 08/08/2011 06:29 PM, Anthony Liguori wrote:
- Efficient, reduce needed traffic no need to re-send pages.
It's not quite that simple. Post-copy needs to introduce a protocol
capable of requesting
On 08/08/2011 04:40 AM, Yaniv Kaul wrote:
On 08/08/2011 12:20, Dor Laor wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
Design/Implementation
=
The basic idea of postcopy livemigration is to use a sort of distributed
shared memory between the migration source and
On Mon, Aug 08, 2011 at 10:47:09PM +0300, Dor Laor wrote:
On 08/08/2011 06:59 PM, Anthony Liguori wrote:
On 08/08/2011 10:36 AM, Avi Kivity wrote:
On 08/08/2011 06:29 PM, Anthony Liguori wrote:
- Efficient, reduce needed traffic no need to re-send pages.
It's not quite that simple.
On Mon, Aug 08, 2011 at 03:38:54PM +0300, Avi Kivity wrote:
On 08/08/2011 06:24 AM, Isaku Yamahata wrote:
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can
This mail is on Yabusame: Postcopy Live Migration for Qemu/KVM
on which we'll give a talk at KVM-forum.
The purpose of this mail is to letting developers know it in advance
so that we can get better feedback on its design/implementation approach
early before our starting to implement it.
22 matches
Mail list logo
