[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Kernel image does not exist


  • To: "John D. Ramsdell" <ramsdell@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Moffie, Micha" <micha.moffie@xxxxxx>
  • Date: Tue, 21 Nov 2006 14:58:04 -0000
  • Delivery-date: Tue, 21 Nov 2006 06:58:14 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccNe+EhMhCRV6NtRmqF4u6Q3MBXRQAASa3A
  • Thread-topic: [Xen-devel] Kernel image does not exist

In kernel.c (miniOs)

Move:
 /* ENABLE EVENT DELIVERY. This is disabled at start of day. */
    __sti(); 

After:
  /* Set up events. */
    init_events();


Look at the discussion yesturday:
"Re: [Xen-devel] [PATCH] Mini-OS update of events initialisation"

:)
Micha.

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of John D.
Ramsdell
Sent: 21 November 2006 14:46
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: ramsdell@xxxxxxxxx
Subject: [Xen-devel] Kernel image does not exist

I noticed some interesting improvements to Mini-OS announced on this
list, so I thought I'd try them out.  Before looking at the new
features, I ran into a problem starting a Mini-OS domain.

I've just performed a fresh install of Fedora Core 6, and installed xen,
kernel-xen, and virt-manager, and booted up xen.  Next I pulled the
latest version of xen-unstable.hg, cd'd into extra/mini-os, and
successfully made mini-os.elf.  When I attempt to start the kernel, xm
claimed the kernel did not exist!

[ramsdell@goo luaxen]$ su -
Password: 
[root@goo ~]# cd /home/ramsdell/repo/xen-unstable.hg/extras/mini-os/
[root@goo mini-os]# xm create -c domain_config Using config file
"domain_config".
Error: Kernel image does not exist:
/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/mini-os.elf

But it's easy to see it really is there.

[root@goo mini-os]# file
/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/mini-os.elf
/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/mini-os.elf: ELF
32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked,
not stripped

As near as I can tell, the error message is generated by
../../tools/python/xen/xend/image.py on line 129.

        if not os.path.isfile(self.kernel):
            raise VmError('Kernel image does not exist: %s' %
self.kernel)

So you might think that os.path.isfile is broken.  Not so.

[root@goo mini-os]# python
Python 2.4.4 (#1, Oct 23 2006, 13:58:00) [GCC 4.1.1 20061011 (Red Hat
4.1.1-30)] on linux2 Type "help", "copyright", "credits" or "license"
for more information.
>>> import os.path
>>> print 
>>> (os.path.isfile("/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/
>>> mini-os.elf"))
True
>>> print 
>>> (os.path.isfile("/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/
>>> Makefile"))
True
>>> print 
>>> (os.path.isfile("/home/ramsdell/repo/xen-unstable.hg/extras/mini-os/
>>> missing"))
False
>>> 

I must be doing something silly.  If not, should I send this bug report
to the Xen bug list or the Fedora bug list?

John

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.