On Sat, Jun 23, 2007 at 06:36:53PM +0100, Nico Kadel-Garcia wrote:
> Ligesh wrote:
> > As for virtualization itself, you need to check the stability of Xen
> > itself, which has only been tagged stable recently. Virtualization makes
> > it easier to manage, and overall I would say increases the reliability,
> > simply on account of being easier to keep track of, and also take
> > backups, migrate in case of hardware failure etc.
> >
> Well, sending them a "sysreport" output might be a good hint, because it
> will name the Xen kernel. In fact, why would you want to lie about it?
> Not telling a vendor your actual setup is begging for them to suffer.
>
NO you need not. Do you tell your application vendor what CPU you are running
on? Or what motherboard you are using? Xen is transparent. That's the whole
point; otherwise I don't think it is useful. Xen should be treated as yet
another hardware, and I don't think it is necessary to tell anyone about it,
unless of course, you are running a software that explicitly deals with
hardware, in which situation you should probably not run Xen, unless you know
what you are doing.
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?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home