similar to: tap:aio doesn''t work with xm command

Hi All, I report new results of dm-ioband bandwidth control test. The previous test results were posted on Jan 25. I've got really good results as well as the last report. dm-ioband works well with Xen virtual disk. I also announce that dm-ioband website has launched. The patches, the manual, the benchmark results and other related information are available through this site. Please check it

Hi All, I report new results of dm-ioband bandwidth control test. The previous test results were posted on Jan 25. I've got really good results as well as the last report. dm-ioband works well with Xen virtual disk. I also announce that dm-ioband website has launched. The patches, the manual, the benchmark results and other related information are available through this site. Please check it

Hi All, I report new results of dm-ioband bandwidth control test. The previous test results were posted on Jan 25. I've got really good results as well as the last report. dm-ioband works well with Xen virtual disk. I also announce that dm-ioband website has launched. The patches, the manual, the benchmark results and other related information are available through this site. Please check it

Hi there. I cannot start xen, I''m getting this error System: Linux netwarrior 2.6.31.13 #5 SMP Wed Jun 30 13:25:47 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linux xend.log le "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 355, in Mkdir complete(path, lambda t: t.mkdir(*args)) File

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

Hi, xen-3.0.3-41.el5 on RHEL5.1 I''m trying to use tap:aio thusly: disk = [ ''file:/var/lib/xen/images/webmail.golden.net.img,hda,w'' _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, I read the blktap readme; there is a section there titled: Mounting images in Dom0 using the blktap driver. It says there that you can mount an image by: xm block-attach 0 tap:aio:<FILENAME> /dev/xvda1 w 0 mount /dev/xvda1 /mnt/disk <--- don''t use loop driver This option also appears in: http://wiki.rpath.com/wiki/Xen_DomU_Guide I assume that this option is not

Hello, This is a second post, with a trial which is different from the first one , in order to solve my blcok-attach problem. I tried the following two actions, according to the blktap readme: qcow-create 1000 qcowFile.img Creating file size 1048576000 Created cksum: 1813725440 then xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0 I see in the /var/log/xen/xend.log: [2007-03-13

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

Package: xen-utils-common Version: 4.1.3-6 Severity: minor Dear Maintainer, I am trying to run the following command on a dom0 Debian server in order to mount a vmware vmdk. I don't want to use kpartx or losetup as they have poor write performance and I'm hoping blktap will provide better performance. xm block-attach 0 tap:vmdk:/mnt/backup/3MSYDDP01/3MSYDDP01_2-flat.vmdk /dev/xvda1 w 0

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

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

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

Hello all, I just notice the new feature in the latest version 4 release. Any one know how to do this ? I have tried lvextend the partition size in dom0, but domU doesn''t see the change. I also need to reboot to make domU reread the block size. Any idea? Best regards, Chao-Rui _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

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

Hi all I was reading through Xen 3 user manual and saw this tap:aio should be used instead of loopback... Then I came to do that, but I can get it working with replacing `file'' URI''s with `tap:aio''. My OS: Debian Lenny 2.6.26-2-xen-amd64 DomU Xen configuration file: kernel = ''/boot/vmlinuz-2.6.26-2-xen-amd64'' ramdisk =

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++