similar to: [Patch] blktap: Remove some code duplication

qemu-xen: Fix open_disk for blktap disks If blktap drives are registered properly, qemu code is much less likely to get confused by them. Use bdrv_new(), assign a device name and create an entry in drives_table for them. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

When a domain wants to use a tap:ioemu disk but has no device model, start a tapdisk-ioemu instance as provider. Also, move the creation and removal of communication pipes to xend so that qemu-dm doesn''t need the unwanted SIGHUP handler anymore. Signed-off-by: Kevin Wolf <kwolf@suse.de> _______________________________________________ Xen-devel mailing list

Hello, i am experiencing something weird on my Xen Dom0 Since a few days, i can no more install or reboot any vm using tap:aio driver My vms complains about no mounted disks OS: On openSUSE 11.2 (x86_64) with xen-tools-3.4.1_19718_04-2.1.x86_64 kernel-xen-base-2.6.31.8-0.1.1.x86_64 xen-libs-3.4.1_19718_04-2.1.x86_64 kernel-xen-2.6.31.8-0.1.1.x86_64

Hi All, I sent the patch to make blktap work with PV-on-HVM. I corrected the part that had been pointed out in the Xen community. ・All xvdN disk is looked like hdN. ・All tap disks are checked.(tap:aio, tap:sync, tap:vmdk, etc.) We cannot use blktap for the volume of the system with PV-on-HVM and are embarrassed. Could you apply this patch? Or, please give the comment to me. Signed-off-by:

Package: src:blktap Version: 2.0.90-3 Severity: normal Tags: sid stretch User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-5 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built

Hi All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Hi I''ve been trying to play with the new blktap support in xen-unstable. First, an observation - blktapctrl is pinned at 100% CPU: ----------------------------------------------------------------------------------------------------------------- top - 17:29:48 up 4 days, 2:02, 3 users, load average: 0.90, 1.01, 1.00 Tasks: 83 total, 3 running, 80 sleeping, 0 stopped, 0 zombie

I''m getting this: blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_device_create: minor 0 sectors 20971520 sector-size 512 blktap_device_create: creation of 253:0: 0 INFO: trying to register non-static key. the code is fine but needs

Hi everyone, as what I''ve learned form this link<http://wiki.xensource.com/xenwiki/blktap>, i know that when i specify tap:aio I’m actually using the blktap driver and finally using "tapdisk" to wirite to raw image file. but the truth is even when i delete /usr/sbin/tapdisk the domU can still boot on my machine with tap:aio protocol after a deeper look into the scene,

hi, i''m trying move from file: based disk to tap:aio but things don''t work i have centos4 dom0 with centos4 domU xen 3.0.4-testing changeset: 13138:d401cb96d8a0 self compiled [root@xen linux-2.6.16.38-xen]# grep XEN_BLKDEV_TAP .config CONFIG_XEN_BLKDEV_TAP=m config disk = [ ''file:/var/lib/xen/test.img,hda1,w'',

Hello, I have a small problem with the blktap, that when I use "tap:aio" protocol to access my disk, the domU stop booting with following message: [ 0.185031] PCI: Fatal: No config space access function found [ 0.189998] Unable to read sysrq code in control/sysrq [ 0.350220] i8042: No controller found [ 0.452153]

tags 490409 + patch thanks Hi, The following is the diff for my xen-3 3.2.1-2.1 NMU. It incorporates three patches from upstream and aims to fix CVE-2008-2004 aka #490409. It is not yet tested much, I would appreciate if interested parties could give it a try. I'll upload in due course. Kind regards T. diff -u xen-3-3.2.1/debian/control.md5sum xen-3-3.2.1/debian/control.md5sum ---

Recently we had a try of stubdom, whose general status is good. One issue we found is with aio/sync blktap as backend, disk performance is obviously slower, and there are some IDE kernel error messages (like irq timeout) at boot time. Another issue (not stubdom specific) comes from blktap''s support for QCOW image which is based on a backing file. We never tried this configure

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

When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O

Hi,mail list members, As needed by my test, blktap/blktap2 modules have to work after new VMs start.Maybe the line about disk in the vm creation configure file is the right position where I should be supposed to specify the function of blktap/blktap2 modules.But specifically I don''t know how to configure the disk line.Who can help me? hxk

Hi All, I'm seeing tapdisk processes not being terminated after a HVM vm is shutdown or migrated away. I don't see this problem with linux paravirt domu's, just windows hvm ones. xl.cfg: name = 'nathanwin' memory = 4096 vcpus = 2 disk = [ 'file:/mnt/gtc_disk_p1/nathanwin/drive_c,hda,w' ] vif = [ 'mac=00:16:3D:01:03:E0,bridge=vlan208' ] builder =

The following two fixes by Jürgen Keil have been in qemu for a year now. They are still missing in ioemu. [Qemu-devel] PATCH: qcow2 image corruption http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00773.html [Qemu-devel] [PATCH] qcow2: release refcount table clusters of the old table, after growing the refcount table http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00043.html

Can anyone explain to me why tap:aio sucks so badly? We''ve got numerous CentOS 5 dom0s running file-backed domUs with tap:aio. The moment any one of them starts doing something disk-intensive, idle CPU in dom0 decreases, iowait increases, and disk IO for every other domU on the system suffers. Where lies the problem, and what to do about it? Sincerely, Ray Barnes