[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <adazl58yuiy.fsf@roland-alpha.cisco.com>
Date: Thu, 24 Dec 2009 12:41:25 -0800
From: Roland Dreier <rdreier@...co.com>
To: Gleb Natapov <gleb@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
Gregory Haskins <gregory.haskins@...il.com>,
Avi Kivity <avi@...hat.com>, kvm@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
netdev@...r.kernel.org,
"alacrityvm-devel\@lists.sourceforge.net"
<alacrityvm-devel@...ts.sourceforge.net>
Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33
> > This is Linux virtualization, where _both_ the host and the guest source code
> > is fully known, and bugs (if any) can be found with a high degree of
> It may sound strange but Windows is very popular guest and last I
> checked my HW there was no Windows sources there, but the answer to that
> is to emulate HW as close as possible to real one and then closed source
> guests will not have a reason to be upset.
>
> > determinism. This is Linux where the players dont just vanish overnight, and
> > are expected to do a proper job.
And without even getting into closed/proprietary guests, virt is useful
for testing/developing/deploying many free OSes, eg FreeBSD, NetBSD,
OpenBSD, Hurd, <random research OS>, etc. Not to mention just wanting a
stable [virtual] platform to run <old enterprise Linux distro> on. So
having a virtual platform whose interface doesn't change very often or
very much has a lot of value at least in avoiding churn in guest OSes.
- R.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists