From: Michal Novotny <minovotn@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "'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:20:27 +0200 [thread overview]
Message-ID: <4C21FC0B.5020604@redhat.com> (raw)
In-Reply-To: <4C21F99E.7070807@redhat.com>
On 06/23/2010 02:10 PM, Paolo Bonzini wrote:
> On 06/23/2010 02:04 PM, Ian Jackson wrote:
>> Michal Novotny writes ("Re: [PATCH] Fix restore handling checks"):
>>> Are you saying that it's OK for administrators to violate the IDE specs
>>> and do it the way that is should never be done since this way it's not
>>> working on bare-metal systems ? This is the breach and it shouldn't be
>>> done this way so why to allow it? Shouldn't we care the code complies
>>> with the specifications to have it done the right way?
>>
>> The job of the programmer is to give effect to the wishes of the
>> users, not to comply with rules from elsewhere. If the wishes of the
>> users conflict with rules from elsewhere, including specs, then the
>> programmer should do what the user wants.
>
> Telling him that he wanted something that cannot be _emulated_
> accurately is also a possibility. But we can agree to disagree here
> and Michal can remove this part of the patch.
>
> Paolo
>
Well, just one correction to this Paolo. It can be emulated but the
emulation doesn't comply to the specifications and since it was never
supported at least for HVM guests prior to my patch to fix read-only
image handling so it shouldn't break anything so if it was not emulated
before the patch I sent 13 days ago why not to emulate/implement it the
right way? I don't see any reason to emulate it the wrong way since we
know the right way that's been implemented/fixed just 13 days ago - at
least for HVM guests. If users want to use read-only drives they can use
SCSI drives so what's the problem here?
Surely, I can remove this part of the patch but I'm just trying to tell
the readers of this thread that I don't see much point in having the
wrong implementation. I don't think users want to do it the wrong way
and I think they could understand that this is not supported and that
they should use SCSI drive definition for read-only drives instead.
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-06-23 12:20 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 [this message]
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
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=4C21FC0B.5020604@redhat.com \
--to=minovotn@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--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).