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/
Home Products Support Community News


Re: [Xen-devel] Problems booting VM using unified Xen kernel (x86_64)

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Problems booting VM using unified Xen kernel (x86_64)
From: "David F. Barrera" <dfbp@xxxxxxxxxx>
Date: Wed, 03 May 2006 16:16:25 -0500
Delivery-date: Wed, 03 May 2006 14:16:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44590BAC.3090407@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44590BAC.3090407@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.7.12-1.4.1
I need to pint out that I am seeing this problem only on an x86_64 machine. i386 is working as expected.


David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "

David F. Barrera wrote:

I am having trouble booting a guest domain using the unified Xen kernel (it works fine when using the XenU kernel). Whenever I try to create the domain, I get
the following message:
bl2-1:/tmp/xen # xm create -c vm1.cfg
Using config file "vm1.cfg".
Error: (9, 'Bad file descriptor')

The build was done using 'make world' and 'make install', and there were no
build errors:

Xen version 3.0-unstable (root@xxxxxxxxxxxxxxxxxx <mailto:root@xxxxxxxxxxxxxxxxxx>) (gcc version 3.3.3 (SuSE
Linux)) Wed May  3 14:23:44 CDT 2006
Latest ChangeSet: Wed May  3 07:33:01 2006 +0100 9920:915d5af5dc18
'strace' shows that files are missing:

stat("/usr/lib64/python/xen/xm/signal", 0x7fffffe08e40) = -1 ENOENT (No such
file or directory)
open("/usr/lib64/python/xen/xm/signal.so", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/lib64/python/xen/xm/signalmodule.so", O_RDONLY) = -1 ENOENT (No such
file or directory)
open("/usr/lib64/python/xen/xm/signal.py", O_RDONLY) = -1 ENOENT (No such file
or directory)
open("/usr/lib64/python/xen/xm/signal.pyc", O_RDONLY) = -1 ENOENT (No such file
or directory)
futex(0x501680, FUTEX_WAKE, 1)          = 0
write(2, "Error:", 6Error:)                   = 6
write(2, " ", 1 )                        = 1
write(2, "(9, \'Bad file descriptor\')", 26(9, 'Bad file descriptor')) = 26
write(2, "\n", 1


domU config file:

kernel = "/boot/vmlinuz-2.6-xen"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.16-xen"
# The domain build function. Default is 'linux'.
# Initial memory allocation (in megabytes) for the new domain.
memory = 256
# A name for your domain. All domains must have different names.
name = "vm1"
disk = [ 'phy:sdb3,0813,w','phy:sdb2,0812,w' ]
# Set if you want dhcp to allocate the IP address.
# vif = [ 'mac= AA:00:00:47:CB:34, bridge=xen-br0' ]
vif = [ '' ]
# Set root device.
root = "/dev/sdb3 ro"

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>