similar to: blktapctrl not running

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

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 +=

Hi, milos/list, now I''m working on some code related to page sharing. Are there any document/wiki that show how to setup the page sharing environment, so that I can test my code? Checking the code, I noticed the only tapdisk/blktap will use this page sharing mechanism. I''m not sure HVM guest without PV driver can use blktap, so does page sharing support HVM guest? Sorry that

-----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

Hello, I''ve downloaded the xen 4.0.1 version as it is explained here: http://wiki.xensource.com/xenwiki/Xen4.0 <http://wiki.xensource.com/xenwiki/Xen4.0>So, I''ve made a clone from repository, with the following command: hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg And finally I''ve built xen, tools and stubdom. I was looking for a

Hello, I''ve downloaded the xen 4.0.1 version as it is explained here: http://wiki.xensource.com/xenwiki/Xen4.0 <http://wiki.xensource.com/xenwiki/Xen4.0>So, I''ve made a clone from repository, with the following command: hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg And finally I''ve built xen, tools and stubdom. I was looking for a

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

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

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

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'']

Hi, When I do the "make install-tools" with xen-4.2-unstable, there are some errors about "warn_unused_result". Is it the error in code or the error in the compiling environment? Thank you so much. gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .tapdisk-queue.o.d

I''m currently working on moving storage services into their own domain and I''ve been looking at blktap2. I''ve been trying to get an image mounted with blktap2 and for some odd reason and tapdisk2 keeps hanging instead of quitting at the end. I haven''t removed any of the storage startup code at this point so everything should be as it normally is in xen-unstable.

Hi everyone, I am working on a project whose goal is evaluating the performance of the vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13 with Fedora11. I I finished all installation and configuration parts. Now I need to boot the system with Xen but while booting, it is freezing at the step "scrubbing free ram". What can be cause this problem and how can I figure it

Hi everyone, I am working on a project whose goal is evaluating the performance of the vTPM Manager. For this project I am using Xen 4.1, Kernel 2.6.31.13 with Fedora11. I I finished all installation and configuration parts. Now I need to boot the system with Xen but while booting, it is freezing at the step "scrubbing free ram". What can be cause this problem and how can I figure it

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.

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.

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.

Hello, I have been playing around with Remus on Xen 4.0.1, attempting to fail-over for an HVM domU. I''ve run into some problems that I think could be related to tapdisk2 and its interaction with how one sets up Remus disk replication in the domU config file. A few things I''ve noticed: -The tap:remus:backupHostIP:port|aio:imagePath notation does not work for me, although this

Hi! When I try to compile xen-unstable on Sarge, I get this error and I don''t know how to solve it: make[3]: Entering directory `/root/xen-unstable/tools/blktap/drivers'' gcc -O2 -fomit-frame-pointer -DNDEBUG -m32 -march=i686 -Wall -Wstrict-prototypes -D__XEN_TOOLS__ -fPIC -Wall -Werror -Wno-unused -g3 -fno-strict-aliasing -I ../../../tools/libxc -I ../../libaio/src -I..