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

[Xen-devel] xl block-attach


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
  • Date: Sun, 30 Jan 2011 14:56:07 -0500
  • Delivery-date: Sun, 30 Jan 2011 11:57:19 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=Q763IuSIfC/ePSz+LpKbSiEa+oOmJT4MmnawUjSA1CrzatqsY6pEm9bf1OptaB+OFL m/ya8bkKFLAigfXQoJXMX/MvgsInIphilm5sqzxFOy6CvO84ijjWKC1xrYbgfTHFWEHl jZKR/reybaGvaWApEe1tbSLTu4aWdcjzybQAg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

The format in which disk information is required in xl block-attach is different
than the one expected in the disk configuration option (in the config file).  It
might make sense to keep the two consistent (excluding the domain/backend dom id
additional param block-attach would require).  Would it be alright if I enforce
it in our implementation (in main_blockattach in xl_cmdimpl.c) and modify
block-attach help to reflect that change?

Kamala

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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