similar to: BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed

Displaying 20 results from an estimated 2000 matches similar to: "BLKTAPCTRL[2375]: blktapctrl_linux.c:86: blktap0 open failed"

2012 Apr 02
23
[PATCH 00 of 18] [v2] tools: fix bugs and build errors triggered by -O2 -Wall -Werror
Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in
2009 May 28
1
[PATCH] blktap2: fix makefile of vhd for parallel make
blktap2: fix makefile of vhd for parallel make With parallel make, libvhd might not be created before link resulting in link error. This patch guarantees it. Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> diff --git a/tools/blktap2/vhd/Makefile b/tools/blktap2/vhd/Makefile --- a/tools/blktap2/vhd/Makefile +++ b/tools/blktap2/vhd/Makefile @@ -12,6 +12,9 @@ CFLAGS +=
2011 Aug 04
3
[Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd
I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43
2010 Jun 21
7
Third release candidate for Xen 4.0.1
Folks, The tag 4.0.1-rc3 has been added to http://xenbits.xensource.com/xen-4.0-testing.hg Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2011 Jun 13
3
blktapctrl not running
Hi, I am running XEN 4.1 on Debian 6 and I cannot find blktapctrl process running. xend is started. I installed XEN from 4.1 source following instructions here: http://wiki.xensource.com/xenwiki/XenParavirtOps http://wiki.xensource.com/xenwiki/Xen4.0 Should there be a blktapctrl process running in this version? The problem I have encountered is that I can create a domain on a raw disk image but
2011 Jun 29
10
xen 4.1.1 + 3.0.0-rc5 dom0 + blktap2
Hi, I''m currently trying xen 4.1.1 with the 3.0.0-rc5 (heard that it now contains the xen code to run as front or back xen domain). Everything seems to run fine, except that I am trying since a few hours to mount a .vhd file in the dom0. What I tried so far: to create a blank vhd file (this is working): host# vhd-util create -n /storage/test.vhd -s 20G Then i try to mount the file
2010 Aug 04
7
Xen 4.0.1-rc5 w/ 2.6.32.16 dom0, DomU''s start paused
I run my production DomU''s using Xen 3.4.1 at the moment with the old 2.6.18.x dom0 kernel. I just built a new Xen version (4.0.1-rc5) with jemerys git repo of 2.6.32.16 dom0 pvops kernel. When starting domains the go instantly into a paused state and eventually i see this error on the command line. [root@host test1]# xm create -c vps.config Using config file
2010 Apr 08
23
Xen 4.0 on gentoo hotplug scripts problem?
Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.
2010 Apr 08
23
Xen 4.0 on gentoo hotplug scripts problem?
Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.
2010 May 04
1
Fwd: Strange network problem
Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
2007 Nov 28
1
RFC: add tapdisk link in xen-common for blktap
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, while trying to get blktap based domus running with current Debian Xen 3.1.2 I came across a missing link: The tapdisk binary should be added to GLOBAL_SCRIPTS in xen-common/scripts/Makefile. Otherwise blktap based domus don't find their disks. blktapctrl forks tapdisk processes. Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG
2010 Jun 22
18
blktap2 does not work
Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']
2010 Jan 28
31
[PATCH 0 of 4] aio event fd support to blktap2
Get blktap2 running on pvops. This mainly adds eventfd support to the userland code. Based on some prior cleanup to tapdisk-queue and the server object. We had most of that in XenServer for a while, so I kept it stacked. 1. Clean up IPC and AIO init in tapdisk-server. [I think tapdisk-ipc in blktap2 is basically obsolete. Pending a later patch to remove it?] 2. Split tapdisk-queue into
2010 Jun 22
2
domU can not start in Xen 4.0.1-rc3-pre using tapdisk
The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:
2010 Jun 22
2
domU can not start in Xen 4.0.1-rc3-pre using tapdisk
The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:
2010 Oct 20
1
Bug#586772: xen-utils-4.0: No block tap backends available
Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Due to license issues this version of Xen does not include the blktap2 backend (tapdisk2) and associated utilities (vhd-util, etc.). The decision was made to disable the blktap v1 kernel module (the default is now blktap2). As a result we can't use any tap devices which means worse performance than previousl. Since blktap1 was available
2013 Mar 02
7
libxl device_disk_add orphans blktap devices on transaction error
I''m using the CentOS 6 bundle of xen from http://dev.centos.org/centos/6/xen-c6/ and ran into an issue when creating domains with multiple VHD tap disks. Comparing unstable to the 4.2.1 code I''m using, it seems this issue still applies. I''m using a configuration line that looks something like disk = [
2013 May 08
9
blktap2 and qcow2 images
Hi There, I''ve been trying to get this to work for the last couple of days, but found no information on the internet that would help. Essentially, a tap-ctl opencommand with a qcow2 image does not work (error code 2) and produces the following line in syslog: tap-ctl: tap-err:tap_ctl_open: open failed, err -2 I have attached a shell script that reproduces the problem on my machine. The
2012 Feb 18
1
Mounting filesystems with blktap2
For those wanting to know how to mount filesystems through blktap2 here is how you do it, as I couldn''t find it fully documented. The instructions on the blktap2 readme file are rather out of date. You can mount them under Dom0 like so. e.g. to mount a vhd file, sudo xm block-attach 0 tap2:vhd:/home/xen/xenwin7-persist.vhd xvdb w 0 Now the device should appear under /dev ls
2010 Aug 11
8
XenConvert
Hi guys I have installed Xen 4 on Debian Lenny 5.0. I have a physical Windows 2003 Server and I wanna convert this server on a virtual server... I try to use XenConvert but without sucsess... Somebody can help??? Thanks Gilberto Nunes TI Selbetti Gestão de Documentos Telefone: +55 (47) 3441-6004 Celular: +55 (47) 8861-6672 _______________________________________________ Xen-users mailing