similar to: qemu VS tapdisk2 VS blkback benchmarks

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

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

Hi all, Suppose tapdisk2(a) serves Dom1, tapdisk2(b) serves Dom2, when both Dom1 and Dom2 are issuing random write requests, is it possible for tapdisk2(a) to dispatch requests both from Dom1 and Dom2? I hope not, but when I trace the I/O in Dom0, I notice that tapdisk2(a) dispatches requests from both guest domains. Is it common? I thought each tapdisk2 should only dispatch requests from its own

Hi there, I just found a segfaulting tapdisk2 process which led into a kernel oops. [1527071.169682] tapdisk2[26548]: segfault at 7fffd324cfe8 ip 000000000040837f sp 00007fffd324cff0 error 6 in tapdisk2[400000+38000] [1527071.220104] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048 [1527071.220170] IP: [<ffffffff810ce73c>] apply_to_page_range+0x47/0x2f3

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

You''re right scout the last line. Out looks like xapi is waiting on tapdisk to plug a key into xenstore. Perhaps a udev rule problem? Perhaps someone who knows more about tapdisk than I well be able to diagnose this tomorrow. Mike Sent from Samsung tablet Sébastien RICCIO <sr@swisscenter.com> wrote: Of course, here it is attached. Last line seems interesting. However tapdisk2

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1300271932 0 # Node ID 7e326d27d899a3133479c8b7c983f660cdeda48c # Parent f35234b6636a0410a7d5eaa409e98ebe59080e4f tools: do not link against unused libraries. A fair few things under tools link against libraries which they don''t even use. Most of this appears to come from copy-and-pasting previous Makefile

Hi, Just wondering if anyone can point me to the new locations for xen/next-3.0 repo? git.kernel.org doesn''t appear to be coming back up (http://www.theregister.co.uk/2011/09/06/linus_torvalds_dumps_kernel_for_github/) and the XenParavirtOps wiki page still refers to that. Searching the list didn''t seem to come up with anything. Thanks, Nathan -- Nathan

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

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

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

I have a problem that tap:tapdisk:vhd:... is never actually plugged in. What can be the reason of such a thing happening? John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

We''ve been working on getting XEN 4.1.2 validated for internal use and have run into what appears to be a livelock induced failure in properly freeing a blktap2 device. We ported the blktap2 driver from Dan Stodden''s GIT tree into 3.2.x which is a reasonably straight forward process. We are also running the toolchain with a patch which Ian Campbell posted in order to get xl to

This commit delays the point at which bdrv_new (and hence blk_open on the underlying device) is called from blk_init to blk_connect. This ensures that in an inbound live migrate, the block device is not opened until it has been closed at the other end. This is in preparation for supporting devices with open/close consistency without using O_DIRECT. This commit does NOT itself change O_DIRECT

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

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

Hi, One of our colleagues spotted a problem in xentop. Sometimes the VBD_WSECT value suddenly becomes unreasonably high, and it turned out xentop reads /sys/bus/xen-backend/devices/vbd-(domid)-(devID)/statistics/wr_sect into an unsigned long long. That value is exposed by blkback, and among other stat counters, it''s a signed integer: drivers/block/xen-blkback/common.h struct

Hello Roger Pau Monne, The patch 4d4f270f1880: "xen-blkback: move free persistent grants code" from Nov 16, 2012, leads to the following warning: drivers/block/xen-blkback/blkback.c:238 free_persistent_gnts() warn: 'persistent_gnt' was already freed. drivers/block/xen-blkback/blkback.c 232 pages[segs_to_unmap] = persistent_gnt->page; 233