On Fri, Nov 05, 2010 at 10:11:00AM -0600, Eric Blake wrote:
On 11/05/2010 09:46 AM, Daniel Veillard wrote:
> v2: incorporates Dan suggestions especially move smbios into <os>
>
> This patch set implements a new way to store system informations and
> pass them to the domain, it's modelled on the SMBIOS support in
> hypervisors using a complete emulation (type hvm) and allow to override
> those informations in domains:
>
> The simplest is the use of:
>
> <os>
> <type>hvm</type>
> <smbios mode="host"/>
> <os>
>
> in which case the domain will try to inherit those values from
> the Host own values, the classical use case is the use of OEM'ed
> Windows versions where one need to export SMBIOS informations from
> the host to the guest.
How does this interact with migration? Will the guest see different
host information (either at the moment of migration, or on the first
reboot after migration), or are we planning on treating this as
shorthand, and internally converting it to a <sysinfo> tree as part of
the migration?
<smbios mode="host"/> clearly can't play well with migration.
With the current code since the internal XML is not extended
the SMBIOS values will be seen as changing during run from a guest
OS point of view.
I'm not sure it's worth trying to "fix" this, unless having
another mode where host data at define time gets turned into
a domain sysinfo.
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine
http://rpmfind.net/
http://veillard.com/ | virtualization library
http://libvirt.org/