similar to: Livelock induced failure in blktap2.

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

--------------------------------------------------------------------------- The following patch when applied on top of: libxl: attempt to cleanup tapdisk processes on disk backend destroy. Establishes correct cleanup behavior for blktap devices. This patch implements the release of the backend device before calling for the destruction of the userspace component of the blktap device. Without

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

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

Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,

flight 17624 xen-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17624/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-oldkern 4 xen-build fail REGR. vs. 17611 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install

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

On Mar 17, 6:14pm, Howell Tam wrote: } Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA p > Hi all again, Hi, hope the weekend is going well for everyone. > > > have you found a solution for this behaviour? Cause I''m currently > > > seeing a similar result with my installation. > > I''ve been away for a few weeks and

On Mar 17, 6:14pm, Howell Tam wrote: } Subject: Re: [Xen-users] Dom0 freeze on HVM DomU Windows reboot with VGA p > Hi all again, Hi, hope the weekend is going well for everyone. > > > have you found a solution for this behaviour? Cause I''m currently > > > seeing a similar result with my installation. > > I''ve been away for a few weeks and

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

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

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

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

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

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

Hi all, as promised I run some simple benchmarks using tapdisk2 and the new qemu as disk backends. If you are in a hurry skip to the last section to see the test results. SOFTWARE REQUIREMENTS --------------------- In order to reproduce these results you need to use the new qemu with linux aio and O_DIRECT as disk backend: - apply the libxl patches that Anthony sent to the list a little while

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1316609964 -3600 # Node ID b43fd821d1aebc8671e684bfc285cda7a6002ff1 # Parent 206afa070919e3fe0b13a03f870ca2da44ab604a libxl: attempt to cleanup tapdisk processes on disk backend destroy. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 206afa070919 -r b43fd821d1ae