From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: Porting Xen
Date: Wed, 22 Dec 2004 04:36:44 +0000 [thread overview]
Message-ID: <41C8F9DC.4040203@blueyonder.co.uk> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12314E@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
> Doesn't seem much point running 32 bit paravirtualized guests (it will
> still run 32 bit user space), and it makes life easier not to. However,
> there are plans to run 32 and 64 bit unmodified guests on a 64 bit
> hypervisor (as well as 64bit paravirtualized guests) using Intel VT
> extensions.
Aha: <http://www.intel.com/research/print/cambridge_collab.pdf>
I was wondering how the Xen developers could be so confident that VT
would be sufficient to run Windows under Xen, given that no details
of VT have been announced publically; this explains it.
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-22 4:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 2:38 Porting Xen Ian Pratt
2004-12-22 3:50 ` Kip Macy
2004-12-22 23:31 ` David Rhodus
2004-12-22 23:55 ` Kip Macy
2004-12-22 4:36 ` David Hopwood [this message]
2004-12-22 5:10 ` Adam Sulmicki
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 17:35 Carl Holtje ;021;vcsg6;
2005-01-05 14:18 ` aq
2005-01-05 14:25 ` Mark Williamson
2005-01-05 16:25 ` Dan Magenheimer
2004-12-22 5:01 Ian Pratt
2004-12-22 11:39 ` Dave Feustel
2004-12-22 11:43 ` Keir Fraser
2004-12-22 21:49 ` David Hopwood
2004-12-22 11:45 ` Dave Feustel
2004-12-22 13:13 ` Keir Fraser
2004-12-21 16:03 Dave Feustel
2004-12-21 19:19 ` Kip Macy
2004-12-21 19:32 ` Luciano Miguel Ferreira Rocha
2004-12-21 19:59 ` Dave Feustel
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=41C8F9DC.4040203@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.