WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] Configuration options from the hypervisor?

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] Configuration options from the hypervisor?
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Wed, 17 Nov 2010 00:40:39 +0300
Delivery-date: Tue, 16 Nov 2010 13:46:29 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=aflzJvDUWL123hyS3lD/wSIxPM+h17XrBqOyDxABEIE=; b=qPGDlaSLuBguDQ+US7is+UWgFXglpf9IGnd1WbHawCs88y7LqPMN6ltNgLCcErqd4Q CQ00mt98xBm2gTGGSVi+JRZf7ngT/LrCRghcm3kG+jc3TnKPDfRGQpOWl/aotyi3vx0s RHkw8iUkdGcKxhNBL3WJLmWuYpy4hiIqLKEoY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=mvNil/m4xh7G/XtWv/4tvotHKaHsZiTkidq9vfFyEzWNRNmgHopoS3icK/eD4JoN3J nRxPx3tgc/T26tCmxiANjj/snPPNx31qUdDduHBkQhexa3es9HeLFad1NtdWMu83EKjy 6sLnYjfVZJ7wBdC+3HRGDNJ0b9MyEBT02sLS8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinxctyg7QY-U4suf+O-oqrYcHw80HNDcYt24WK9@xxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimvxGHMji3KLoQBiH+FEqJahwCG9a06_iKV5UKs@xxxxxxxxxxxxxx> <20101116080003.GQ32385@xxxxxxxxxxxxxxxxxxxxxx> <AANLkTinCELL=YgjDPXtE7VP=c_DEurWQGxUdxzY-BcD=@xxxxxxxxxxxxxx> <20101116165051.GV32385@xxxxxxxxxxxxxxxxxxxxxx> <AANLkTinxctyg7QY-U4suf+O-oqrYcHw80HNDcYt24WK9@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Fist: hypervisor don't know what is 'virtual machine'. It have no any
knowledge about disks, networks, OS'es, etc.

All it know is about _DOMAINS_. What difference between domain and VM? 

If VM rebooted - it's new domain. If VM migrated - it's new domain. So,
if you are talking about VM you must talk not about hypervisor, but a
'domain builder'. Look at it code and see if you understand what's
happens. I really do not, it's mystic ocaml and moonspeak  everywhere.

If you do really wish to do some patches to hypervisor, you can f.e. add
you own hypercall. But xen code (compare to userspace one) is much more
complicated and operate in different to userspace terms.

В Втр, 16/11/2010 в 13:23 -0500, Cutter 409 пишет:
> I'm making modifications to the hypervisor itself, which needs to be
> aware of a few things about each VM it's managing.
> 
> For example, I want the hypervisor to know if the guest is Windows XP,
> Vista, 2000, etc. 
> Somehow I'd like to store this information with the VM once, when
> configuring it, and be able to read it each time the VM is launched
> from the hypervisor.
> 
> Xapi provides the ability to store arbitrary configuration data via
> the "other_config" section, which in python is "
> session.xenapi.VM.add_to_other_config() ",
> but I'm starting to think that information stored there is not
> readable by the hypervisor.
> 
> Hope that clarifies, and thanks!
> 
> 
> On Tue, Nov 16, 2010 at 11:50 AM, Magnus Therning
> <magnus.therning@xxxxxxxxxx> wrote:
>         On Tue, Nov 16, 2010 at 03:30:48PM +0000, Cutter 409 wrote:
>         > Thanks, but I'm actually referring to per VM configuration
>         data. I'm trying
>         > to get some custom configuration strings passed to the
>         hypervisor when a VM
>         > starts.
>         >
>         > I was hoping that somehow I could read the other_config
>         section from the
>         > hypervisor, but maybe it's only possible to pass data after
>         starting the
>         > guest with an event channel?
>         
>         
>         I don't quite understand what you are asking about, unless by
>         "hypervisor" you
>         actually mean Xapi :-)
>         
>         Maybe it would be easier for me to understand if you tell us
>         what you would
>         like to do more specifically?
>         
>         Cheers,
>         M
>         
>         > On Tue, Nov 16, 2010 at 3:00 AM, Magnus Therning
>         <magnus.therning@xxxxxxxxxx<mailto:magnus.therning@xxxxxxxxxx>> wrote:
>         > On Mon, Nov 15, 2010 at 09:33:26PM +0000, Cutter 409 wrote:
>         > > Hello,
>         > >
>         > > I'm trying to pass configuration options to the
>         hypervisor.
>         > >
>         > > It seems like each VM has an "other_config" section that I
>         should be able to
>         > > add options to, but I can't seem to figure out how to read
>         them from the
>         > > hypervisor.
>         > > In userland I can set the options using "
>         session.xenapi.VM.add_to_
>         > > other_config(  ) " (In Python) but is there any way to
>         retreive it from the
>         > > hypervisor?
>         > >
>         > > If not, is there another mechanism where I can store
>         additional
>         > > configuration data?
>         >
>         > Arguments for the hypervisor are passed by the boot loader.
>          Take a look at
>         > /boot/extlinux.conf.
>         >
>         > Cheers,
>         > M
>         >
>         > --
>         > Magnus Therning
>         
>         >
>         magnus.therning@xxxxxxxxxxxxx<mailto:magnus.therning@xxxxxxxxxxxxx>   
>        Jabber: magnusth@eng
>         >
>         > There does not now, nor will there ever, exist a programming
>         language
>         > in which it is the least bit hard to write bad programs.
>         >     -- Flon's Axiom
>         >
>         >
>         > Perl is another example of filling a tiny, short-term need,
>         and then
>         > being a real problem in the longer term.
>         >     -- Alan Kay
>         >
>         > _______________________________________________
>         > xen-api mailing list
>         
>         >
>         xen-api@xxxxxxxxxxxxxxxxxxx<mailto:xen-api@xxxxxxxxxxxxxxxxxxx>
>         > http://lists.xensource.com/mailman/listinfo/xen-api
>         >
>         
>         > _______________________________________________
>         > xen-api mailing list
>         > xen-api@xxxxxxxxxxxxxxxxxxx
>         > http://lists.xensource.com/mailman/listinfo/xen-api
>         
>         
>         
>         --
>         
>         Magnus Therning
>         magnus.therning@xxxxxxxxxxxxx          Jabber: magnusth@eng
>         
>         There does not now, nor will there ever, exist a programming
>         language
>         in which it is the least bit hard to write bad programs.
>             -- Flon's Axiom
>         
>         
>         Perl is another example of filling a tiny, short-term need,
>         and then
>         being a real problem in the longer term.
>             -- Alan Kay
>         
>         _______________________________________________
>         xen-api mailing list
>         xen-api@xxxxxxxxxxxxxxxxxxx
>         http://lists.xensource.com/mailman/listinfo/xen-api
>         
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api