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

[Xen-users] error booting Fedora Core 5 root


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Arijit Ganguly" <aganguly@xxxxxxxxx>
  • Date: Tue, 6 Jun 2006 17:04:03 -0400
  • Delivery-date: Tue, 06 Jun 2006 14:04:35 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=mQofs7Ha3wExd2cLF6knaVTLVO+hV0m8zeN5quRtm3fQcplrikyxa5qvZIlmxc14hMOPcwTHFLZNxKeuDy2TeZ4B23SCB4TC4QKBkVhxqyAeI9F6jd2C8zvDNp/lWUAb/QgzXCDzwrPlTQxLfslAPMS05Ny1CSRyNw1Em+QwNWA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

All,

I see the following error when trying to boot a root based on Fedora core.
EXT3 FS on hda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 132k freed
Kernel panic - not syncing: Attempted to kill init!
 [<c01178a0>] panic+0x3c/0x188
 [<c011a79e>] do_exit+0x6a/0x6f4
 [<c0349e34>] vesafb_probe+0x434/0x593
 [<c011aeb1>] sys_exit_group+0x0/0x11
 [<c0104b4d>] syscall_call+0x7/0xb

I am working with the Xen packaged with Fedora, even using the latest unstable tree I see similar errors.
The same kernel boots debian images so well.

Any clues?
Arijit



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

 


Rackspace

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