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

Re: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)

  • To: Brendan Cully <brendan@xxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 02 May 2007 16:19:31 +0100
  • Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 02 May 2007 08:18:21 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceMzUgmhvK71PjAEduO2AAX8io7RQ==
  • Thread-topic: [Xen-devel] blktap failure after 14895:800aa9f5cec9 (moves /dev/xen/... to /var/run/tap/...)

On 2/5/07 16:11, "Brendan Cully" <brendan@xxxxxxxxx> wrote:

>> More likely it's simply because /var/run/tap/ doesn't exist?
>> Either some startup script needs to 'mkdir -p', or blktapctrl needs to make
>> the directory on demand.
> the blktap tools do create that directory on demand, and in fact
> /var/run/tap/blktap0 is properly created. What fails is the 'open',
> somewhere in the kernel I believe. Maybe this only affects
> block-attaching a device in domain 0?

The open() that's part of mkfifo()? Those FIFO files have nothing to do with
the blktap kernel module, I believe, in which case this can't have anything
to do with a mismatch of something between blktap user and blktap kernel.

 -- Keir

Xen-devel mailing list



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