WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] bug in starting xen machines - expectation of /dev/sda1

To: Luke Kenneth Casson Leighton <lkcl@xxxxxxxx>
Subject: Re: [Xen-devel] bug in starting xen machines - expectation of /dev/sda1 existing on *host*
From: "M.A. Williamson" <maw48@xxxxxxxxx>
Date: 30 Dec 2004 14:25:03 +0000
Cc: xen-devel@xxxxxxxxxxxx
Delivery-date: Thu, 30 Dec 2004 14:26:23 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <20041230104930.GN7161@xxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <20041230104930.GN7161@xxxxxxxx>
Reply-to: maw48@xxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
This is a known limitation... :-(

... what has the existence or otherwise of /dev/sda1 on the
xen master machine got to do with the guest OSes?

In order to create the guest, Xend needs to look up the major / minor for the device name in the guest you specified. It has to do this on dom0's filesystem, so if there isn't a /dev/sda1 there it'll fail.

The current workaround is to specify the device number explicitly (e.g. phy:0801 should work for /dev/sda1).

The long-term fix would be to include a table for Xend to generate device numbers from, thus eliminating the dependency on these nodes existing in dom0.

HTH,
Mark

to "fix" this problem, you must cp -aux /.dev/sd* /dev.

l.

[2004-12-29 22:11:16 xend] DEBUG (XendDomainInfo:720) init_domain> Created domain=1 name=xenselinuxnfs memory=32 [2004-12-29 22:11:16 xend] INFO (console:92) Created console id=12 domain=1 port=9601 [2004-12-29 22:11:17 xend] DEBUG (blkif:146) Connecting blkif <BlkifBackendInterface 1 0> [2004-12-29 22:11:17 xend] INFO (XendRoot:91) EVENT> xend.console.create [12, 1, 9601] [2004-12-29 22:11:17 xend] DEBUG (XendDomainInfo:1099) Creating vbd dom=1 uname=phy:/dev/hda17 [2004-12-29 22:11:17 xend] DEBUG (blkif:63) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1' [2004-12-29 22:11:17 xend] DEBUG (XendDomainInfo:674) Destroying vbds for domain 1 [2004-12-29 22:11:17 xend] DEBUG (blkif:541) Destroying blkif domain=1 [2004-12-29 22:11:17 xend] DEBUG (XendDomainInfo:634) Closing console, domain 1 [2004-12-29 22:11:17 xend] DEBUG (XendDomainInfo:622) Closing channel to domain 1 [2004-12-29 22:11:17 xend] ERROR (SrvBase:162) op=create: vbd: Device not found: sda1 Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks
    self.result = callback(self.result, *args, **kw)
  File "/lib/python/xen/xend/XendDomainInfo.py", line 975, in <lambda>
    d.addCallback(lambda x: self.create_devices())
File "/lib/python/xen/xend/XendDomainInfo.py", line 802, in create_devices
    v = dev_handler(self, dev, dev_index)
  File "/lib/python/xen/xend/XendDomainInfo.py", line 1102, in vm_dev_vbd
    defer = ctrl.attachDevice(idx, val, recreate=recreate)
  File "/lib/python/xen/xend/server/blkif.py", line 530, in attachDevice
    dev = self.addDevice(idx, config)
  File "/lib/python/xen/xend/server/blkif.py", line 515, in addDevice
    dev = BlkDev(idx, self, config )
  File "/lib/python/xen/xend/server/blkif.py", line 318, in __init__
    self.configure(config)
  File "/lib/python/xen/xend/server/blkif.py", line 335, in configure
    raise VmError('vbd: Device not found: %s' % self.dev)
VmError: vbd: Device not found: sda1





-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel