From: Michal Novotny <minovotn@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Re: [PATCH] Fix restore handling checks
Date: Wed, 23 Jun 2010 14:37:07 +0200 [thread overview]
Message-ID: <4C21FFF3.6020302@redhat.com> (raw)
In-Reply-To: <20100623133558.57991abf@lxorguk.ukuu.org.uk>
On 06/23/2010 02:35 PM, Alan Cox wrote:
> On Wed, 23 Jun 2010 13:29:56 +0200
> Michal Novotny<minovotn@redhat.com> wrote:
>
>
>> On 06/23/2010 01:27 PM, Ian Jackson wrote:
>>
>>> Paolo Bonzini writes ("Re: [PATCH] Fix restore handling checks"):
>>>
>>>
>>>> We tried to get that to work, and we could not really find a device
>>>> error that worked reliably in the guests. We often got infinite loops
>>>> on mount or little after that, on both Linux and Windows.
>>>>
>>>>
>>> That's fine. If the admins don't want that then they can use SCSI or
>>> PV or simply not tell the guest to write to the device.
>>>
>>> Disallowing the configuration entirely just because the error handling
>>> is suboptimal (but safe!) is not correct.
>>>
>>> Ian.
>>>
>>>
>> Why do you think so, Ian? This follows the IDE specifications to
>> disallow read-only IDE disks since the specs doesn't support IDE
>> read-only disks. The only read-only device being supported by IDE specs
>> is the CD-ROM device.
>>
> IDE (or more properly ATA) doesn't support CD-ROM either. ATAPI does, and
> it also supports other ATAPI devices with write protect including magneto
> optical and floppy.
>
>
>
Agreed Alan. This is right that ATAPI does. Nevertheless in IDE specs
it's about ATA and ATAPI. The read-only file systems are supported for
IDE drives only for floppy and tape media according to the linux kernel
source codes. Also, CD-ROM devices can be read-only but no other IDE
media, i.e. no IDE disks.
Michal
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
prev parent reply other threads:[~2010-06-23 12:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 16:30 [PATCH] Fix restore handling checks Michal Novotny
2010-06-21 18:04 ` Keir Fraser
2010-06-22 5:43 ` Michal Novotny
2010-06-22 6:11 ` Michal Novotny
2010-06-22 6:14 ` Keir Fraser
2010-06-22 6:17 ` Michal Novotny
2010-06-22 12:56 ` Michal Novotny
2010-06-22 14:10 ` Konrad Rzeszutek Wilk
2010-06-23 11:27 ` Michal Novotny
2010-06-22 20:46 ` Dan Magenheimer
2010-06-23 9:59 ` Michal Novotny
2010-06-23 11:21 ` Michal Novotny
2010-06-23 13:51 ` Dan Magenheimer
2010-06-23 14:14 ` Michal Novotny
2010-06-22 14:56 ` Ian Jackson
2010-06-23 11:19 ` Paolo Bonzini
2010-06-23 11:27 ` Ian Jackson
2010-06-23 11:29 ` Michal Novotny
2010-06-23 11:50 ` Ian Jackson
2010-06-23 11:54 ` Michal Novotny
2010-06-23 12:04 ` Ian Jackson
2010-06-23 12:10 ` Paolo Bonzini
2010-06-23 12:20 ` Michal Novotny
2010-06-23 12:20 ` Michal Novotny
2010-06-23 12:12 ` Michal Novotny
2010-06-23 12:33 ` Alan Cox
2010-06-23 15:12 ` George Dunlap
2010-06-23 16:26 ` Dan Magenheimer
2010-06-23 12:35 ` Alan Cox
2010-06-23 12:37 ` Michal Novotny [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=4C21FFF3.6020302@redhat.com \
--to=minovotn@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=pbonzini@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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).