It is basically used to tailor the boot sequence if the VM gets booted in OpenStack. For ex. it could do the following
1. Get IP through DHCP if booted in OpenStack 2. Read config drive or contact metadata service and init the system if booted in OpenStack Thanks, Vijay V. From: Bob Ball [mailto:bob.b...@citrix.com] Sent: Tuesday, November 26, 2013 7:25 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova] Are BIOS strings configured in Hyper-V & ESX similar to KVM instantiated VMs? It's not certain that this will be implemented for the XenAPI driver. Our view is that the BIOS strings shouldn't be relied upon - the hypervisor can clearly set them to anything so it's not really a reliable way to configure the application. Also note that in some scenarios, such as PV guests in Xen clouds, you will not have any BIOS to query. Finally we're not clear on the use case here - What's the use case for needing to know whether you VM is running under OpenStack or not? Bob From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com] Sent: 26 November 2013 01:44 To: OpenStack Development Mailing List (firstname.lastname@example.org<mailto:email@example.com>) Subject: [openstack-dev] [Nova] Are BIOS strings configured in Hyper-V & ESX similar to KVM instantiated VMs? Hi, In a KVM instantiated VM the following signature is present in the BIOS of the VM The 'Manufacturer ' field in 'System Information' group is set to "OpenStack Foundation" This helps the VM to identify that it is getting used in an OpenStack environment. As far as I know XenServer is planning to set the BIOS Strings in IceHouse release. Is this functionality available in other Hypervisors, especially Hyper-V & ESX? Thanks, Vijay V.
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev