similar to: xen 4.1.1 + 3.0.0-rc5 dom0 + blktap2

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

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

Hi, Ooops, mistake, please read host# tapdisk2 -n vhd:/storage/test.vhd instead of host# tapdisk2 -n vhc:/storage/test.vhd in my previous post. Kind regards, Sébastien _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

Hi folks, I met a problem: when 6 VM reboot at the same time, 3:00 morning, the Dom0 reboot it self: Xen version is 4.0.0, VMs are windows 2003 with redhat pv, they will update and reboot itself every 3:00 AM. # last ... ... admin pts/0 10.247.1.1 Fri Jun 25 03:40 - 04:30 (00:50) reboot system boot 2.6.31.13 Fri Jun 25 11:16 (00:-3) admin pts/0

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

Have an interesting one here, originally found on xen 4.1.0 but just upgraded to xen 4.1.1 and it''s still here. Creating a VM with a tap2 device pointed at /dev/mapper/something, when that device doesn''t exist, causes the tapdisk2 process to go into D mode and also manages to take out any process that queries it. For example, I have /dev/mapper/nathanxenuk1 as a valid disk

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

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

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

--------------------------------------------------------------------------- Backport of the following patch from development: # User Ian Campbell <[hidden email]> # Date 1309968705 -3600 # Node ID e4781aedf817c5ab36f6f3077e44c43c566a2812 # Parent 700d0f03d50aa6619d313c1ff6aea7fd429d28a7 libxl: attempt to cleanup tapdisk processes on disk backend destroy. This patch properly terminates the

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

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

Hi, I''m trying to run guest pv vm on my machine running xen-unstable (xen-4.0.0-rc3.pre + linux-2.6-pvops). However, I get blktap error: " sudo xm create -c xmexample Using config file "./xmexample". Error: Failed to create device. stdout: unrecognized child response stderr: Check that target "/home/ashish/xen/hd.img" exists and that blktap2 driver

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

I was wondering if someone can shed some light on why vhd files created with qemu-img don''t really work right with vhd-util and consequentially blktap in general. To validate the incompatiblity its simple enough to do qemu-img create -f vpc test.vhd 40g vhd-util snapshot -n child.vhd -p test.vhd Which will show the below and then the headers don''t display the BATMAP summary:

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.

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, Currently i''m going through the source codes of tools/blktap2. I need to find-out where blktap2 calls 1. mem_share_nominate() 2. mem_sharing_share_page() functions to do the memory sharing on HVM guests. Can someone please provide me some guidance on blktap2 driver. Thanks, Harshan _______________________________________________ Xen-devel mailing list