From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: DMI BIOS String Date: Mon, 22 Aug 2011 10:45:49 +0100 Message-ID: <20110822094549.GD9456@redhat.com> References: Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: kvm@vger.kernel.org To: Derek Return-path: Received: from mx1.redhat.com ([209.132.183.28]:20933 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752970Ab1HVJqG (ORCPT ); Mon, 22 Aug 2011 05:46:06 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Aug 22, 2011 at 03:52:19PM +1200, Derek wrote: > Hi Folks, > > I could not track down any solid info on modifying the DMI BIOS string. > > For example, in VirtualBox you can use 'vboxmanage setsextradata' to > set the BIOS product and vendor string per VM. > > Any ideas if this is possible with KVM? If using QEMU directly you can use '-smbios' args. eg -smbios "type=0,vendor=LENOVO,version=6FET82WW (3.12 )" -smbios "type=1,manufacturer=Fedora,product=Virt-Manager,version=0.8.2-3.fc14,serial=32dfcb37-5af1-552b-357c-be8c3aa38310,uuid=c7a5fdbd-edaf-9455-926a-d65c16db1809,sku=1234567890,family=Red Hat" If using QEMU via libvirt you can use the following: http://libvirt.org/formatdomain.html#elementsSysinfo Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|