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

[Xen-devel] Re: Getting VBD working with xenstore, again

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jacob Gorm Hansen <jacobg@xxxxxxx>
  • Date: Thu, 12 Jan 2006 15:42:12 +0100
  • Delivery-date: Thu, 12 Jan 2006 14:49:09 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SzyoflwSeUgILVn9uV3BN1B2f8bGQTwZpg1W17JWqGt/M5qNNIOGYI3Pg9qF9yl8ULba4U9kEGxZOuIvAzPcm2pkOH7GQ7f2YjCU9Vh5AR6aDlPkAsUjTNAuhASVCd857KD0qhFPRAqnZSlWUwbbVISwk0j1LPq2zIBb7a9mHaI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 1/12/06, Jacob Gorm Hansen <jacobg@xxxxxxx> wrote:
> hi,
> I have the code below, a version of which used to (just before xen3
> release) work fine for giving my domain access to a block device. I
> have tried to adjust this based on the python source, but my block
> device no longer registers in domU :-(

Got it working, main points was that I had to reverse the order of
writing to frontend and backend stores (probably not new actually),
that the physical-device string is now in "%x:%x" format (but the
virtual-device is not...) and that the the mode key is mandatory.


Xen-devel mailing list



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