From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Gardner Subject: More on domU not starting Date: Tue, 11 Oct 2005 15:25:20 -0600 Message-ID: <434C2DC0.10701@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xs: This Python has API version 1012, module xen.lowlevel.xs has version 1011. from xen.lowlevel import xs Xend does seem to start ok, and xm seems to run ok. But domU still can't find its boot disk. In the boot messages I see: xen_blk: Initialising virtual block device driver But following that I see no message like Registering block device major 3 which I normally see on a working system. The non-working system has python 2.3.4 on it. Could this be a problem? My disk config is: disk = [ 'file:/xen/disk-images/dom1.fs,sda1,w'] The strange thing is if I change the filename to something non-existent, the behavior stays the same. The disk image file does exist and is in good shape. Rob