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

[Xen-devel] BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Dante Cinco <dantecinco@xxxxxxxxx>
  • Date: Mon, 19 Jul 2010 14:27:07 -0700
  • Delivery-date: Mon, 19 Jul 2010 14:27:47 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hedWjdkUvSIbLcKGXgGl2TVS+eDdEIQVQXC9Jjjga7myuXu+4KRbbTIBMCcSVwuGzy jbFOfUyGqYvLmcxLs623QL83Zg18RTggJ6d+m7Sbg99gwSELi+aQiEh1Wt4OiMGij2jo hEVm0iXKVMSO6jGzme4ld3ahTWLSoxT831sTg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm getting this message (subject line) in daemon.log every time I
start or restart xend. I'm not sure if this is related to the fact
that I cannot boot up my Windows domU from a VHD file. The Windows
domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel).
When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can
no long boot the Windows domU from VHD. The VNC console for the
Windows HVM has this message:

Booting from Hard Disk ...
Boot from Hard Disk failed; could not read the boot disk

No bootable device.
Powering off in 30 seconds.

Here's the disk setting in my Windows domU config file: disk =
['tap:tapdisk:vhd:/mnt/win2008sp2.vhd,xvda:sda1,w']

Here's the other BLKTAPCTRL messages in daemon.log:

BLKTAPCTRL[2444]: blktapctrl.c:790: blktapctrl: v1.0.0
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [raw image (aio)]
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [raw image (sync)]
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [vmware image (vmdk)]
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [ramdisk image (ram)]
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [qcow disk (qcow)]
BLKTAPCTRL[2444]: blktapctrl.c:792: Found driver: [qcow2 disk (qcow2)]
BLKTAPCTRL[2444]: blktapctrl_linux.c:86: blktap0 open failed
BLKTAPCTRL[2444]: blktapctrl.c:859: couldn't open blktap interface
BLKTAPCTRL[2444]: blktapctrl.c:922: Unable to start blktapctrl

I've also attached the output from /var/log/xen/xend.log when
attempting to bringup the Windows domU.

When the Windows domU VHD file was booting under Xen 4.0.0, I would
get these messages in syslog:

tapdisk2[4833]: Created /dev/xen/blktap-2/control device
tapdisk2[4833]: Created /dev/xen/blktap-2/blktap0 device
tapdisk2[4833]: Created /dev/xen/blktap-2/tapdev0 device
tapdisk2[4833]: new interface: ring: 253, device: 253, minor: 0
tapdisk2[4833]: I/O queue driver: lio
tapdisk2[4833]: /mnt/win2008sp2.vhd version: tap 0x00010003, b: 12800,
a: 6903, f: 6087, n: 28330016
tapdisk2[4833]: opened image /mnt/win2008sp2.vhd (1 users, state:
0x00000001, type: 4)
tapdisk2[4833]: VBD CHAIN:
tapdisk2[4833]: /mnt/win2008sp2.vhd: 4

I appreciate any insight or recommendation.

Thanks.

- Dante

Attachment: xend_win2008sp.log
Description: Binary data

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

 


Rackspace

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