Jeniffer, Loren
2009-Feb-26 05:39 UTC
[Xen-devel] domU boot problem. (xen 3.3, kernel-2.6.18.8, gcc-4.3.2)
Hi ~ I got an error : "Kernel panic - not syncing: Attempted to kill init" And googling doesn''t help me about this. I built domU kernl using buildconfigs/linux-defconfig_xenU_x86_32. And I copied directories to /dev/hdc8 which is supposed to be domU''s rootfs like : root@hyper1:/boot# mount /dev/hdc8 /mnt/ root@hyper1:/boot# ls /mnt/ bin/ dev/ lib/ root/ sbin/ usr/ var/ root@hyper1:/boot# umount /mnt/ What should I do to get a domU''s console ? Belows are the domain_config and xm create output. root@hyper1:/boot# cat domain_config # -*- mode: python; -*- kernel = "/boot/vmlinuz-2.6.18.8-domU" ramdisk = "/boot/initrd-2.6.18.8-domU.img" memory = 256 name = "linux-domU" disk = [ ''phy:hdc8,sda1,w'' ] root = "/dev/sda1 ro" root@hyper1:/boot# xm create -c domain_config vmid=1 Using config file "./domain_config". Started domain linux-domU Linux version 2.6.18.8 (root@hyper1) (gcc version 4.3.2 ( Ubuntu 4.3.2-1ubuntu12) ) #1 SMP Thu Feb 26 10:50:43 KST 2009 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000) Detected 3391.647 MHz processor. Built 1 zonelists. Total pages: 67584 Kernel command line: root=/dev/hda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 3391.498 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f53fe000, maxmem 2d7fe000 Memory: 255876k/270336k available (2003k kernel code, 6268k reserved, 507k data, 140k in it, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6785.85 BogoMIPS (lpj=33929290) Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K Checking ''hlt'' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed Brought up 1 CPUs migration_cost=0 NET: Registered protocol family 16 Brought up 1 CPUs suspend: event channel 6 xen_mem: Initialising balloon driver. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) 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 xvc0 Event-channel device installed. netfront: Initialising virtual ethernet driver. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode xen-vbd: registered block device major 3 blkfront: hda1: barriers enabled XENBUS: Device with no driver: device/console/0 EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 140k freed Kernel panic - not syncing: Attempted to kill init! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel