xen-devel
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!
Ian,
One thing about RHEL 4 is that the devices in /dev seem to be created
dynamically, at boot time. When I mount the 'hdc1' partition and go to
the /dev directory, there is nothing in it, as on a SuSE 9.0 or earlier
Red Hat installs. That is why I need an initrd, I suppose, to make or
create those devices.
David
Ian Pratt wrote:
Derrick,
I rebuilt the xenU kernel, with the devfs support disabled, and it makes
no difference. It behaves in the same manner as the pre-built kernel
that's included with the binary pack. I am at a loss. I've been able to
boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a
little experience with this:-)
David, earlier in the boot messages do you see the hdc1 partition
being found when the partition check happens?
You'll need to export the partition 'rw' eventually, but that's
not your current problem.
You might like to try exporting it as 'sda1' or something to see
if that helps. Not sure why it would, but I've heard folklore
along these lines.
Adding some more debugging to the linuxrc nash script might shed
some light on the problem.
Also, what happens if you skip the initrd and try booting
directly off the disk. I doubt there's anything in the initrd you
need.
Ian
Freeing unused kernel memory: 92k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..
David Barrera
Derrik Pates wrote:
David F Barrera wrote:
The distro I am using is RHEL 4 Beta 2 (Red Hat Enterprise Linux
Desktop release 3.90 (Nahant)
/dev/hdc1 / ext2
defaults 1 1
LABEL=SWAP-hdc2 swap swap
defaults 0 0
/dev/hda /media/cdrom auto
pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed
0 0
# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,r' ]
Well, the configuration of the virtual disk looks correct; the swap
might disagree with it, but that shouldn't appear until later in the
boot process. Perhaps it's an interaction with devfs? Do you have
devfs enabled in your xenU (unprivileged domain) kernel? This gave me
fits when I first began using Xen, mostly because it seems that the
xenU prebuilt kernel that's included with the binary pack has devfs
support enabled, and this breaks things. The only other possibility I
can think of is that you need to change the block-device import to
read-write.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, (continued)
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Derrik Pates
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Ian Pratt
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Ian Pratt
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Ian Pratt
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
- Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!,
David F Barrera <=
Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, David F Barrera
RE: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Ian Pratt
RE: [Xen-devel] Kernel panic - not syncing: Attempted to kill init!, Ian Pratt
|
|
|