From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: Xen and Vanderpool Date: Wed, 16 Feb 2005 14:58:48 -0800 Message-ID: <4213D028.2070309@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: jean-paul.pigache@bull.net Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org On 2/16/2005 7:08 AM, jean-paul.pigache@bull.net wrote: > > Steve, > > I have a couple of questions about the support of Vanderpool by Xen : > > "Yes - works just fine. We can currently support an unmodified > Linux kernel with fully virtualized devices, etc." > > I assume that for the virtualized devices you are using the same > Front-End device drivers as the current ones. Correct ? > No, we have done a port of Bochs (bochs.sf.net) to Xen/VT. See tools/ioemu in the unstable tree. > The work necessary to take benefit of the Vanderpool Technology should > be located in the Xen hypervisor. > Does this require a brand new development or only some changes to the > current hypervisor ? > > Will most of these changes be compatible for the support of Vanderpool > on IA64 or will the work have to be done twice (for IA32 then for IA64) ? The Bochs device models should be reusable, but most of the hypervisor code is arch specific. -Arun ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click