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

RE: [Xen-users] GPLPV under NetBSD dom0


  • To: "Dustin Marquess" <dmarquess@xxxxxxxxx>, "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Fri, 30 Oct 2009 10:35:33 +1100
  • Cc:
  • Delivery-date: Thu, 29 Oct 2009 16:36:22 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcpY5BXiWHhdaRJNTpuBR31/hzD/cQAC82aw
  • Thread-topic: [Xen-users] GPLPV under NetBSD dom0

> 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.

James

_______________________________________________
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®.