From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: grant table errors with qemu-xen-traditional Date: Wed, 20 Jun 2012 17:12:46 +0200 Message-ID: <20120620151246.GA18207@aepfle.de> References: <20120620121539.GA18219@aepfle.de> <4FE1E823020000780008AD6B@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4FE1E823020000780008AD6B@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Jun 20, Jan Beulich wrote: > >>> On 20.06.12 at 14:15, Olaf Hering wrote: > > > I'm not sure if thats guest or host related, but current xen-unstable > > with device_model_version="qemu-xen-traditional" fail to access the > > block device properly, both PV and HVM are affected. The guest runs the > > upcoming 12.2 kernel, which is based on forward ported xenlinux sources. > > > > I added f7f8c33cd49885d69efc2e5f7f9a613d631762e2 to > > qemu-xen-traditional, but that does not seem to help. > > > > Any idea whats wrong? > > Did you verify that the added code actually gets executed? The > log messages provided suggest that the limit didn't really get > raised from its default of 128. The patch applied with fuzz, so patch decided to put the change into blk_disconnect() instead of blk_alloc(). With a correctly refreshed patch qemu-xen-traditional works again. Olaf