All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David F. Barrera" <dfbp@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Problems booting VM using unified Xen kernel (x86_64)
Date: Wed, 03 May 2006 16:16:25 -0500	[thread overview]
Message-ID: <44591DA9.1060002@us.ibm.com> (raw)
In-Reply-To: <44590BAC.3090407@us.ibm.com>

I need to pint out that I am seeing this problem only on an x86_64 
machine. i386 is working as expected.

-- 
Regards,

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

"The wisest men follow their own direction. "
                                                       Euripides




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@ltc.austin.ibm.com 
> <mailto:root@ltc.austin.ibm.com>) (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'.
> builder='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"
>

  reply	other threads:[~2006-05-03 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 19:59 Problems booting VM using unified Xen kernel David F. Barrera
2006-05-03 21:16 ` David F. Barrera [this message]
2006-05-04 15:27   ` Problems booting VM using unified Xen kernel (x86_64) David F. Barrera

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=44591DA9.1060002@us.ibm.com \
    --to=dfbp@us.ibm.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.