https://bugzilla.novell.com/show_bug.cgi?id=642078
https://bugzilla.novell.com/show_bug.cgi?id=642078#c3
--- Comment #3 from James Fehlig
I think using the upstream xen 4.0.1 way could make the problem go away, any reason why we are handling tapdisk with qemu-dm?
During SLES11 development, Kevin changed blktapctrl to use qemu's tap drivers instead of the duplicated code in tools/blktap/drivers (see blktapctrl-default-to-ioemu.patch). The intent was development of new features and fixing of bugs would occur in one code base only - the qemu code. The code is more actively maintained in the qemu project anyhow. Not much has changed in tools/blktap/drivers. As an example, there has been a lot of work on on qcow2 (much of it by Kevin) in upstream qemu but tools/blktap/drivers/block-qcow2.c in the xen tree has not changed in 19 months, and that was to fix compile warnings! Is using the qemu drivers instead of tapdisk ones causing this problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.