Re: [Xen-devel] printk calls in xen-blkback/blkback.c not appearing

[Misiu Godfrey <misiu.godfrey@xxxxxxxxx>]

Pardon, when I said "sparse install" I was referring to the domU OS I
installed using debootstrap (Ubuntu running a 2.6.38-15-generic-pae
kernel).

The modifications I am working on relate to any hard drive disk
accesses from DomUs, not just raw ones. It seems, from your comments,
that I might have been mistaken in assuming that blkback was a common
interface for this.  Is there a common interface that all DomU disk
I/O requests need to pass through or am I better off modifying each
driver separately?

Thanks for your help,

-Misiu

On Tue, Jan 29, 2013 at 11:47 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Tue, 2013-01-29 at 16:39 +0000, Misiu Godfrey wrote:
>> I am running a dom0 with Ubuntu 12.04 with kernel version 3.2.28 and
>> two domUs with sparse Ubuntu installs.
>
> blkback only supports raw block devices, so if by sparse images you mean
> files in dom0 (raw sparse files, qcow, vhd etc) rather than block
> devices (/dev/lvm/blah etc) then you are using some other backend and
> not blkback, perhaps blktap or qdisk (part of qemu).
>
> You can tell which by looking at the name of the backend directory in
> xenstore.
>
> Ian.
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel