Re: [Xen-devel] [PATCH] [RESEND] Don't mount raw blktap disks for pygrub

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

What is the broken thing that you are trying to fix with this patch?
The current code works fine and treats all tap-based devices equally,
while this new code special-cases certain tap-based drivers (aio and
sync).

a.

On 3/7/07, Mark McLoughlin <markmc@xxxxxxxxxx> wrote:
> (Doesn't seem to be in the staging tree; re-sending just in case it
> slipped through the cracks)
>
> Hi,
>         Currently, we mount all blktap disks for pygrub so that it can boot
> from e.g. QCOW images. However, since pygrub will handle a raw image
> just fine without mounting through blktap, we shouldn't bother in that
> case.
>
>         Also, it looks like XendDomainInfo.create_vbd() takes the full disk
> uname rather than the image path.
>
>   Signed-off-by: Mark McLoughlin <markmc@xxxxxxxxxx>
>
> Cheers,
> Mark.
>
> _______________________________________________
> 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