mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Alok Kataria <akataria@vmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: kexec with vmware esx 3.0.2
Date: Fri, 03 Oct 2008 14:48:41 -0700	[thread overview]
Message-ID: <1223070521.7330.122.camel@bodhitayantram.eng.vmware.com> (raw)
In-Reply-To: <86802c440810031440o59359f30ka72230b4b0ff73e@mail.gmail.com>

On Fri, 2008-10-03 at 14:40 -0700, Yinghai Lu wrote:
> On Fri, Oct 3, 2008 at 2:21 PM, Zachary Amsden <zach@vmware.com> wrote:
> > On Fri, 2008-10-03 at 14:08 -0700, Yinghai Lu wrote:
> >> anyone tried to use linux kernel to kexec vmware esx?
> >
> > That would not be a recommended practice.  It might work.  It should not
> > be very useful.
> >
> 
> esx 3.0.2 relys on correct mps table,
> could boot linux with update_mptable or alloc_mptable, and then load
> vmware with kexec.

And end up running ESX on hardware where it is not supported and you
already have a buggy BIOS?  Yeah, it might work, but it should not be
very useful.

Zach


  reply	other threads:[~2008-10-03 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 21:08 Yinghai Lu
2008-10-03 21:21 ` Zachary Amsden
2008-10-03 21:40   ` Yinghai Lu
2008-10-03 21:48     ` Zachary Amsden [this message]
2008-10-03 21:58       ` Yinghai Lu
2008-10-03 22:08         ` Zachary Amsden
2008-10-03 22:51           ` Yinghai Lu
2008-10-03 22:58             ` Zachary Amsden
2008-10-03 23:45               ` Yinghai Lu
2008-10-04  5:41                 ` Zachary Amsden

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=1223070521.7330.122.camel@bodhitayantram.eng.vmware.com \
    --to=zach@vmware.com \
    --cc=akataria@vmware.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@kernel.org \
    /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

all inboxes | Powered by JetHome®