[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH] [RESEND] Don't mount raw blktap disks for pygrub
- To: "Mark McLoughlin" <markmc@xxxxxxxxxx>
- From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
- Date: Wed, 7 Mar 2007 08:35:54 -0800
- Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- Delivery-date: Wed, 07 Mar 2007 08:34:58 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=XcTQ9JnZk3uzDcOTc5QegZE4mc7TWkBoTyNj/rZYOWR9giQ1rkFftZV/jrGZTNZZpoBf6dZ/3G6LZuvJT15iuP+0gw9cj1pJxZxFAaw8BheoxUbZtKkT6+zDETKmkl8TgEHWVpdohYeUTo5DFIdhr9FMD55Z4wIwnmWo1guIg/4=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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
|
