virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: akpm@osdl.org, Zachary Amsden <zach@vmware.com>,
	xen-devel@lists.xensource.com,
	Jeremy Fitzhardinge <jeremy@xensource.com>,
	linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
	virtualization@lists.osdl.org
Subject: Re: [patch 7/8] Add a bootparameter to reserve high linear address space.
Date: Tue, 04 May 2010 16:37:38 -0700	[thread overview]
Message-ID: <4BE0AFC2.2090207@goop.org> (raw)
In-Reply-To: <19700101001522.GA3999@ucw.cz>

On 12/31/1969 04:15 PM, Pavel Machek wrote:
> Dynamically loaded hypervisor? Do we really want to support that?
>   

(Missed this because your datestamp was 1969...)

The idea was that you could boot a guest under VMWare fully virtualized
then switch it to a VMI guest by loading a module.  I don't think it
ever worked out - the transition was too trick to get right (especially
applying all the pvops patching to a live system).

    J

  parent reply	other threads:[~2010-05-04 23:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060803002510.634721860@xensource.com>
     [not found] ` <20060803002518.595166293@xensource.com>
     [not found]   ` <20060802231912.ed77f930.akpm@osdl.org>
     [not found]     ` <44D1A6B6.8040003@vmware.com>
     [not found]       ` <20060803004144.554d9882.akpm@osdl.org>
     [not found]         ` <44D1BAB8.8070509@vmware.com>
2006-08-05 21:58           ` [patch 7/8] Add a bootparameter to reserve high linear address space Andrew Morton
2006-08-05 22:52             ` Zachary Amsden
2006-08-05 23:17             ` Rusty Russell
2006-08-06 22:00   ` Pavel Machek
2006-08-06 22:02   ` Pavel Machek
     [not found]   ` <19700101001522.GA3999@ucw.cz>
2006-08-07  2:10     ` Andi Kleen
2010-05-04 23:37     ` Jeremy Fitzhardinge [this message]
2006-08-07  9:12   ` Pavel Machek

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=4BE0AFC2.2090207@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@xensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).