From: Dave Feustel <dfeustel@mindspring.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: Vertualization of Unmodified Operating Systems
Date: Sat, 15 Apr 2006 20:30:02 -0500 [thread overview]
Message-ID: <200604152030.03386.dfeustel@mindspring.com> (raw)
In-Reply-To: <pan.2006.04.15.22.53.58.12262@us.ibm.com>
On Saturday 15 April 2006 17:53, Anthony Liguori wrote:
> On Sat, 15 Apr 2006 17:39:10 -0500, Dave Feustel wrote:
>
> > AMD Pacifica and Intel's VT make possible the virtualization of unmodified
> > operating systems. Is it still necessary to add code to the hypervisor to
> > support specific operating systems, or can Xen, as written, support any
> > arbitrary OS that successfully boots on a PC? (I'm thinking of the BSDs
> > here).
>
> This sort of thing has been addressed here before.
I know this and I appreciate your patience. I definitely don't
pick things up or figure things out as quickly now as I did
when I was younger.
> While theoritically,
> VT and SVM ought to allow any OS to run under Xen, in practice, if an OS
> hasn't been tested as a guest under Xen, it is likely to turn up some bugs
> or incompleteness. Over time, this will certainly be a less of an issue.
>
> The problem has to do with the fact that different OS's will use different
> instructions when accessing things like page tables. Right now, Xen only
> emulates the instructions that we know are used by the systems we test
> with (things like Linux and certain versions of Windows).
Xen and OpenBSD running under Xen are rapidly rising to the top of my list
of things to work with as general availability of AM2-socket motherboards and
revision F AMD64 chips approaches. Xen and hardware virtualization have been
for a while now at the very top of the list of topics I follow in the news.
Dave Feustel
> Regards,
>
> Anthony Liguori
>
> > Thanks,
> > Dave Feustel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Lose, v., experience a loss, get rid of, "lose the weight"
Loose, adj., not tight, let go, free, "loose clothing"
next prev parent reply other threads:[~2006-04-16 1:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 22:39 Vertualization of Unmodified Operating Systems Dave Feustel
2006-04-15 22:53 ` Anthony Liguori
2006-04-16 1:30 ` Dave Feustel [this message]
2006-04-16 20:31 ` Ronald G Minnich
2006-04-16 21:01 ` Bastian Blank
2006-04-17 21:19 ` Rolf Neugebauer
2006-04-18 17:48 ` Randy Thelen
2006-06-04 8:19 ` Yinghai Lu
2006-06-05 13:12 ` George Dunlap
2006-04-21 16:10 ` Stefan Kaltenbrunner
2006-04-16 13:14 ` M.A. Williamson
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 18:24 Ian Pratt
2006-04-21 19:53 ` Stefan Kaltenbrunner
2006-04-23 7:34 ` Stefan Kaltenbrunner
2006-04-23 22:13 Ian Pratt
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=200604152030.03386.dfeustel@mindspring.com \
--to=dfeustel@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.