Hi all
xm create -c vm1
Using config file "/etc/xen/vm1".
Started domain vm1
Linux version 2.6.12.6-xenU (root@xxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version
3.4.4 20050721 (Red Hat 3.4.4-2)) #1 SMP Mon Dec 19 15:44:16 WST 2005
kernel direct mapping tables upto 10800000 @ 43d000-4c3000
Built 1 zonelists
Kernel command line:
ip=172.30.13.120:1.2.3.4:172.30.13.254:255.255.255.0:vm1:eth0:off
root=/dev/sda1 ro 1
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 3200.112 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 252796k/270336k available (1659k kernel code, 16904k reserved, 561k
data, 132k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 3
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1135100047.227:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
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 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
Registering block device major 8
IP: routing cache hash table of 1024 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
device=eth0, addr=172.30.13.120, mask=255.255.255.0, gw=172.30.13.254,
host=vm1, domain=, nis-domain=(none),
bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Kernel panic - not syncing: No init found. Try passing init= option to
kernel.
(adding 'init=/sbin/init' to extras in the config makes no difference)
Note that no disks are found. This is why I think I need an initrd with the
modules for the SCSI control (LSI MPT Fusion).
Note also that after the panic, a 'xm list' shows vm1 *not* in a crashed
state, is this correct?
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 251 1 r----- 16.8
vm1 6 256 1 r----- 22.9
My config is:
kernel = "/boot/vmlinuz-2.6-xenU"
memory = 256
name = "vm1"
vcpus = 1
disk = [ 'phy:rootvg/xen_vm1,sda1,w' ]
ip = "172.30.13.120"
netmask = "255.255.255.0"
gateway = "172.30.13.254"
hostname = "vm1"
root = "/dev/sda1 ro"
extra = "1"
on_crash = 'destroy'
I had a troll through the linux-2.6.12-xenU tree under xen-3.0.0 src and
found that the kernel config has PCI disabled, why is this?
Thanks
CC
-----Original Message-----
From: Andrew D. Ball [mailto:aball@xxxxxxxxxx]
Sent: Wednesday, 21 December 2005 2:11 AM
To: Colin Coe; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] No init found.
> Not necessarily. domU initrd aren't usually necessary as far as I know,
> but I have made several of them on the same distribution and version as
> you on that type of blade with commands like
>
> cd /lib/modules
> depmod 2.6.12.6-xenU
> mkinitrd --omit-scsi-modules /boot/initrd-2.6.12.6-xenU.img 2.6.12.6-
xenU
>
> Can you post output from 'xm create -c' for your domU as well as the
> domU configuration?
>
> Good luck.
> Andrew
************************************************************************
Bunnings Legal Disclaimer:
1) This email is confidential and may contain legally privileged
information. If you are not the intended recipient, you must not
disclose or use the information contained in it. If you have received
this email in error, please notify us immediately by return email and
delete the document.
2) All emails sent to and sent from Bunnings Group Limited.
are scanned for content. Any material deemed to contain inappropriate
subject matter will be reported to the email administrator of all
parties concerned.
************************************************************************
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home