blkdev_name_to_number issues while running xenU

blkdev_name_to_number issues while running xenU

[Arun Sharma]

Anytime I try to start xenU, it fails the first time with the traces 
below. The second invocation is ok (but doesn't boot yet - still debugging).

blkdev_name_to_number() failures don't seem to be benign this time..

	-Arun

Traceback (most recent call last):
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 566, in construct
     self.configure()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 967, in configure
     self.create_devices()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 796, in 
create_devices
     self.create_configured_devices()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 785, in 
create_configured_devices
     self.createDevice(ctrl_type, dev_config)
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 410, in 
createDevice
     backdb['physical-device'] = "%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):
   File "/usr/lib/python2.3/sre.py", line 132, in match
     return _compile(pattern, flags).match(string)
TypeError: expected string or buffer
Traceback (most recent call last):
   File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 78, in 
op_create
     dominfo = self.xd.domain_create(config)
   File "/usr/lib/python/xen/xend/XendDomain.py", line 292, in domain_create
     dominfo = XendDomainInfo.create(self.dbmap, config)
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 161, in create
     vm.construct(config)
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 573, in construct
     self.destroy()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 694, in destroy
     self.cleanup()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 665, in cleanup
     self.release_devices()
   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 717, in 
release_devices
     Blkctl.block('unbind', devdb['type'].getData(),
   File "/usr/lib/python/xen/xend/xenstore/xsobj.py", line 425, in 
__getitem__
     v = self.readChildDB(k)
   File "/usr/lib/python/xen/xend/xenstore/xsobj.py", line 521, in 
readChildDB
     raise LookupError("invalid key '%s'" % k)
LookupError: invalid key 'type'

Re: blkdev_name_to_number issues while running xenU

[Christian Limpach]

On 8/24/05, Arun Sharma <arun.sharma@intel.com> wrote:
>   File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 410, in
> createDevice
>     backdb['physical-device'] = "%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

Re: blkdev_name_to_number issues while running xenU

[Arun Sharma]

Christian Limpach wrote:
> On 8/24/05, Arun Sharma <arun.sharma@intel.com> wrote:
> 
>>  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 410, in
>>createDevice
>>    backdb['physical-device'] = "%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.
> 

The value of node was None (because I have no /dev/hda on the host).

[2005-08-25 18:30:11 xend] DEBUG (blkif:24) exception looking up device 
number for hda: [Errno 2] No such file or directory: '/dev/hda'
[2005-08-25 18:30:11 xend] INFO (XendDomainInfo:411) arun node: None
[2005-08-25 18:30:11 xend] DEBUG (blkif:24) exception looking up device 
number for None: coercing to Unicode: need string or buffer, NoneType found

	-Arun