From: Sebastian Biedermann <biedermann@seceng.informatik.tu-darmstadt.de>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: Logging Access to HDD
Date: Tue, 19 Apr 2011 11:44:08 +0200 [thread overview]
Message-ID: <4DAD5968.1030408@seceng.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01CC8B2B@trantor>
Am 19.04.2011 11:35, schrieb James Harper:
>> Dear List,
>>
>> I´m working in research and I tought this list could be
>> a good adress for my questions.
>>
>> I want to log the disk accesses of the virtual hvm instances running in Xen.
>> That means for the start I want to log the write querys of a running
>> domU instance in the dom0 instance.
>>
>> So I´m trying to modify the Xen 3.2.1 source code,
>> but actually I was not able to find a good entry point to do this.
>>
>> For now, I want to log the disk accesses of a running windows 7 domU
>> instance.
>> The best what could happenis that I could see even the source and target
>> of a hdd write query.
>>
>> Does anyone have an idea how I could do this on a good way?
>> Which Xen source file / function should I modify? Where is the best
>> entry point to do this?
> HVM access can either be emulated PCI IDE, or PV. For the emulated access you would hook into qemu, I think. For PV access you would need to hook into whatever block device backend you are using.
>
> Do you just want to count reads and writes, or do you want to log every single byte read/written?
>
> James
I dont need to log every single byte, it would be enough to know which
file is accessed by the domU inside its image.
So when I use HVM I need to modify qemu and not the xen source?
thanks
--
Sebastian
next prev parent reply other threads:[~2011-04-19 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 9:15 Logging Access to HDD Sebastian Biedermann
2011-04-19 9:35 ` James Harper
2011-04-19 9:44 ` Sebastian Biedermann [this message]
2011-04-19 9:54 ` Michal Novotny
2011-04-19 12:52 ` Sebastian Biedermann
2011-04-19 10:02 ` Heiko Wundram
2011-04-19 10:08 ` Michal Novotny
2011-04-19 10:18 ` Laszlo Ersek
2011-04-19 10:22 ` Michal Novotny
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=4DAD5968.1030408@seceng.informatik.tu-darmstadt.de \
--to=biedermann@seceng.informatik.tu-darmstadt.de \
--cc=james.harper@bendigoit.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).