RE: [Xen-users] XenAccess Library: Introspection for Xen

[Steve Brueckner <steve@xxxxxxxxxxxxxx>]

> I'm pleased to announce a new project called XenAccess.  The project  
> goals are to provide a full featured introspection library for Xen.   
> Introspection is a technique where applications in one domain can  
> view memory from another domain.  For example, you can run an  
> application in dom0 to list the processes or LKMs in a domU.  More  
> information is available on the website:
> 
> http://xenaccess.sourceforge.net/
> 
> Introspection has been discussed for a few years in the research  
> community.  I'm hoping that this open source project will allow more  
> people to play with it and start thinking about interesting  
> applications for it.  And, of course, I'd be happy to see others  
> interested in introspection get involved with this project as well!
> 
> Cheers,
> bryan

I'm interested in introspection for both Linux and Windows; let me ask a few
naïve questions about potential capabilities:

Would XenAccess implementation and functionality be the same for both
paravirtualized and fully virtualized (using VT) guests?

Would the only difference between introspection on a Linux vs Windows guest
be the closed and undocumented nature of the Windows kernel?

How difficult would it be to get a look at a running guest's file system?
Linux seems easy, but I believe Windows guests use vmx images; can the
Windows file system be viewed naturally from the outside?

Are there any other potential obstacles or difficulties that would make
various introspection techniques on Windows impossible, difficult, or merely
a nuisance?

Thanks for any thoughts,

Steve Brueckner, ATC-NY

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users