Driver detected an internal error in its data structures for XenVbd

A user has reported that after they boot with my Xen PV drivers, windows
reports “Driver detected an internal error in its data structures for
XenVbd”. XenVbd is a scsiport driver. Is this one of those messages that
could mean almost anything or does it normally refer to something
specific?

I don’t get that error on my system. We are both running 32 bit 2003 R2.

I’m not sure whether to look at values I might not have initialised
correctly, SCSI commands I am emulating, or somewhere else…

Thanks

James

I’ve never seen that one, though that doesn’t mean anything really :slight_smile:

Do you have the rest of the error log entry? It might have an NTSTATUS code
or some other interesting info in it. Do you have access to the offending
system? I’d set a breakpoint on SCSIPORT calling IoWriteErrorLogEntry to see
if I could make any sense based on the call stack.

Good luck!

-scott


Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“James Harper” wrote in message
news:xxxxx@ntdev…
A user has reported that after they boot with my Xen PV drivers, windows
reports “Driver detected an internal error in its data structures for
XenVbd”. XenVbd is a scsiport driver. Is this one of those messages that
could mean almost anything or does it normally refer to something
specific?

I don’t get that error on my system. We are both running 32 bit 2003 R2.

I’m not sure whether to look at values I might not have initialised
correctly, SCSI commands I am emulating, or somewhere else…

Thanks

James

> I’ve never seen that one, though that doesn’t mean anything really :slight_smile:

Do you have the rest of the error log entry? It might have an NTSTATUS
code or some other interesting info in it. Do you have access to the
offending system? I’d set a breakpoint on SCSIPORT calling
IoWriteErrorLogEntry to see if I could make any sense based on the
call stack.

Your NTSTATUS comment made me think of trying something - I changed my
code to return ‘SP_RETURN_BAD_CONFIG’ and got that exact message. There
may be other causes of the message but that one is the most likely, and
possibly of a result of a mismatch in versions between the bus driver
and the enumerated device driver. Time for another question to the
list…

James