From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K8qpD-0007TC-AU for qemu-devel@nongnu.org; Wed, 18 Jun 2008 02:07:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K8qpC-0007T0-JM for qemu-devel@nongnu.org; Wed, 18 Jun 2008 02:07:18 -0400 Received: from [199.232.76.173] (port=47810 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K8qpC-0007Sx-GX for qemu-devel@nongnu.org; Wed, 18 Jun 2008 02:07:18 -0400 Received: from il.qumranet.com ([212.179.150.194]:11472) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K8qpA-0002UX-DL for qemu-devel@nongnu.org; Wed, 18 Jun 2008 02:07:16 -0400 Received: from gleb-debian.qumranet.com (unknown [172.16.15.143]) by il.qumranet.com (Postfix) with ESMTP id 76B84250310 for ; Wed, 18 Jun 2008 09:07:13 +0300 (IDT) Date: Wed, 18 Jun 2008 09:07:13 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] [RESEND PATCH v3 0/5] Add UUID support. Message-ID: <20080618060713.GD32664@minantech.com> References: <20080616130135.24174.93474.stgit@gleb-debian.qumranet.com.qumranet.com> <48583502.6090803@bellard.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48583502.6090803@bellard.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wed, Jun 18, 2008 at 12:04:50AM +0200, Fabrice Bellard wrote: > Gleb Natapov wrote: > > There was no additional comments last time I sent this patch series and > > it was not yet committed to the SVN. Resend it for review/inclusion. > > > > This is updated version of the patch series. The patch #5 checks libuuid > > availability and uses it for UUID generation if present, but it is > > optional so if people think that libvirt is a better place for UUID generation > > just don't apply the last patch. > > I don't like this vmport "backdoor" and I would like to disable it by > default, so I consider it is not the solution to pass the UUID > information to the BIOS. Do you have other interface in mind for host/guest communication? VMware uses the I/O port backdoor interface. Microsoft Virtual PC uses "Invalid Opcode" mechanism as a backdoor. We need this interface for other things too. For instance there are OEM Windows versions that require specific vendor's ACPI table to be present for installation. I have a patch that pass additional ACPI tables to BIOS using backdoor interface since it's not practical to compile different BIOSes for different Windows OEM versions. > > BTW, what is the use of this UUID ? > It is used for system management to tell two identical computers apart. Something like MAC but more stable. In Windows WMI can be used to obtain UUID and we have vendors that use VB scripts to configure machines differently based on their UUIDs. -- Gleb.