[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] tap:aio not working...



Nick Couchman schrieb:
I'm running SLES10 SP1 and have been using file:/ for my file-backed domUs.  
The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three 
or four XEN servers.  I'm having issues with the loopback devices not being 
released when the domUs shutdown or migrate, so I decided to switch over to 
tap:aio for my file-backed domUs.  This isn't working, either.  Whereas the 
domUs with file: at least boot and run, the domUs with tap:aio: fail with this 
error:
syslog messages are unhelpful - here's the output when I try with tap:aio:
Apr 29 16:55:02 xen02 kernel: blkback: ring-ref 8, event-channel 38, protocol 1 
(x86_64-abi)
Apr 29 16:55:02 xen02 kernel: blkback: ring-ref 8, event-channel 38, protocol 1 
(x86_64-abi)
Apr 29 16:55:02 xen02 logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/0/51952
Apr 29 16:56:42 xen02 logger: /etc/xen/scripts/block: remove 
XENBUS_PATH=backend/vbd/0/51952
Apr 29 16:56:43 xen02 logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vbd/0/51952
Anyone have any hints as to what might be going on here? Any possible solutions?

You should have some BLKTAPCTRL and TAPDISK lines in your /var/log/messages which could give you some hints. If these lines are missing you most probably don't have loaded the kernel modules (they aren't loaded by default, IIRC) or blktapctrl isn't running.

Kevin

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.