From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: lmr@redhat.com, amit.shah@redhat.com, dgilbert@redhat.com,
quintela@redhat.com
Subject: [Qemu-devel] [PATCH v2 1/3] migration: Read JSON VM description on incoming migration
Date: Mon, 23 Feb 2015 13:56:41 +0100 [thread overview]
Message-ID: <1424696203-76895-2-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1424696203-76895-1-git-send-email-agraf@suse.de>
One of the really nice things about the VM description format is that it goes
over the wire when live migration is happening. Unfortunately QEMU today closes
any socket once it sees VM_EOF coming, so we never give the VMDESC the chance to
actually land on the wire.
This patch makes QEMU read the description as well. This way we ensure that
anything wire tapping us in between will get the chance to also interpret the
stream.
Along the way we also fix virt tests that assume that number_bytes_sent on the
sender side is equal to number_bytes_read which was true before the VMDESC
patches and is true again with this patch.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
v1 -> v2:
- read in small chunks
---
savevm.c | 22 +++++++++++++++++++++-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/savevm.c b/savevm.c
index 8040766..1b78654 100644
--- a/savevm.c
+++ b/savevm.c
@@ -929,6 +929,7 @@ int qemu_loadvm_state(QEMUFile *f)
uint8_t section_type;
unsigned int v;
int ret;
+ int file_error_after_eof = -1;
if (qemu_savevm_state_blocked(&local_err)) {
error_report("%s", error_get_pretty(local_err));
@@ -1034,6 +1035,24 @@ int qemu_loadvm_state(QEMUFile *f)
}
}
+ file_error_after_eof = qemu_file_get_error(f);
+
+ /*
+ * Try to read in the VMDESC section as well, so that dumping tools that
+ * intercept our migration stream have the chance to see it.
+ */
+ if (qemu_get_byte(f) == QEMU_VM_VMDESCRIPTION) {
+ uint32_t size = qemu_get_be32(f);
+ uint8_t *buf = g_malloc(0x1000);
+
+ while (size > 0) {
+ uint32_t read_chunk = MIN(size, 0x1000);
+ qemu_get_buffer(f, buf, read_chunk);
+ size -= read_chunk;
+ }
+ g_free(buf);
+ }
+
cpu_synchronize_all_post_init();
ret = 0;
@@ -1045,7 +1064,8 @@ out:
}
if (ret == 0) {
- ret = qemu_file_get_error(f);
+ /* We may not have a VMDESC section, so ignore relative errors */
+ ret = file_error_after_eof;
}
return ret;
--
1.7.12.4
next prev parent reply other threads:[~2015-02-23 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:56 [Qemu-devel] [PATCH v2 0/3] migration: Fixups for VMDESC submission Alexander Graf
2015-02-23 12:56 ` Alexander Graf [this message]
2015-03-04 11:50 ` [Qemu-devel] [PATCH v2 1/3] migration: Read JSON VM description on incoming migration Dr. David Alan Gilbert
2015-02-23 12:56 ` [Qemu-devel] [PATCH v2 2/3] migration: Allow to suppress vmdesc submission Alexander Graf
2015-02-23 12:56 ` [Qemu-devel] [PATCH v2 3/3] pc: Disable vmdesc submission for old machines Alexander Graf
2015-03-04 11:53 ` Dr. David Alan Gilbert
2015-03-05 13:24 ` [Qemu-devel] [PATCH v2 0/3] migration: Fixups for VMDESC submission Lucas Meneghel Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1424696203-76895-2-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).