| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Re: [Xen-devel] tap:qcow causes dom-U to hang in 3.0.3
Roland Paterson-Jones wrote:
Julian Chesterfield wrote:
There's a bunch of DPRINTFs in the code which send debug output to
syslog. You can play with syslog settings to switch on the debug
messages and direct them to a log file.
Here is another clue from syslog. Below is the full log, but the hang
seems to accur when the following log messages are triggered (there's
a bunch of them at the end):
Nov 14 11:59:47 dom0-0-50-45-5d-6a-bc TAPDISK: AIO_LOCK or
iocb_free_count (0) failed[869040]
And when I try to 'xm destroy' the instance after it hangs, I get a slew
of the following :
Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: invalid kernel
buffer -- could not remap it
Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: Reached Fail_flush
Nov 14 12:41:35 dom0-0-50-45-5d-6a-bc kernel: blk_tap: BLKTAP_INVALID_HANDLE
This is the inverse of the error messages I see when I build the
user-land tools myself. In the above it's the kernel buffer that can't
be re-mapped. With my user-land tools it's the user buffer that can't be
remapped. I wonder (but have no idea) whether this is related to PAE at all.
Roland
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home