From: Carl Karsten <carl@personnelware.com>
To: Eric Blake <eblake@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] format=raw,readonly errors
Date: Mon, 8 May 2017 11:33:40 -0500 [thread overview]
Message-ID: <CADmzSSgN6+gK2rhcpiYu7y_gG3UT7oL92Q4zG+GQVoqGbVGKXg@mail.gmail.com> (raw)
In-Reply-To: <0456ed7c-c465-6e6b-77a2-8be37e0e6ae2@redhat.com>
On Mon, May 8, 2017 at 11:29 AM, Eric Blake <eblake@redhat.com> wrote:
> On 05/08/2017 10:56 AM, Carl Karsten wrote:
>
> >>>>> 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.
>
> > "write operations on block 0 will be restricted."
> >
> > Is there a way to explicitly enable that?
>
> Yes. Pass format=raw at the right place (in other words, instead of
> getting the 'raw' format driver by default, explicitly mentioning that
> you KNOW you want the 'raw' format driver is enough to shut up the
> warning).
>
according to the warning: "Specify the 'raw' format explicitly to remove
the restrictions."
I want the restriction.
format=raw, (write operations on block 0)=restricted
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
>
>
--
Carl K
next prev parent reply other threads:[~2017-05-08 16:34 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 [this message]
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
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=CADmzSSgN6+gK2rhcpiYu7y_gG3UT7oL92Q4zG+GQVoqGbVGKXg@mail.gmail.com \
--to=carl@personnelware.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.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).