WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Debian Etch and Xen 3.1 (from Lenny) and XenSource kernels -

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Debian Etch and Xen 3.1 (from Lenny) and XenSource kernels - initial ramdisk problems
From: "Amos Shapira" <amos.shapira@xxxxxxxxx>
Date: Thu, 1 Nov 2007 11:11:19 +1100
Delivery-date: Wed, 31 Oct 2007 17:12:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=OOmCV+35EUGJS1jCABoGTlQATwK2WgUC8f5O7BLi/Ug=; b=pJoDZDti22P+u04SVf5qa8qrFkUQYykWGaQsuRSwAPVLrRwGaAPicI+uR/FI7C3agqFKQ/c5dZktey8u/OC2LKJLscLzIXMkZ8GRn81oereHvDU62/ipOG0alaI1g3b9YiZs44CruRXeSM8PWRDna5B93FSRzF9Q0UYcfZxFx7c=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=IHoVLOPm6H6PR1ZDSR3YofmioQnmNP/asrUbja1oiG/ZjHXAZyMO293ETHKHFYAHndGe6+VuvQsp4XDFL6NjDOwvy5LsghbCjVlPujkK61ka4ZICJdTnNqxDS2pSQifnp6R+ylOJNvE7ROYvDlZLn0BcohjRyc9YeTFV2EsGk3E=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

My hardware is an Intel Xeon 3050 with VT support and 4 Gb RAM.

I previously got Debian Etch and Xen 3.0.3-1 up and running with Windows Server 2003 and CentOS 5 x86_64 DomU's, but in order to support also CentOS 4 and CentOS 3 with 32 bits I got the impression that I need to upgrade to Xen 3.1.

So, trying to follow the process described in http://bderzhavets.blogspot.com/2007/08/xen-3_27.html more or less, I upgraded to Xen 3.1 from Debian Lenny, using kernel and initrd file from XenSource's tar ball (Debian's kernel panics right in the beginning) and I sort of manage to get the CentOS image start to boot but it get stuck on creation of the right device files by the inittial ramdisk.

Here is the current configuration:

kernel = '/boot/vmlinuz-2.6.18-xen'
ramdisk = '/boot/initrd.img-2.6.18-xen'
extra = "ydebug text root=/dev/sda1"
name = "centos50-01"
memory = "512"
disk = [ 'phy:/dev/xen/centos5.0-01-root,ioemu:sda1,w', 'phy:/dev/xen/centos5.0-01-swap,ioemu:sda2,w']
device_model='/usr/lib/xen-3.1-1/bin/qemu-dm'
vif = [ 'type=ioemu', 'bridge=xenbr0', ]
vcpus=1
>>
And here is the output from "xm create" (it's more verbose because of a "ydebug" kernel command line argument):

Using config file "./centos5.0-01.cfg".
Started domain centos50-01
Bootdata ok (command line is ydebug text root=/dev/sda1)
Linux version 2.6.18-xen (shand@endor) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #1 SMP Fri May 18 16:01:42 BST 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 133120
Kernel command line: ydebug text root=/dev/sda1
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 2133.406 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Software IO TLB disabled
Memory: 504576k/532480k available (2014k kernel code, 19044k reserved, 874k data, 172k init)
Calibrating delay using timer specific routine.. 4268.62 BogoMIPS (lpj=21343118)Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 24k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4176k freed
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen < tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1193874811.104:1): 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 (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
blkfront: sda2: barriers enabled
vif vif-0: 2 parsing device/vif/0/mac
netfront: device eth1 has copying receive path.
XENBUS: Timeout connecting to device: device/vif/0 (state 6)
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 172k freed
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/drivers/scsi/scsi_mod.ko
scsi_mod: no version for "struct_module" found: kernel tainted.
SCSI subsystem initialized
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/drivers/scsi/libata.ko
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/drivers/scsi/ata_piix.ko
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/drivers/scsi/sd_mod.ko
register_blkdev: cannot get major 8 for sd
+ mkbdev /dev/sda sda
+ mksymdev /dev/sda /sys/block/sda/dev b
+ devfile=/dev/sda
+ sysfile=/sys/block/sda/dev
+ cb=b
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Waiting 1 seconds for /sys/block/sda/dev to show up
Waiting 1 seconds for /sys/block/sda/dev to show up
+ sleep 1
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Waiting 2 seconds for /sys/block/sda/dev to show up
Waiting 2 seconds for /sys/block/sda/dev to show up
+ sleep 2
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Waiting 4 seconds for /sys/block/sda/dev to show up
Waiting 4 seconds for /sys/block/sda/dev to show up
+ sleep 4
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Waiting 8 seconds for /sys/block/sda/dev to show up
Waiting 8 seconds for /sys/block/sda/dev to show up
+ sleep 8
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Waiting 16 seconds for /sys/block/sda/dev to show up
Waiting 16 seconds for /sys/block/sda/dev to show up
+ sleep 16
+ /bin/cat /sys/block/sda/dev
/bin/cat: /sys/block/sda/dev: No such file or directory
+ devpair=
+ [  =  ]
+ echo Device /sys/block/sda/dev seems to be down.
Device /sys/block/sda/dev seems to be down.
+ [ yes !=  ]
+ echo Debugging opportunity, type ^D to continue.
Debugging opportunity, type ^D to continue.
+ /bin/dash
/bin/dash: can't access tty; job control turned off

At this stage I get a dash prompt at which I manually create /dev/sda, /dev/sda[12] and /dev/sda5 (why does it expect sda5 of all places?)
init fails because /proc/block/sda/dev doesn't exist (there are /dev/block/sda[12]), after I create these devices it still fails on not finding 'xen' volume group
(why does it expect it? It has a raw partition to use):

Device /sys/block/sda/sda5/dev seems to be down.
+ [ yes !=  ]
+ echo Debugging opportunity, type ^D to continue.
Debugging opportunity, type ^D to continue.
+ /bin/dash
/bin/dash: can't access tty; job control turned off
# + maj=
+ min=
+ /bin/mknod /dev/sda5 b
/bin/mknod: missing operand after `b'
Special files require major and minor device numbers.
Try `/bin/mknod --help' for more information.
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/drivers/md/dm- mod.ko
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
+ [ ! -c /dev/mapper/control ]
+ /bin/mkdir /dev/mapper
/bin/mkdir: cannot create directory `/dev/mapper': File exists
+ mkcdev /dev/mapper/control misc/device-mapper
+ mksymdev /dev/mapper/control /sys/class/misc/device-mapper/dev c
+ devfile=/dev/mapper/control
+ sysfile=/sys/class/misc/device-mapper/dev
+ cb=c
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ /bin/cat /sys/class/misc/device-mapper/dev
+ devpair=10:62
+ [ 10:62 =  ]
+ maj=10
+ min=62
+ /bin/mknod /dev/mapper/control c 10 62
+ /sbin/vgchange -a y xen
  Volume group "xen" not found
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/fs/jbd/jbd.ko
+ /sbin/insmod /lib/modules/2.6.18-xen/kernel/fs/ext3/ext3.ko
+ /bin/mount -n -r -t ext3 -o errors=remount-ro,noatime /dev/mapper/xen-root /mnt
mount: special device /dev/mapper/xen-root does not exist
+ switchroot ydebug text
+ [ yes !=  ]
+ echo Debugging opportunity, ^D to continue.
Debugging opportunity, ^D to continue.
+ /bin/dash
/bin/dash: can't access tty; job control turned off
# + echo Switching root ...
Switching root ...
+ /bin/umount -n /sys
+ /bin/umount -n /proc
+ exec /usr/lib/yaird/exec/run_init /mnt /sbin/init ydebug text
/usr/lib/yaird/exec/run_init: current directory on the same filesystem as the root: Success
Kernel panic - not syncing: Attempted to kill init!


Can anyone point me at what am I doing wrong?

Thanks,

--Amos

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Debian Etch and Xen 3.1 (from Lenny) and XenSource kernels - initial ramdisk problems, Amos Shapira <=