From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ralph Passgang Subject: Re: Debian kernel doesn't support DomU bit width != Dom0 bit width for PV drivers? Date: Fri, 01 Feb 2008 23:48:30 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 01.02.08 23:40, "James Harper" wrote: >>> >>> My suspicion then is that the Debian kernel's blkback driver doesn't > pay >>> attention to the 'protocol' set by the frontend, even though > blkfront >>> driver included in the Debian kernel does actually set it. >> >> Depends what Xen version their kernel / userspace is based on. IIRC > you >> need to have at least Xen 3.1.1 to get 32-on-64 working properly - > the >> compatability 'protocol' stuff didn't make the original 3.1.0 release >> > > I am using 3.1.1, but I think the Debian kernel is 3.1.0 vintage. Which Debian Kernel? The 2.6.18-5-xen-686/amd64 kernel is quite old and based on some redhat kernel patch from around Xen 3.0.x. It's definitly too old for mixing 64bit and 32bit machines (pv) up. Please use a newer kernel for both dom0 and domU, if you need help with that, let me know. > And I was incorrect when I said that blkfront is setting 'x86_NN-abi'. > That is being done by the xen userspace stuff. It's all making sense > now! > > Curiously, the HVM stuff works perfectly with the single exception of > vbd, and only because of the alignment issues in the two related > structs. > > I think I'll fudge it and release two versions of the PV drivers, one to > use when Dom0 is 32 bit and one to use when Dom0 is 64 bit. > > James > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel