Re: [Xen-devel] PATCH: Enable QEMU booting of blktap disks

["Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>]

So two comments on this:

In the other thread that's currently going on this topic, it sounds
like others are quite successfully using the phantom code.  Why is it
broken for you?

As I've said before, I dislike the idea of having separate
implementations of disks -- one in qemu and one in tapdisk.  We'd
quite like to encourage people to be able to extend virtual block
devices in the future, and it seems like your approach is going to
force them to do two independent implementations of things.  It also
leads to complications if you want to add things like caching, shared
ramdisks, etc.  If phantom is broken, why don't we just fix that?

a.

On 7/19/07, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
> This is a re-send of previous patches:
>
> http://lists.xensource.com/archives/html/xen-devel/2007-06/msg01021.html
>
> The only change is that it explicitly looks for the driver type in xenstore
> rather than assuming 'xvd' == 'tap' - this is because tap could be configured
> with 'hd' or 'sd' nodenames too, and we still need to strip the leading
> ':aio' or ':vmdk', etc prefix from the path.
>
> There are two patches:
>
>   - xen-revert-phantom-2.patch  removes the phantom device code since it
>     doesn't work & is redundant if QEMU can process tap devices straight
>     from xenstore
>
>   - xen-qemu-blktap-2.patch makes QEMU able to handle disks with xvd prefix
>     treating them as IDE. Also makes QEMU strip the driver type prefix from
>     tap disks since it can auto-guess driver
>
>
>    Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx>
>
> Dan.
> --
> |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
> |=-           Perl modules: http://search.cpan.org/~danberr/              -=|
> |=-               Projects: http://freshmeat.net/~danielpb/               -=|
> |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel