Robin Bowes wrote:
> I'd love to post a patch, but I'm afraid I'm not a coder.
>
> I'm downloading the SRPMS as I type and I'll give it a go, but it might
> be an idea if someone with more coding skills fixes this.
>
> I'll post an update when I've had a go.
OK, I've made the change to blkfront.c but there is no xenbus_printf in
blkback.c so I didn't make that change. (I'm using xen-3.0.3 from the
FC6 SRPM)
I've rebuilt the xen RPM with this patch:
diff -ur
xen-3.0.3-rc3/linux-2.6-xen-sparse/drivers/xen/blkfront/blkfront.c
xen-3.0.3-rc3.patched/linux-2.6-xen-sp
arse/drivers/xen/blkfront/blkfront.c
--- xen-3.0.3-rc3/linux-2.6-xen-sparse/drivers/xen/blkfront/blkfront.c
2006-10-10 15:23:43.000000000 +0100
+++
xen-3.0.3-rc3.patched/linux-2.6-xen-sparse/drivers/xen/blkfront/blkfront.c
2006-11-21 01:10:54.000000000 +000
0
@@ -294,7 +294,8 @@
*/
static void connect(struct blkfront_info *info)
{
- unsigned long sectors, sector_size;
+ blkif_sector_r sectors;
+ unsigned long sector_size;
unsigned int binfo;
int err;
@@ -305,7 +306,7 @@
DPRINTK("blkfront.c:connect:%s.\n", info->xbdev->otherend);
err = xenbus_gather(XBT_NIL, info->xbdev->otherend,
- "sectors", "%lu", §ors,
+ "sectors", "%llu", §ors,
"info", "%u", &binfo,
"sector-size", "%lu", §or_size,
NULL);
I installed the resulting RPMs (xen and xen-libs) and rebooted the dom0
host.
However, the xvdb device still only shows up like this:
major minor #blocks name
202 16 782819328 xvdb
Did I not do it right?
R.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|