From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: [PATCH 0/2] qemu: SMBIOS passing support Date: Mon, 30 Mar 2009 07:59:36 -0600 Message-ID: <1238421576.15558.146.camel@lappy> References: <1237835133.7276.1107.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: kvm To: qemu-devel Return-path: Received: from g4t0015.houston.hp.com ([15.201.24.18]:3263 "EHLO g4t0015.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752234AbZC3N74 (ORCPT ); Mon, 30 Mar 2009 09:59:56 -0400 In-Reply-To: <1237835133.7276.1107.camel@lappy> Sender: kvm-owner@vger.kernel.org List-ID: Is there any interest in this series? Aside from copying host SMBIOS entries, it also seems useful for providing information to the guest about their virtual machine pool (perhaps via a type 3 entry), or whatever other bits of data someone might find useful (type 11, OEM string for instance). Thanks, Alex On Mon, 2009-03-23 at 13:05 -0600, Alex Williamson wrote: > This series adds a new -smbios option for x86 that allows individual > SMBIOS entries to be passed into the guest VM. This follows the same > basic path as the support for loading ACPI tables. While SMBIOS is > independent of ACPI, I chose to add the smbios_entry_add() function to > acpi.c because they're both somewhat PC BIOS related (and ia64 can > support SMBIOS and might be able to make use of it there). > > This feature allows the guest to see certain properties of the host if > configured correctly. For instance, the system model and serial number > in the type 1 entry. Obviously its only built at boot, so doesn't get > updated for migration scenarios. User provided entries will supersede > generated entries, so care should be taken when passing entries which > describe physical properties, such as memory size and address ranges. > Thanks, > > Alex >