From: "Michael R. Hines" <michael@beethovenweb.com>
To: xen-devel@lists.xensource.com
Subject: vbd backend dropping block I/Os?
Date: Sat, 02 Dec 2006 00:42:29 -0500 [thread overview]
Message-ID: <45711245.9060100@beethovenweb.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]
Hi,
I have a block device (implemented as a kernel module)
that we've written for our own purposes which we've
attempted to load as an IDD...
I have done the following:
1. added the appropriate [ phy:/dev/somedevice,/dev/somedevice,w ]
entry to the guest domU config
2. issued a block-based mknod /dev/somedevice
3. Finally: I sent some blocks to the device with dd from
a loaded guest on the blkfront side. I have debug printk's
in the device that periodically let me know how many BIOs
the block device has received on the blkback side: but the
number of requests received by the device does not match
the number of requests sent to it from the guest kernel
through the device channel. (It's about a 10 to 1 ratio
of missing requests) -> yet the dd command seems to think
they were all sent successfully from the guest's perspective.
I've done a 'xenstore-ls' and verified that the sector
size of the device that xen perceives is identical to
that of my block device.
Is there any obvious reason why this might happen?
Your help is much appreciated.
- Michael
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-12-02 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 5:42 Michael R. Hines [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-02 17:54 vbd backend dropping block I/Os? Michael R. Hines
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=45711245.9060100@beethovenweb.com \
--to=michael@beethovenweb.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.