[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] blkfront problems: 32 bit domU talking to 64 bit dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Arun Sharma" <arun@xxxxxxxxxxxxxxx>
  • Date: Sat, 23 Jun 2007 02:05:57 -0700
  • Delivery-date: Mon, 25 Jun 2007 09:34:24 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=mPhFSlwSb5wZhG/0M3zPy9v7qfSJuSKxSIIAZFgDm90up175NQMjOlCGKPZ5a1n8ZQEjJEKkk+cMBQVmS8IAjcRYWiIZZnJN6zY2Fv3uPenzWQRFAbrzWLbFtnciLT03g8p2sSyPblgwnsQaKQUmJWgetJX5+svIYzVooLd2/84=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On a fedora core 7 (x86_64) box I checked out linux-2.6.18.hg and
compiled a 32 bit domU kernel. The kernel has problems reading the
superblock of the filesystem being mounted.

However a 64 bit domU kernel compiled from the same tree works fine,
which leads me to suspect that there may be a compatibility issue
between the dom0 backend and the domU frontend.

My dom0 kernel is the default fc7xen kernel.

Is this known? Has anyone tested this configuration?

-Arun

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.