On Sat, Nov 12, 2005 at 04:00:43PM -0500, John L Griffin wrote:
> Ewan's workaround solves my problem. For the record, here is the
> necessary change in meterif.py:
>
> def getDeviceDetails(self, config):
> devid = self.allocateDeviceID()
> back = { 'hotplug-status' : 'connected' }
> return (devid, back, {})
>
> By the way, did I miss a page that discusses this on the Xen wiki or on
> this list? (I'd searched these, but to no avail.)
There is very little documentation of the Xen internals, I'm afraid. There
are people working on API and user documentation, but the internals is pretty
much last on the list. Your best bet is to ask on the list if you get stuck.
> > You lost me completely. What is it you want to do?
>
> I'd like to start three domains:
> 1. dom0 [xen0 kernel]
> 2. my-backend [xen0 kernel]: the meter backend domain
> 3. my-frontend-1 [xenU kernel]: connects to my-backend
> 4. my-frontend-2 [xenU kernel]: connects to my-backend
> etc.
>
> In other words, the meter backend functionality will be entirely contained
> in the "my-backend" domain. My understanding of the "netif", "blkif", and
> "tpmif" domain configuration options is that they're intended for exactly
> this purpose?
Yes, this kind of structure should be fine.
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home