From: Nick Logan <nick_logan@symantec.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com, jacobg@diku.dk, ushuanglily@gmail.com
Subject: Re: Where can I find some tutorial or manual on how to use xenstore?
Date: Wed, 28 Jun 2006 14:38:15 +0100 [thread overview]
Message-ID: <44A28647.3010108@symantec.com> (raw)
In-Reply-To: <20060628130526.GC26663@leeni.uk.xensource.com>
Thanks Ewan,
See below.
Cheers,
Nick
Ewan Mellor wrote:
>On Wed, Jun 28, 2006 at 12:08:33PM +0100, Nick Logan wrote:
>
>
>
>>It's certainly possible, I've used this code as the basis for a new
>>driver, which is similar to the vbd driver. The driver starts fine but I
>>am unable to have it participate in a domain save/restore. I guess that
>>this is because xend is not aware of the new driver and the open
>>devices supported by this driver and hence the driver does not receive
>>resume calls when the domain is restored..
>>
>>Is there any way that a new driver can make it's existance known to xend?
>>
>>
>
>If you've managed to get the driver to start through xend, I'd be surprised if
>it's xend's fault that save/restore does not work.
>
>
The driver was started outside of xend, using a varient of Jacob's
buscreate program to set the necessary values in xenstore. As this a 3rd
party driver, I'm looking for a solution that does not involve xm or
xend changes, if that's possible. I'll take a look at the blktap patches
to see if that helps.
>In any case, the main driver integration point is at the bottom of
>tools/python/xen/xend/XendDomainInfo.py, where you can register a subclass of
>xen.xend.server.DevController.py to manage the device. You also need to make
>sure that the driver's config is parsed properly by xm.
>
>Take a look at Julian Chesterfield and Andrew Warfield's recent blktap patches
>to see how driver tool integration is done:
>
>http://lists.xensource.com/archives/html/xen-devel/2006-06/msg00738.html
>
>Cheers,
>
>Ewan.
>
>
next prev parent reply other threads:[~2006-06-28 13:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Fukq5-00045x-5p@host-192-168-0-1-bcn-london>
2006-06-28 11:08 ` Where can I find some tutorial or manual on how to use xenstore? Nick Logan
2006-06-28 13:05 ` Ewan Mellor
2006-06-28 13:38 ` Nick Logan [this message]
2006-06-28 14:57 ` Ewan Mellor
2006-06-28 15:20 ` Nick Logan
2006-06-28 15:32 ` Ewan Mellor
2006-06-29 13:53 ` Nick Logan
2006-06-29 14:19 ` Ewan Mellor
2006-06-29 14:41 ` Andrew Warfield
2006-06-29 14:42 ` Nick Logan
2006-06-19 7:13 Lily Huang
2006-06-20 2:15 ` Where can I find some tutorial or manual on how to use?xenstore? Horms
2006-06-25 12:57 ` Where can I find some tutorial or manual on how to use xenstore? Jacob Gorm Hansen
2006-06-25 19:00 ` Lily Huang
2006-06-26 17:16 ` Jacob Gorm Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A28647.3010108@symantec.com \
--to=nick_logan@symantec.com \
--cc=ewan@xensource.com \
--cc=jacobg@diku.dk \
--cc=ushuanglily@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.