This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] GPLPV under NetBSD dom0

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] GPLPV under NetBSD dom0
From: Dustin Marquess <dmarquess@xxxxxxxxx>
Date: Thu, 29 Oct 2009 22:06:09 -0500
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 29 Oct 2009 20:06:49 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=i0Evdt3LOuUQg269bFVeUQZAczbPscbHSeft5sewQZE=; b=Uu4V8PhXV+4QUcq5y+DtMn6qiZYS6g9/tzSgTiYE0XokH0EgNBJBS+wH0IcDvjG/CN aGJobs3FbDvEuBnyubtVHHjPcueSk5NmoCO4gaQ65VStGv6b69R9RjNkzoISYSCtfug9 ANXlDmndSCoYFbs/GJTT/G3ZL5K3250tgb7ac=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xRFJiUX9qB2NrVIU039uzSCV6CFCGE89gpNJ5LooLu/odsDperoIsH9hWxK45j1LCD gmTq+iHPYt0av9YNdrAi79LaLj0XtLrC8ntkbytm00acVpiSIPm6flc9unDJ2lBHvdFv 4nvqMKgT+jr5yU0dQ78IsvpSW6L+a2hyUG9w4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0180D09F@trantor>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1aa643d80910291504k75a3dfa6ne0cd8ad5904d2b4e@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0180D09F@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Oct 29, 2009 at 6:35 PM, James Harper
<james.harper@xxxxxxxxxxxxxxxx> wrote:
>> XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers
>> XenPCI     testing path = device/vbd/768/device-type
>> XenPCI     testing disk vs disk
>> XenPCI     condition = 0
>> XenPCI --> XenPci_ChangeFrontendState
>> XenPCI --> XenPci_DeviceWatchHandler
>> XenPCI <-- XenPci_DeviceWatchHandler
>> XenPCI --> XenPci_UpdateBackendState
>> XenPCI     state unchanged
>> XenPCI     Still waiting for 2 (currently 4)...
> Looks like my state transition code isn't quite compatible with NetBSD's
> backend code.
> Just as a test, and you'll have to be fast, as soon as you see 'Still
> waiting for 2 (currently 4)', manually set the backend state to 2, and
> then back to 4, eg:
> xenstore-write /local/domain/0/backend/vbd/<domid>/768 2
> xenstore-write /local/domain/0/backend/vbd/<domid>/768 4
> GPLPV expects to see the backend state go to 2 and then to 4, not direct
> to 4. I need to investigate that a bit more as it has caused problems
> before with other backends (tap:aio etc) before.
> If that works let me know and I'll see what I can do.

I tried this a few times and ended up pulling my hair.  After some
poking around, I realized I needed to add "/state" to the path.  Once
I did that, surprise surprise... it worked!

On an unrelated note... WinDbg is getting spammed with:

XenNet     Error: rxrsp offset 16, size -1
XenNet     Error: rxrsp offset 16, size -1
XenNet     Error: rxrsp offset 16, size -1
XenNet     Error: rxrsp offset 16, size -1

And my dom0 dmesg is getting spammed with:

xvif18.1: req_prod 713 req_cons 466 rsp_prod 465 rsp_prod_pvt 465 i 1
xvif18.1 GNTTABOP_transfer[0] -1
xvif18.1: req_prod 713 req_cons 467 rsp_prod 466 rsp_prod_pvt 466 i 1
xvif18.1 GNTTABOP_transfer[0] -1
xvif18.1: req_prod 713 req_cons 468 rsp_prod 467 rsp_prod_pvt 467 i 1
xvif18.1 GNTTABOP_transfer[0] -1
xvif18.1: req_prod 713 req_cons 469 rsp_prod 468 rsp_prod_pvt 468 i 1

So I assume there's a problem with the network driver.  However at
least it's booting at not BSOD'ing, so it's a step in the right


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>