aboutsummaryrefslogtreecommitdiffstats
path: root/hw/hw.h
diff options
context:
space:
mode:
authorChris Lalancette <clalance@redhat.com>2009-05-25 16:38:23 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2009-05-27 09:46:07 -0500
commit8a43b1ea7fd02a8e9a5c5ef58017b1bd059663bb (patch)
tree267c6df69d20628c38875715e1f8c97551b4834b /hw/hw.h
parentc16b5a2ca0b186de618654a576bdad9cdd2d1ab2 (diff)
Allow monitor interaction when using migrate -exec
All, I've recently been playing around with migration via exec. Unfortunately, when starting the incoming qemu process with "-incoming exec:cmd", it suffers the same problem that -incoming tcp used to suffer; namely, that you can't interact with the monitor until after the migration has happened. This causes problems for libvirt usage of -incoming exec, since libvirt expects to be able to access the monitor ahead of time. This fairly simple patch allows you to access the monitor both before and after the migration has completed using exec. (note: developed/tested with qemu-kvm, but applies perfectly fine to qemu) Signed-off-by: Chris Lalancette <clalance@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'hw/hw.h')
-rw-r--r--hw/hw.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/hw/hw.h b/hw/hw.h
index a3f5717b3..c83580073 100644
--- a/hw/hw.h
+++ b/hw/hw.h
@@ -51,6 +51,7 @@ QEMUFile *qemu_fopen(const char *filename, const char *mode);
QEMUFile *qemu_fopen_socket(int fd);
QEMUFile *qemu_popen(FILE *popen_file, const char *mode);
QEMUFile *qemu_popen_cmd(const char *command, const char *mode);
+int qemu_popen_fd(QEMUFile *f);
void qemu_fflush(QEMUFile *f);
int qemu_fclose(QEMUFile *f);
void qemu_put_buffer(QEMUFile *f, const uint8_t *buf, int size);