Bug#548345: xen-linux-system-2.6.26-2-xen-amd64: tap:aio for domU disks fails

[Jamon <bugs@jamon.ca>]

Package: xen-linux-system-2.6.26-2-xen-amd64
Version: 2.6.26-19
Severity: important

Using tap:aio for a domU disk parameter will result in the domU failing to 
boot. Specifically, the domU will boot partially until it reaches block device 
creation e.g. 

XENBUS: Waiting for devices to initialise: 295s...290s...285s...

After 300 seconds the kernel drops into a busybox shell having failed to find 
a root disk device.

Other users have reported the same problem via mailing lists and irc (##xen on 
freenode): 

http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2009-January/002262.html

Using file: instead of tap:aio results in a working domU, but tap:aio is the 
preferred method and is the default in newer versions of Xen.

Finally, as Andrey reported on the mailing list, recompiling the xenblktap 
driver from a newer 3.4.1 xen source distribution does not make a difference.

If there's more infomation I can collect, I'll be happy to send it along to 
the relevant list/bug etc.

Regards, Jamon

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xen-linux-system-2.6.26-2-xen-amd64 depends on:
ii  linux-image-2.6.26-2-xen-amd6 2.6.26-19  Linux 2.6.26 image on AMD64, oldst
ii  xen-hypervisor-3.2-1-amd64    3.2.1-2    The Xen Hypervisor on AMD64

xen-linux-system-2.6.26-2-xen-amd64 recommends no packages.

xen-linux-system-2.6.26-2-xen-amd64 suggests no packages.

-- no debconf information