qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Lalancette <clalance@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Mon, 28 Jul 2008 19:27:01 +0300	[thread overview]
Message-ID: <20080728162701.GC23771@minantech.com> (raw)
In-Reply-To: <488DF11D.7090100@codemonkey.ws>

On Mon, Jul 28, 2008 at 11:17:33AM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
>>
>> CMOS has enough memory for UUID, but UUID is not the only thing that
>> needs to be passed to BIOS, so eventually we can run out of space there.
>>   
>
> I'm inclined to think that on a real machine, the UUID is stored in the  
> CMOS.
>
Should be easy to check.

>> For example we have a requirement to pass additional ACPI tables that
>> user may specify on command line.
>
> What's the use-case?  I don't think this is a very good idea.
>
AFAIK some OEM version of windows needs special ACPI table for
activation.

>>  There is no enough space to put those
>> tables into CMOS. What I did is that: BIOS passes to qemu address where to
>> store additional tables (via backdoor) and qemu copies them there. To
>> this scheme to work there should be bidirectional channel between qemu
>> and BIOS. Other then that I am not particularly attached to vmware
>> backdoor :)
>>   
>
> You can not arbitrarily extend the backdoor interface.  It's an  
> interface defined and controlled by VMware.  If you extend it, you risk  
> breaking other OSes that are assuming that interface has a different  
> meaning.
>
I am not disagreeing with you. Lets define another interface that is
acceptable by everyone here and I (or somebody else) will implement it. 

--
			Gleb.

  reply	other threads:[~2008-07-28 16:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 13:25 [Qemu-devel] [PATCH 0/3]: Add UUID command-line option Chris Lalancette
2008-07-28 14:15 ` [Qemu-devel] " Gleb Natapov
2008-07-28 14:37   ` Anthony Liguori
2008-07-28 14:41     ` Chris Lalancette
2008-07-28 15:02       ` Anthony Liguori
2008-07-28 15:09         ` Chris Lalancette
2008-07-28 15:12           ` Anthony Liguori
2008-07-28 15:42             ` Chris Lalancette
2008-07-28 16:02               ` Gleb Natapov
2008-07-28 16:17                 ` Anthony Liguori
2008-07-28 16:27                   ` Gleb Natapov [this message]
2008-07-28 17:41                     ` Blue Swirl
2008-07-28 16:28                   ` Jamie Lokier
2008-07-28 19:02                     ` Anthony Liguori
2008-07-28 20:00                       ` Jamie Lokier
2008-07-28 20:25                         ` Anthony Liguori
2008-07-28 20:40                           ` Paul Brook
2008-07-28 20:55                             ` Anthony Liguori
2008-07-29  6:31                           ` Gleb Natapov
2008-07-28 15:48             ` Jamie Lokier
2008-07-31 19:45               ` [Qemu-devel] " Sebastian Herbszt
2008-07-28 15:49             ` [Qemu-devel] " Jamie Lokier
2008-07-28 16:06               ` Anthony Liguori
2008-07-28 15:35     ` Gleb Natapov
2008-07-29 19:22       ` Anthony Liguori
2008-07-29 19:50         ` Gleb Natapov
2008-07-30 17:32           ` Blue Swirl
2008-08-05 14:33             ` Gleb Natapov
2008-08-06  2:35               ` Anthony Liguori
2008-08-06 16:26                 ` Blue Swirl
2008-08-06 16:33                   ` Anthony Liguori
2008-08-06 22:07                     ` [Qemu-devel] " Sebastian Herbszt
2008-08-06 22:11                       ` [Qemu-devel] " Anthony Liguori
2008-07-29  8:15     ` Daniel P. Berrange
2008-07-29  8:42       ` Chris Lalancette
2008-07-28 15:51   ` Jamie Lokier

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=20080728162701.GC23771@minantech.com \
    --to=gleb@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=clalance@redhat.com \
    --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).