On Thu, Jul 31, 2008 at 12:27:43PM -0500, Anthony Liguori wrote:
Chris Lalancette wrote:
We've been trying to plumb libvirt to do KVM migration. One of the
stumbling
blocks we are running into, however, is that libvirt expects to be able to
use
the Qemu monitor both before and after
Daniel P. Berrange wrote:
An accept trick only handles the TCP case though. I know this was Chris'
example that we're currently using, but we intend to switch to passing
an open file descriptor instead, and proxying the data via a secure
channel instead of the plain tcp, or builtin SSH
Daniel P. Berrange wrote:
@@ -9673,11 +9675,16 @@ int main(int argc, char **argv)
if (incoming) {
int rc;
-rc = migrate_incoming(incoming);
-if (rc != 0) {
-fprintf(stderr, Migration failed rc=%d\n, rc);
-exit(rc);
-}
+
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on both the
source and destination nodes. After migration has taken place
On Thu, Jul 31, 2008 at 04:50:51PM +0200, Chris Lalancette wrote:
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on
Chris Lalancette wrote:
We've been trying to plumb libvirt to do KVM migration. One of the stumbling
blocks we are running into, however, is that libvirt expects to be able to use
the Qemu monitor both before and after migration has taken place, on both the
source and destination nodes. After
