[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 589315] Re: qemu: Improve error reporting when migrati
|
From: |
Thomas Huth |
|
Subject: |
[Qemu-devel] [Bug 589315] Re: qemu: Improve error reporting when migration can't connect |
|
Date: |
Fri, 16 Feb 2018 23:16:35 -0000 |
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/589315
Title:
qemu: Improve error reporting when migration can't connect
Status in QEMU:
Fix Released
Bug description:
Tested with upstream qemu as of Jun 3 2010
If the source qemu instance can't connect to the migration destination (say
there is no listening QEMU instance, or port is blocked by a firewall), all we
get is info migrate -> Migration status: failed. This is all we have to report
back to libvirt users if their firewall is misconfigured, which is crappy.
Ideally, if we can't connect, migration would fail immediately with a relevant
message and strerror(). More info from 'info migrate' would be nice too, no
idea how this will play with QMP though.
As a slightly related issue, try entering
migrate tcp:127.0.0.0:6000
We get a 'migration failed' error, and then the monitor hangs!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/589315/+subscriptions