Re: [Xen-devel] tap:aio problem on Xen 3.4.3-rc7-pre

[Fantu <fantonifabio@xxxxxxxxxx>]

In syslog i see that:
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:789: blktapctrl: v1.0.0
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver: [raw
image (aio)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver: [raw
image (sync)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver:
[vmware image (vmdk)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver:
[ramdisk image (ram)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver:
[qcow disk (qcow)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:791: Found driver:
[qcow2 disk (qcow2)]
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl_linux.c:92: couldn't find
device number for 'blktap0'
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:858: couldn't open
blktap interface
May 12 09:01:54 vfarm BLKTAPCTRL[2795]: blktapctrl.c:917: Unable to start
blktapctrl



Fantu wrote:
> 
> Dom0 Lenny 64 bit with kernel
> linux-image-2.6.32-5-xen-amd64_2.6.32-12_amd64.deb and xen from hg-testing
> DomU windows xp with gplpv_XP_0.11.0.213_debug.msi
> 
> Starting domU with tap:aio (my default option config in all production
> system) gives always blu screen and i solved only changing disk from
> "tap:aio" to "file"
> Here the log file with tap:aio disk and problem: 
> http://old.nabble.com/file/p28526121/qemu-dm-CORSO01.log
> qemu-dm-CORSO01.log 
> 
> Can somebody help me solve problem for continue use tap:aio and also xen
> 3.4.3?
> 

-- 
View this message in context: 
http://old.nabble.com/tap%3Aaio-problem-on-Xen-3.4.3-rc7-pre-tp28526121p28532629.html
Sent from the Xen - Dev mailing list archive at Nabble.com.


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