From: Christopher Pereira <kripper@imatronix.cl>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Reopen file descriptors on 'cont' command
Date: Fri, 06 Mar 2015 14:43:39 -0300 [thread overview]
Message-ID: <54F9E74B.4030708@imatronix.cl> (raw)
In-Reply-To: <20150306171950.GE2431@stefanha-thinkpad.redhat.com>
On 06-03-2015 14:19, Stefan Hajnoczi wrote:
> On Wed, Feb 25, 2015 at 09:32:18PM -0300, Christopher Pereira wrote:
>> Does qemu reopen files on a 'cont' command?
>>
>> When working with images on a gluster volume, file descriptors may get into
>> a bad state because of network timeouts, remounting a share, etc...and
>> reinitializing file descriptors may be usefull to get paused VMs up again.
>>
>> Related BZ:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1058300
> No, QEMU doesn't reopen file descriptors.
>
> This can be challenging because QEMU supports file descriptor passing,
> which is used when the QEMU process is isolated using SELinux so it
> cannot open files itself. Reopening would require new file descriptors
> passed in from the management tool.
Thanks Stefan.
I confirmed that libvirtd is not passing a FD to QEMU, but an image path.
Is QEMU reopening this image file when the VM is resumed?
QEMU must check if the FD (initialized by QEMU) is still valid,
especially after resuming a paused VM.
prev parent reply other threads:[~2015-03-06 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 0:32 [Qemu-devel] Reopen file descriptors on 'cont' command Christopher Pereira
2015-03-06 17:19 ` Stefan Hajnoczi
2015-03-06 17:43 ` Christopher Pereira [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=54F9E74B.4030708@imatronix.cl \
--to=kripper@imatronix.cl \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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.