From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] block-commit & dropping privs
Date: Fri, 27 Mar 2015 12:07:03 +0300 [thread overview]
Message-ID: <55151DB7.3090200@msgid.tls.msk.ru> (raw)
Hello.
I tried to experiment with block-commit command, which propagates
changes accumulated in an overlay (qcow2) block image file back to
the base image file.
And immediately faced a problem. All my VMs are run chrooted into
an empty dir and with low-priv user (using -runsa and -chroot options,
initially started as root). Ofcourse this low-priv qemu process
can't open the base image anymore, because it doesn't have the
necessary permissions and because the base file is inaccessible
within the chroot.
So I wonder if we can avoid reopening the base img by always opening
it read-write (using a command-line option), does it make sense?
Or maybe there's some other possible solution to this, for example,
passing in a filedescriptor for the new base img over a unix socket?
Thanks,
/mjt
next reply other threads:[~2015-03-27 9:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:07 Michael Tokarev [this message]
2015-03-27 14:49 ` [Qemu-devel] block-commit & dropping privs Eric Blake
2015-03-27 15:36 ` Michael Tokarev
2015-03-27 17:12 ` Eric Blake
2015-03-30 15:36 ` Kevin Wolf
2015-04-01 9:26 ` Michael Tokarev
2015-04-01 9:54 ` Michael Tokarev
2015-04-01 12:34 ` Kevin Wolf
2015-04-02 10:58 ` Michael Tokarev
2015-04-02 11:24 ` Kevin Wolf
2015-04-02 12:04 ` Michael Tokarev
2015-04-02 13:07 ` Eric Blake
2015-04-03 4:28 ` Jeff Cody
2015-04-03 19:49 ` Eric Blake
2015-04-03 19:57 ` Jeff Cody
2015-04-02 13:19 ` Kevin Wolf
2015-04-06 15:37 ` Michael Tokarev
2015-04-07 9:24 ` Kevin Wolf
2015-04-03 3:59 ` Jeff Cody
2015-04-07 9:18 ` Kevin Wolf
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=55151DB7.3090200@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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.