Steve,
Some statistics from kernel of domu, something like information about
domu''s cpu usage , its schedular and number of interrupts or something
about I/O. What is important for me is that these information are
accessible from xen or domu without any need to trap to xen or dom0.
I want to know what information is accessible this way, so that I choose
between them which can represent intrusion to domu somehow.
Mina
On Mon, Jul 29, 2013 at 5:53 AM, Steven Maresca <steve@zentific.com>
wrote:
>
>
>
> On Sat, Jul 27, 2013 at 7:27 AM, Mina Jafari
<ai.minajafari@gmail.com>wrote:
>
>> Hi,
>>
>> What information does dom0 or xen have about domu which
doesn''t need
>> switching to domu or back?
>> I want to make a feature vector of some features of domu but I
don''t want
>> accessing those features need extra price of switching to domu.
>>
>
> Mina,
>
> Some of the information you seek might be available to domain 0 -- a fair
> amount of information is preserved in xenstore as a consequence of creating
> a VM. Similarly, libvirt and other management mechanisms often collect
> valuable metadata (e.g., libvirt''s inspection facilities which can
use
> libguestfs to infer the type of operating system running within a VM).
> It''s important to keep in mind that many virtualization tools
treat each VM
> as a mere container and leave most OS internals to traditional
> deployment/management mechanisms.
>
> What information do you wish to obtain?
>
> Steve
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel