From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: exception looking up device number for hda Date: Mon, 08 Aug 2005 17:06:54 -0700 Message-ID: <42F7F39E.3020300@intel.com> References: <42F3BF2C.70403@intel.com> <3FC59BBFF4B882takebe_akio@jp.fujitsu.com> <42F6EFE2.8010107@intel.com> <200508081548.18887.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200508081548.18887.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson Cc: Mike Wray , xen-devel@lists.xensource.com, takebe_akio@jp.fujitsu.com List-Id: xen-devel@lists.xenproject.org Mark Williamson wrote: >>I was looking for suggestions as to how: >> >>a) IDE hard drives for VMX domains should be configured >>b) VBD based devices for VMX domains should be configured > > > Ah, I guess we have to distinguish the two... > > Hope about an optional: vbd:/emu: prefix (or similar) on the second part of > the triplet for a disk? The default (for non VMX domains) could be "vbd" so > existing behaviour would remain the same. Sounds good to me. How about: hda = VBD hda vbd://hda = VBD hda ioemu://hda = IDE hda The VBD patches are not ready yet - so I'd like to propose that we do: - self.create_configured_devices() + if self.image.ostype != 'vmx': + self.create_configured_devices() and - self.create_blkif() + if self.image.ostype != 'vmx': + self.create_blkif() When our VBD patches are ready, we'll revert this. -Arun