[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH 0/7] Revamped Smbios/Sysinfo support v2



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?

I believe that VMWare defines that the data in this region *will* change
when the guest is migrated. Whether this upsets the guest OS or not is
a open question. If the admin wants something explicitly migration
safe, then they can use the manual setup we allow for in the XML, though
of course only QEMU supports this approach.

Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]