I choose b)
在2014年08月01 11时15分, "Gareth"写道:
Hi all
What does '-enable-kvm' option mean? I have heard two versions of answers:
a) guest OS would have /dev/kvm device and which could help vm in guest OS
(nested vm)
b) use /dev/kvm and intel-vt on host OS which could help vm run more fast
Calling dma_bdrv_unmap() twice is not necessary and may cause
potential problems if some code changes.
Signed-off-by: Jules Wang
---
dma-helpers.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/dma-helpers.c b/dma-helpers.c
index 5f421e9..53cbe92 100644
--- a/dma
ft migration.
* receiver: look for the signature:
QEMU_VM_EOF_MAGIC + QEMU_VM_FILE_MAGIC_FT(64bit total)
which indicates the end of one migration.
--
Jules Wang (4):
Curling: add doc
Curling: cmdline interface.
Curling: the sender
Curling: the receiver
: Jules Wang
---
include/migration/qemu-file.h | 1 +
include/sysemu/sysemu.h | 2 +
migration.c | 22 --
savevm.c | 158 --
4 files changed, 173 insertions(+), 10 deletions(-)
diff --git a/include
previous
migration.
Signed-off-by: Jules Wang
---
arch_init.c | 25 -
include/sysemu/sysemu.h | 3 ++-
migration.c | 25 +++--
savevm.c| 20
4 files changed, 61 insertions(+), 12 deletions
Curling provides fault tolerant mechanism for KVM.
For more info, see 'doc/curling.txt'.
Signed-off-by: Jules Wang
---
docs/curling.txt | 51 +++
1 file changed, 51 insertions(+)
create mode 100644 docs/curling.txt
diff --git a/docs/c
Add an option '-f' to migration cmdline.
Indicating whether to enable fault tolerant or not.
Signed-off-by: Jules Wang
---
hmp-commands.hx | 10 ++
hmp.c | 3 ++-
include/migration/migration.h | 1 +
migration.c | 3
total)
which indicates the end of one migration.
--
Jules Wang (4):
Curling: add doc
Curling: cmdline interface.
Curling: the sender
Curling: the receiver
arch_init.c | 25 --
docs/curling.txt | 51
hmp-commands.hx
: Jules Wang
---
include/migration/qemu-file.h | 1 +
include/sysemu/sysemu.h | 2 +
migration.c | 22 --
savevm.c | 158 --
4 files changed, 173 insertions(+), 10 deletions(-)
diff --git a/include
previous
migration.
Signed-off-by: Jules Wang
---
arch_init.c | 25 -
include/sysemu/sysemu.h | 3 ++-
migration.c | 25 +++--
savevm.c| 20
4 files changed, 61 insertions(+), 12 deletions
Curling provides fault tolerant mechanism for KVM.
For more info, see 'doc/curling.txt'.
Signed-off-by: Jules Wang
---
docs/curling.txt | 51 +++
1 file changed, 51 insertions(+)
create mode 100644 docs/curling.txt
diff --git a/docs/c
Add an option '-f' to migration cmdline.
Indicating whether to enable fault tolerant or not.
Signed-off-by: Jules Wang
---
hmp-commands.hx | 11 +++
hmp.c | 3 ++-
include/migration/migration.h | 1 +
migration.c | 3
Curling provides fault tolerant mechanism for KVM.
For more info, see 'doc/curling.txt'.
Signed-off-by: Jules Wang
---
docs/curling.txt | 52
1 file changed, 52 insertions(+)
create mode 100644 docs/curling.txt
diff --git a/docs/c
previous
migration.
Signed-off-by: Jules Wang
---
arch_init.c | 18 +-
migration.c | 23 ++-
savevm.c| 4
3 files changed, 39 insertions(+), 6 deletions(-)
diff --git a/arch_init.c b/arch_init.c
index e47e139..5d006f6 100644
--- a/arch_init.c
+++ b
the receiver is prefectching data, how does it know where is the EOF of
one migration?
Currently, we use a magic number 0xfeedcafe to indicate the EOF.
Any better solutions?
2. How to reduce the overhead entailed by vm_stop and iothread locks?
Any solutions other than sleeping?
--
Jules Wan
: Jules Wang
---
include/migration/qemu-file.h | 1 +
include/sysemu/sysemu.h | 1 +
migration.c | 22 --
savevm.c | 154 --
4 files changed, 168 insertions(+), 10 deletions(-)
diff --git a/include/migration
Parse the word 'curling' when incoming/outgoing migration is
starting. So we know whether to enable fault tolerant or not.
Signed-off-by: Jules Wang
---
include/migration/migration.h | 2 ++
migration.c | 16
2 files changed, 18 insertions(+)
di
17 matches
Mail list logo
