WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] RE: XEN and Windows Guests in critical environment(hospital)

To: "Ligesh" <myself@xxxxxxxxxx>, "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
Subject: [Xen-users] RE: XEN and Windows Guests in critical environment(hospital)
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 24 Jun 2007 14:54:53 +1000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Jordi Espasa Clofent <sistemes.llistes@xxxxxxxxxxxxx>
Delivery-date: Sat, 23 Jun 2007 21:53:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070623220624.GA12722@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <467CFE8F.9010501@xxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01166BD7@trantor> <20070623131951.GA6011@xxxxxxxxxx> <467D5A35.2040001@xxxxxxxxx> <20070623201616.GA11755@xxxxxxxxxx> <467D942F.4040106@xxxxxxxxx> <20070623220624.GA12722@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ace14MGBBRJMC2rlRWefQziQIJTGHgAOXI8Q
Thread-topic: XEN and Windows Guests in critical environment(hospital)
> On Sat, Jun 23, 2007 at 10:44:15PM +0100, Nico Kadel-Garcia wrote:
> > Ligesh wrote:
> >
> > > For the app vendor, it is irrelevant if you are running it inside
xen
> or
> > > on baremetal. Even for windows it doesn't matter, so for something
> that
> > > sits so high up in the application chain, why would you want to
> > > complicate and confuse the easily confused people by bringing in
> > > information about a software about which they probably haven't
heard
> about
> > >
> > Nonesense. I've *been* the vendor, and it makes a big difference
what
> > kernel you're using. Lying to them just confuses the issues, and
I've
> > run into *that*, too.
> 
>  We are talking about application written in dotnet. That's pretty
much 3
> layers above the kernel. I had very clearly stated that if you are
running
> kernel level apps, then it is better you stick with real hardware, or
even
> if you are migrating, you get the proper experts to do it.
> 
>  We are talking about pure user-level applications, like the one in
the
> Original Post--a dotnet medical app --which would mostly be dealing
with
> accounting and database. So obviously, it has nothing to do with Xen
or
> the hardware. If you are running apps that has device drivers, then
the
> situation is completely different, but that's obvious.

What you are saying is probably correct, assuming as you say that the
applications in question are not data acquisition processes or anything
requiring low level drivers. But the point you aren't getting is about
support, and what happens when something goes wrong. 

I made the assumption that the word 'critical' used in the original post
meant that lives could depend on it, eg if the application in question
is responsible for scheduling medical test and sending results to the
right person. In my experience the platform for 'critical' applications
like this is that they are sized and specified very tightly by the
vendor, and if you have ever been in the role of support for such a
thing you'll understand why.

So I agree with you that the application will almost certainly work and
work perfectly, but everyone is very sensitive about legal
responsibilities these days, and if someone died and it was determined
that a computer failure caused the results of a medical test to be lost
or delayed and that that was a contributing factor to their death, and
it turns out that you used an unsupported system configuration to run
the software on, then take a guess what happens next - the fact that it
wasn't Xen or VMWare's fault will have nothing to do with the outcome of
the inquiry...

James


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users