From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KNVQI-0003QD-5y for qemu-devel@nongnu.org; Mon, 28 Jul 2008 12:18:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KNVQG-0003Pq-B3 for qemu-devel@nongnu.org; Mon, 28 Jul 2008 12:18:09 -0400 Received: from [199.232.76.173] (port=35914 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNVQG-0003Pl-5s for qemu-devel@nongnu.org; Mon, 28 Jul 2008 12:18:08 -0400 Received: from wr-out-0506.google.com ([64.233.184.233]:1881) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KNVQG-0003Gl-6I for qemu-devel@nongnu.org; Mon, 28 Jul 2008 12:18:08 -0400 Received: by wr-out-0506.google.com with SMTP id c46so4068622wra.18 for ; Mon, 28 Jul 2008 09:18:06 -0700 (PDT) Message-ID: <488DF11D.7090100@codemonkey.ws> Date: Mon, 28 Jul 2008 11:17:33 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <488DC8B2.1070009@redhat.com> <20080728141515.GJ3196@minantech.com> <488DD98D.5010907@codemonkey.ws> <488DDA93.4070702@redhat.com> <488DDF8B.8020103@codemonkey.ws> <488DE142.1060100@redhat.com> <488DE1E0.1070005@codemonkey.ws> <488DE8D4.5020502@redhat.com> <20080728160215.GB23771@minantech.com> In-Reply-To: <20080728160215.GB23771@minantech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Chris Lalancette , "qemu-devel@nongnu.org" 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. > 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. > 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. Regards, Anthony Liguori > -- > Gleb. >