qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Frédéric Dreier" <frederic.dreier@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] read-only IDE drives in qemu
Date: Fri, 5 Aug 2011 08:14:25 +0200	[thread overview]
Message-ID: <CAA5b1EtwTtpTEDjYfqJuvDWbOP0kGet1O2GCnrtksuTpooS2DA@mail.gmail.com> (raw)
In-Reply-To: <m362mdrqcb.fsf@blackfin.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]

Hi,

Now I understand why read-only IDE support was dropped. I will investigate
if I could use read-only virtio disks for my purpose.

Thank you for your response and for the hints,

Best regards,

Frederic



Le 4 août 2011 20:20, Markus Armbruster <armbru@redhat.com> a écrit :

> Frédéric Dreier <frederic.dreier@gmail.com> writes:
>
> > Hi,
> >
> > We are updating some machines in our server farm to Ubuntu natty (KVM /
> > Opennebula cluster). Since then we used to have some VM with shared
> > read-only IDE disks to mirror software repositories through several
> isolated
> > networks (one-way data diode).
> >
> > The updated qemu does not allow it. It failed to start the VM with a
> 'Can't
> > use a read-only drive' error. After checking in the qemu git, it seems
> that
> > this has been forbidden by this commit
> > '7aa9c811ca0761918a0252d0f923a80224953fa6' :
> >
> > -----------------------------
> > Author: Markus Armbruster <armbru@redhat.com>  2010-06-28 19:10:36
> > Committer: Kevin Wolf <kwolf@redhat.com>  2010-07-06 17:05:50
> > Parent: c4d74df726cb3791d9f1661b58067df5608b627e (ide: Make
> ide_init_drive()
> > return success)
> > Child:  dce9e92834cc4f962e547cae46b73ca559d05b0c (ide: Reject invalid CHS
> > geometry)
> > Branches: master, remotes/origin/master, remotes/origin/stable-0.13,
> > remotes/origin/stable-0.14, remotes/origin/stable-0.15
> > Follows: v0.12.0-rc0
> > Precedes: v0.13.0-rc0
> >
> >     ide: Reject readonly drives unless CD-ROM
> >
> >     drive_init() doesn't permit option readonly for if=ide, but that's
> >     worthless: we get it via if=none and -device.
> >
> >     Signed-off-by: Markus Armbruster <armbru@redhat.com>
> >     Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > -----------------------------
> >
> > I do not understand the comment, if there is a workaround or if it
> something
> > to avoid.
> >
> > May you help me to understand it?
>
> Real IDE disks can't do read-only.
>
> -drive if=ide rejects readonly unless you also supply media=cdrom, which
> turns the drive into a CD-ROM.
>
> When -drive if=none got added, we inadvertedly created a loophole: the
> reject covered only if=ide, not if=none when used for a -device
> ide-drive.  The commit you quoted fixed that.
>
> Can you use an IDE CD-ROM instead?  Or virtio-blk-pci?
>

[-- Attachment #2: Type: text/html, Size: 3133 bytes --]

      reply	other threads:[~2011-08-05  6:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 17:52 [Qemu-devel] read-only IDE drives in qemu Frédéric Dreier
2011-08-04 18:20 ` Markus Armbruster
2011-08-05  6:14   ` Frédéric Dreier [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=CAA5b1EtwTtpTEDjYfqJuvDWbOP0kGet1O2GCnrtksuTpooS2DA@mail.gmail.com \
    --to=frederic.dreier@gmail.com \
    --cc=armbru@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).