> On 07/02/10 12:47, Richard L. Hamilton wrote: > > That is...is there a mechanism provided to do this? > > > > As an afterthought, this also applies to non-global [...] > > was would be better. Ideal if the same mechanism > (on what might > > or might not be a zone, LDOM, or virtualized > instance running under > > for example Xvm (xen) or VirtualBox) could be used > for a guest of any > > of those sorts to determine its current host for > informational purposes > > only - and for no other purpose, if one wishes to > leave > > migration of guests unaffected! If such a [...] > > S10U9 will include the implementation of PSARC > 2010/004 > Logical Domain Information API and ldminfo. Despite > the > case title, it implements a new utility: > /usr/sbin/virtinfo > nd library: libv12n that I believe (at least for > LDoms) > supplies the information you're looking for. This > was > implemented to support sun4v/LDoms customers and > doesn't > currently support zones or Xen. But there's no > reason why > it can't in the future be extended to zones and/or > Xen. > > Mike
Thank you! That will solve the problem for LDOMs, where workarounds that would transparently detect migration were likely to require hooking into the migration itself. I think that extending the mechanism to zones might be the next easy step; some of the bits of how to do that are obvious even to me, if not all of them. The easy part of that is it doesn't need to interact with hardware or with the external virtualization providing software, and that it should be identical for SPARC and x86/amd64. If anyone is thinking along those lines, and is free to say not when it might be available (we all understand that's not permitted) but at least where they're at so far, I'd be very interested. But I'd love to see the mechanism eventually extended to _all_ virtualization or hardware partitioning schemes, especially those where there are mechanisms for migrating the guest for different hosts, although even for hardware domains, it would be of some value. I see paravirtualization environments as the next step after zones, and non-paravirtualized as coming after that (since it would need some convention for how to make hosting info available to guests on a range of hosting platforms like VB w/o guest additions, VMware, etc). -- This message posted from opensolaris.org _______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
