From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Carl Karsten <carl@personnelware.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] format=raw,readonly errors
Date: Mon, 8 May 2017 17:00:51 +0100 [thread overview]
Message-ID: <20170508160051.GZ18871@redhat.com> (raw)
In-Reply-To: <bdb8ffb7-b9f0-242c-2bf9-3eb94530180b@redhat.com>
On Mon, May 08, 2017 at 11:32:12AM -0400, John Snow wrote:
>
>
> On 05/08/2017 10:15 AM, Carl Karsten wrote:
> > On Mon, May 8, 2017 at 3:51 AM, Markus Armbruster <armbru@redhat.com> wrote:
> >
> >> Carl Karsten <carl@personnelware.com> writes:
> >>
> >>> juser@gator:~/temp$ qemu-system-x86_64 -m 256 -display curses -drive
> >>> file=disk.cow -drive file=boot.img
> >>> WARNING: Image format was not specified for 'boot.img' and probing
> >> guessed
> >>> raw.
> >>> Automatically detecting the format is dangerous for raw images,
> >>> write operations on block 0 will be restricted.
> >>> Specify the 'raw' format explicitly to remove the restrictions.
> >>>
> >>> This is OK, as I don't want anything writing to that thing anyway. So to
> >>> get rid of the waring:
> >>>
> >>> juser@gator:~/temp$ qemu-system-x86_64 -drive
> >>> file=boot.img,format=raw,readonly qemu-system-x86_64: Can't use a
> >> read-only
> >>> drive
> >>> qemu-system-x86_64: Initialization of device ide-hd failed: Device
> >>> initialization failed.
> >>
> >> -drive without if=... creates an IDE disk[*]. IDE disks can't do
> >> read-only. Have you tried omitting ",readonly"?
> >>
> >
> >
> > omitting works, but my goal was for the drive to be read only.
> >
> >
>
> I don't think there's a way to make physical IDE drives "read only." I
> don't think there's any jumper settings or any of the like which can
> accomplish this.
You could use an IDE cdrom though, rather than an IDE disk, as that's
readonly from guest POV (we don't emulate a cd-writer).
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-05-08 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 4:28 [Qemu-devel] format=raw,readonly errors Carl Karsten
2017-05-08 8:51 ` Markus Armbruster
2017-05-08 14:15 ` Carl Karsten
2017-05-08 15:32 ` John Snow
2017-05-08 15:56 ` Carl Karsten
2017-05-08 16:29 ` Eric Blake
2017-05-08 16:33 ` Carl Karsten
2017-05-08 16:39 ` Eric Blake
2017-05-08 16:43 ` Eric Blake
2017-05-08 16:47 ` Max Reitz
2017-05-08 16:00 ` 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=20170508160051.GZ18871@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=carl@personnelware.com \
--cc=jsnow@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 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).