diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:24:58 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:27:06 +0000 |
| commit | 33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch) | |
| tree | 406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/589315 | |
| parent | adedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff) | |
| download | qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip | |
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/589315')
| -rw-r--r-- | results/scraper/launchpad-without-comments/589315 | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/589315 b/results/scraper/launchpad-without-comments/589315 new file mode 100644 index 000000000..29d2ddb31 --- /dev/null +++ b/results/scraper/launchpad-without-comments/589315 @@ -0,0 +1,18 @@ +qemu: Improve error reporting when migration can't connect + +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! \ No newline at end of file |