From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Avoid permanently disabled QEMU monitor when UNIX migration fails
Date: Fri, 11 Dec 2009 20:56:01 +0000 [thread overview]
Message-ID: <20091211205601.GK21297@redhat.com> (raw)
In-Reply-To: <1260564571-28005-1-git-send-email-berrange@redhat.com>
On Fri, Dec 11, 2009 at 08:49:31PM +0000, Daniel P. Berrange wrote:
> If a UNIX migration command is attempt to a UNIX socket which does
> not exist, then the monitor is suspended, but never resumed. This
> prevents any further use of the monitor
>
> * migration-unix.c: Only call migrate_fd_monitor_suspend() once
> connected to the UNIX socket.
Sorry, forgot to include the signed-off tag with this patch, so will
resend.
FYI, the test case here is simply
(qemu) migrate unix:/tmp/doesnotexist
migration failed
...now hung, no prompt returns..
There is also similar kind of problem with exec migration, but I have not
been able to figure out where the problem lies for that one. I suspect
something is not dealing with errors properly in the buffered file code.
If someone fancies investigating the exec: issue, the test case is simply
to run exec with a command that fails, eg give invalid syntax for one of
its args. I discovered the problem when i did a simple typo with dd
(qemu) migrate "exec:dd bs-1m of=/tmp/file"
dd: unrecognized operand `bs-1m'
Try `dd --help' for more information.
...now hung, no prompt returns..
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2009-12-11 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 20:49 [Qemu-devel] [PATCH] Avoid permanently disabled QEMU monitor when UNIX migration fails Daniel P. Berrange
2009-12-11 20:56 ` Daniel P. Berrange [this message]
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=20091211205601.GK21297@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.