|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] Re: Kernel panic - not syncing: Attempted to kill init!
Hello Anirban
> Hi,
>
> I followed the topic on this thread. I do not have selinux enabled and
still
> I get the same error. Here is the error message when I try to create a
guest
> domain (2.6.12.6-xenU):
> Am I missing something? Thanks in advance.
>
> -Anirban.
>
> Using config file "xm1".
> Started domain Domain-1
> Linux version 2.6.12.6-xenU (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version
> 3.4.220041017 (Red Hat
> 3.4.2-6.fc3)) #1 SMP Mon Nov 14 23:28:06 PST 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000008000000 (usable)
> 0MB HIGHMEM available.
> 136MB LOWMEM available.
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sdb1 ro 4
> Initializing CPU#0
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Xen reported: 797.961 MHz processor.
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> vmalloc area: c9000000-fb7fe000, maxmem 34000000
> Memory: 126268k/139264k available (1809k kernel code, 4500k reserved,
490k
> data, 136k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
Ok.
> Mount-cache hash table entries: 512
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 256K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> Brought up 1 CPUs
> NET: Registered protocol family 16
> Brought up 1 CPUs
> xen_mem: Initialising balloon driver.
> Grant table initialized
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> Registering block device major 8
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 8Kbytes
> TCP established hash table entries: 8192 (order: 5, 131072 bytes)
> TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: Incomplete network configuration information.
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 136k freed
> kjournald starting. Commit interval 5 seconds
> Enforcing mode requested but no policy loaded. Halting now.
> Kernel panic - not syncing: Attempted to kill init!
I had this problem and fixed it using an initrd in the config file ie
ramdisk = /boot/initrd (or whatever yours is named.) If I remember
correctly I just used the 'stock' initrd that was created on the initial
installation (sles9).
>
> and here is the config file for the guest domain:
>
> kernel = "/boot/vmlinuz-2.6.12-xenU"
> memory = 128
> name = "Domain-1"
> nics=1
> vif = [ 'mac=aa:00:00:00:00:11' ]
> disk = [ 'phy:vg/vmdisk1,sdb1,w' ]
> dhcp="dhcp"
> root = "/dev/sdb1 ro"
> extra = "4"
HTH.
Regards,
John Little
Hendricks Regional Health IS Department
317-718-4752
jslittl@xxxxxxxxxxxxx
http://www.hendrickshospital.org
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] Re: Kernel panic - not syncing: Attempted to kill init!,
John S Little <=
|
|
|
|
|