This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp
Signed-off-by: Yoshiaki
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by:
Juan:
It's especailly important for ft to be a standalone thread, as it
may cause monitor to be blocked by network problems. what's your
schedule, maybe I can help some.
Yoshi:
in the following code:
+
+s-file = qemu_fopen_ops(s, ft_trans_put_buffer, ft_trans_get_buffer,
+
[ trimming cc to kvm qemu lists]
Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp wrote:
Juan Quintela wrote:
Yoshiaki Tamuratamura.yoshi...@lab.ntt.co.jp wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this
2011/2/24 Juan Quintela quint...@redhat.com:
[ trimming cc to kvm qemu lists]
Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp wrote:
Juan Quintela wrote:
Yoshiaki Tamuratamura.yoshi...@lab.ntt.co.jp wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by:
Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Could you explain
Juan Quintela wrote:
Yoshiaki Tamuratamura.yoshi...@lab.ntt.co.jp wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by:
2011/2/23 ya su suya94...@gmail.com:
Yoshi:
thanks for your explaining.
if you introduce a new stage as 3, I think stage 1 also need to change as
it will mark all pages dirty.
looking forward to your new patch update.
Unless there're strong comments from others, I won't put it in
Hi Green,
2011/2/21 ya su suya94...@gmail.com:
Yoshiaki:
I have one question about ram_save_live, during migration 3
stage(completation stage), it will call
cpu_physical_memory_set_dirty_tracking(0) to stop recording ram dirty pages.
at the end of migrate_ft_trans_connect function, it
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by:
12 matches
Mail list logo