From: Daniel Berrange <1875139@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1875139] Re: Domain fails to start when 'readonly' device not writable
Date: Mon, 27 Apr 2020 09:32:17 -0000 [thread overview]
Message-ID: <158797993725.17831.13213290853647082757.malone@wampee.canonical.com> (raw)
In-Reply-To: 158788589324.18152.6333525201430073299.malonedeb@wampee.canonical.com
> This issue is introduced in QEMU 4.2.0 (4.1.0 is working fine)
That's not neccessarily the case - with QEMU 4.2.0, libvirt switched
over to using the new -blockdev command line syntax. When you were
testing with 4.1.0, it would have been using the legacy -drive syntax.
So the change in behaviour is more likely related to the usage of
-blockdev, than any bug introduced in QEMU.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1875139
Title:
Domain fails to start when 'readonly' device not writable
Status in QEMU:
New
Bug description:
This issue is introduced in QEMU 4.2.0 (4.1.0 is working fine)
My root disk is a LVM2 volume thin snapshot that is marked as read-only
But when I try to start the domain (using virt-manager) I get the following error:
Error starting domain: internal error: process exited while connecting
to monitor: 2020-04-26T06:55:06.342700Z qemu-system-x86_64: -blockdev
{"driver":"host_device","filename":"/dev/vg/vmroot-20200425","aio":"native
","node-name":"libvirt-3-storage","cache":{"direct":true,"no-
flush":false},"auto-read-only":true,"discard":"unmap"} The device is
not writable: Permission denied
Changing the lvm snapshot to writeable allows me to start the domain.
(Making it changes possible during domain is running)
I don't think QEMU should fail when it can't open a (block) device when the read-only option is set.
(why is write access needed?)
Reproduce steps:
* Create LVM read-only volume (I don't think any data is needed)
* Create domain with read-only volume as block device
* Try to start the domain
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1875139/+subscriptions
next prev parent reply other threads:[~2020-04-27 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 7:24 [Bug 1875139] [NEW] Domain fails to start when 'readonly' device not writable A van Schie
2020-04-26 7:31 ` [Bug 1875139] " A van Schie
2020-04-27 9:09 ` Daniel Berrange
2020-04-27 9:32 ` Daniel Berrange [this message]
2020-04-27 12:09 ` A van Schie
2020-04-29 5:08 ` Peter Krempa
2020-09-20 6:37 ` A van Schie
2021-05-06 14:15 ` Thomas Huth
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=158797993725.17831.13213290853647082757.malone@wampee.canonical.com \
--to=1875139@bugs.launchpad.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).