All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hp.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: exception looking up device number f,or hda
Date: Mon, 08 Aug 2005 09:08:51 +0100	[thread overview]
Message-ID: <42F71313.4010201@hp.com> (raw)
In-Reply-To: <42F3BF2C.70403@intel.com>

Arun Sharma wrote:
> Hi Mike,
> 
> I have the following line in my config file:
> 
> disk = [ 'file:/var/images/min-el3-i386.img,hda,w' ]
> 
> and my host doesn't have a /dev/hda (it has a SATA disk which shows up 
> as /dev/sda).
> 
> But I would like the guest to see a /dev/hda. Sounds reasonable?
> 
> Now, when I try to create this domain, I get:
> 
> [2005-08-05 14:40:53 xend] DEBUG (blkif:24) exception looking up device 
> number for hda: [Errno 2] No such file or directory: '/dev/hda'
> 2005-08-05 14:40:53 xend] DEBUG (blkif:449) Destroying blkif domain=1
> [2005-08-05 14:40:53 xend] DEBUG (blkif:337) Destroying vbd domain=1 id=0
> 
> The code in util/blkif.py that tries to convert name to device number 
> doesn't seem to be new, but I don't know why it started showing up 
> suddenly.
> 
> I worked around by manually creating /dev/hda, but I don't think it's 
> reasonable to expect that host's /dev contains entries for all guest 
> devices.

No, and the blkdev_name_to_number() function should convert names like /dev/hda
without the device existing. This code should be trapping the error:

     try:
         return os.stat(n).st_rdev
     except Exception, ex:
         log.debug("exception looking up device number for %s: %s", name, ex)
         pass

The code then uses regexps to analyse the device name (though you will see
the debug message in the log).


What xen version are you using?

> 
> Also, the effect of having a bad "disk=" line in xmdefconfig (such as 
> pointing to a non-existent file) results in a xend crash. We probably 
> need to add a few checks at the python level so that the user sees a 
> more useful stack trace.

All errors during domain construction are intended to be trapped and returned
to the caller - so maybe something got broken.
Did you see anything in the xend log?
Might be worth causing the error using xend with tracing on (xend trace_start)
and having a look at the trace (/var/log/xend.trace).

Mike

      parent reply	other threads:[~2005-08-08  8:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 19:34 exception looking up device number f,or hda Arun Sharma
2005-08-05 20:33 ` Anthony Liguori
2005-08-05 21:20   ` Arun Sharma
2005-08-08  2:21 ` takebe_akio
2005-08-08  5:38   ` exception looking up device number for hda Arun Sharma
2005-08-08 14:48     ` Mark Williamson
2005-08-09  0:06       ` Arun Sharma
2005-08-09  1:25         ` David Hopwood
2005-08-09  1:49         ` Mark Williamson
2005-08-09  2:58           ` Xiaofeng Ling
2005-08-09 18:19             ` Arun Sharma
     [not found]         ` <mailman.1123552364.22306@unix-os.sc.intel.com>
2005-08-09 19:06           ` Arun Sharma
2005-08-09 19:18             ` Mark Williamson
2005-08-08  8:08 ` Mike Wray [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42F71313.4010201@hp.com \
    --to=mike.wray@hp.com \
    --cc=arun.sharma@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.