From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: blkdev_name_to_number issues while running xenU Date: Thu, 25 Aug 2005 10:53:44 +0100 Message-ID: <3d8eece20508250253735bc3af@mail.gmail.com> References: <430CEA90.3030608@intel.com> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <430CEA90.3030608@intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Arun Sharma Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 8/24/05, Arun Sharma wrote: > File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 410, in > createDevice > backdb['physical-device'] =3D "%li" % blkdev_name_to_number(node) > File "/usr/lib/python/xen/util/blkif.py", line 27, in > blkdev_name_to_number > if re.match( '/dev/sd[a-p]([1-9]|1[0-5])?', n): You might find it helpful to add something like log.error(node) in XendDomainInfo.py before the line which calls blkdev_name_to_number and see what's in node. christian