Bugzilla – Bug 613490
blk_tap: Error initialising /dev/xen/blktap - No more devices
Last modified: 2010-06-14 15:31:58 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1 Firefox/3.5.9 On openSUSE 11.2 (x86_64) with xen-tools-3.4.1_19718_04-2.1.x86_64 kernel-xen-base-2.6.31.8-0.1.1.x86_64 xen-libs-3.4.1_19718_04-2.1.x86_64 kernel-xen-2.6.31.8-0.1.1.x86_64 xen-kmp-desktop-3.4.1_19718_04_2.6.31.5_0.1-2.1.x86_64 xen-3.4.1_19718_04-2.1.x86_64 i can no more create or reboot any VMs using tap:aio driver. All seems to be fine with other VMs with "file" driver My vms complains about no mounted disks and i find in my logs: un 7 16:11:41 alca2 kernel: [12537879.848530] blk_tap: Error initialising /dev/xen/blktap - No more devices Jun 7 16:11:41 alca2 logger: /etc/xen/scripts/blktap: Writing backend/tap/136/51712/hotplug-status connected to xenstore. Jun 7 16:11:41 alca2 logger: /etc/xen/scripts/blktap: Writing backend/tap/136/51728/hotplug-status connected to xenstore. Jun 7 16:11:44 alca2 kernel: [12533839.409637] blktap: ring-ref 8, event-channel 12, protocol 1 (x86_64-abi) Jun 7 16:11:44 alca2 kernel: [12533839.412361] blktap: ring-ref 9, event-channel 13, protocol 1 (x86_64-abi) Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51712 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51728 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51728 Jun 7 16:12:09 alca2 logger: /etc/xen/scripts/blktap: remove XENBUS_PATH=backend/tap/136/51712 Reproducible: Always Steps to Reproduce: 1.VM's with high ID (above 130) 2. 3.
Created attachment 368610 [details] xen-hotplug.log
Created attachment 368611 [details] xend.log
Created attachment 368612 [details] screenshot of a booting guest
*** Bug 612081 has been marked as a duplicate of this bug. ***
This very likely is a duplicate (just with different manifestation) of bug 589788. Therefore, a fix is already queued for a future kernel maintenance update. If the issue persists beyond that, please re-open. *** This bug has been marked as a duplicate of bug 589788 ***