From: Anthony Liguori <anthony@codemonkey.ws>
To: Ian Kirk <blob@blob.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Make vmport an optional feature at run time.
Date: Sun, 24 Aug 2008 19:23:59 -0500 [thread overview]
Message-ID: <48B1FB9F.3090405@codemonkey.ws> (raw)
In-Reply-To: <alpine.LFD.1.10.0808242052020.13622@bcny.fcbq.bet>
Ian Kirk wrote:
> Anthony Liguori wrote:
>
>
>> Ian Kirk wrote:
>>
>>> Hi,
>>>
>>> This is my first time sending a patch, so apologies for any errors.
>>>
>>> Patch makes vmport optionally initiated.
>>>
>>>
>> Why should it be optional?
>>
>
> I believe that VMware ESXi (and perhaps other hypervisors/emulators/etc)
> doesn't work when it thinks it is running within virtual enviroment, as it
> talks to vmport when booting (and fails in the current implemtnation -
> perhaps it only works under itself?)
>
That's most likely because the vmport emulation isn't complete enough.
> If I comment init_vmport() out, it definately progresses further along the
> boot sequence.
>
> Also, I guess, it gives you the option to better emulate a real PC (which
> I assume doesn't have vmport).
>
I don't think that's very valuable in and of itself. Moreover, there
are probably a lot more issues with respect to getting ESXi to run under
QEMU. Adding another command line option to support something that we
don't know will ever work worries me. It's just another knob for
someone to accidentally tweak.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-08-25 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 11:47 [Qemu-devel] [PATCH 1/1] Make vmport an optional feature at run time Ian Kirk
2008-08-24 19:38 ` Anthony Liguori
2008-08-24 19:54 ` Ian Kirk
2008-08-25 0:23 ` Anthony Liguori [this message]
2008-08-25 6:19 ` [Qemu-devel] [PATCH] 1/1: vmport update Todd T. Fries
2008-09-07 2:24 ` [Qemu-devel] [PATCH 1/1] Make vmport an optional feature at run time Anthony Liguori
2008-09-07 3:48 ` qemu-devel
2008-08-25 8:34 ` Thiemo Seufer
2008-08-25 9:26 ` Ian Kirk
2008-09-07 2:27 ` Anthony Liguori
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=48B1FB9F.3090405@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blob@blob.co.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).