Hello, i will describe my approach
1) I have downloaded Centos5-64bit xen image from jailtime.org 2) I have created own swap image with 512MB file size 3) I have used same as dom0 kernel 2.6.18-53.1.19.el5xen 4) I have mounted my image file and copied /lib/modules/2.6.18-53.1.19.el5xen 5) I have created custom ramdisk for domU with mkinitrd --with=xennet --preload=xenblk /boot/initrd-2.6.18-53.1.19.el5xen.domU.img `uname -r` (uname -r = 2.6.18-53.1.19.el5xen) 6) Here comes my config file :
kernel = "/boot/vmlinuz-2.6.18-53.1.19.el5xen" ramdisk = "/boot/initrd-2.6.18-53.1.19.el5xen.domU.img"
memory = 512 name = "webdev"
vcpus = 2
vif = [ '' ]
disk = [ 'tap:aio:/home/xen/webdev/webdev_root.img,sda1,w', 'tap:aio:/home/xen/webdev/webdev_swap.img,sda2,w' ]
root = "/dev/sda1 ro"
7) when i will run domU machine using xm create webdev_config.xen -c , it will start booting but it will got freeze , exactly at step after starting crond
Using config file "./webdev_config.xen". Started domain webdev_labs_polarion_com PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default 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 audit: initializing netlink socket (disabled) audit(1211455944.113:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 496E59E526CA1803 - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.18-53.1.19.el5xen (mockbuild@builder10.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed May 7 08:51:05 EDT 2008 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) No mptable found. Built 1 zonelists. Total pages: 133120 Kernel command line: root=/dev/sda1 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2387.998 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: 499712k/532480k available (2358k kernel code, 23900k reserved, 1325k data, 172k init) Calibrating delay using timer specific routine.. 5973.11 BogoMIPS (lpj=11946225) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 2 (SMP-)alternatives turned off Brought up 1 CPUs checking if image is initramfs... it is Grant table initialized NET: Registered protocol family 16 ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 377A0 could not acquire Mutex [2] [20060707] ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread 377A0 could not acquire Mutex [2] [20060707] Initializing CPU#1 migration_cost=2742 Brought up 2 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. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default 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 audit: initializing netlink socket (disabled) audit(1211455944.113:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key 496E59E526CA1803 - User ID: CentOS (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver 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 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0 Write protecting the kernel read-only data: 445k Red Hat nash version 5.1.19.6 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading xenblk.ko module Registering block device major 8 Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading jbd.ko module Loading ext3.ko module Loading raid1.ko module md: raid1 personality registered for level 1 Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module register_blkdev: cannot get major 8 for sd Loading libata.ko module Loading ata_piix.ko module Loading pata_marvell.ko module Loading dm-mod.ko module device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Loading xennet.ko module netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. Waiting for driver initialization. Scanning and configuring dmraid supported devices md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. 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. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys INIT: version 2.86 booting Welcome to CentOS release 5 (Final) Press 'I' to enter interactive startup. Setting clock : Thu May 22 07:32:31 EDT 2008 [ OK ] Starting udev: [ OK ] Setting hostname localhost.localdomain: [ OK ] DM multipath kernel driver not loaded No devices found Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1 /dev/sda1: clean, 19482/128256 files, 110482/256256 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0... failed. [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] Starting sshd: [ OK ] Starting crond: [ OK ]
Thanks for help!
David Hláèik wrote on Thu, 22 May 2008 13:34:17 +0200:
disk = [ 'tap:aio:/home/xen/webdev/webdev_root.img,sda1,w', 'tap:aio:/home/xen/webdev/webdev_swap.img,sda2,w' ]
I suggest using file: instead of tap:aio (I haven't tested this, but it's been said here or elsewhere several times that it is faster than tap:aio) I've been using it all the time with good results.)
root = "/dev/sda1 ro"
You do not need that, comment it out.
- when i will run domU machine using xm create webdev_config.xen -c , it
will start booting but it will got freeze , exactly at step after starting crond
I saw the same when I created a Xen VM for CentOS 4.6. It freezes because there's no tty for the console. I'm not sure if this might be the same. The solution for the tty problem is explained here: http://wiki.centos.org/HowTos/Xen/MoveNative2DomU#head-e05b7d1b0ec9d8ea4815 a6531065760ad1be3dde
Btw: *why* do you want to use a jailtime image if you can just install/kickstart a CentOS 5 VM in no time?
Kai
Kai Schaetzl maillists@conactive.com writes:
David Hláèik wrote on Thu, 22 May 2008 13:34:17 +0200:
disk = [ 'tap:aio:/home/xen/webdev/webdev_root.img,sda1,w', 'tap:aio:/home/xen/webdev/webdev_swap.img,sda2,w' ]
I suggest using file: instead of tap:aio (I haven't tested this, but it's been said here or elsewhere several times that it is faster than tap:aio) I've been using it all the time with good results.)
the tap driver is quite a bit faster than what file: does (file: mounts the file as a loopback device, and passes in the loopback device to the DomU. the tap driver directly manipulates the blocks in the file.)
for more details:
http://www.usenix.org/events/usenix05/tech/general/full_papers/short_papers/...
root = "/dev/sda1 ro"
You do not need that, comment it out.
You need that if you are not using pygrub.
Btw: *why* do you want to use a jailtime image if you can just install/kickstart a CentOS 5 VM in no time?
I agree this is probably the best course of action if you want CentOS 5. virt-install will give you a working system with pygrub (and I think pygrub is keen.)
Luke S Crawford wrote:
Kai Schaetzl maillists@conactive.com writes:
David Hláèik wrote on Thu, 22 May 2008 13:34:17 +0200: Btw: *why* do you want to use a jailtime image if you can just install/kickstart a CentOS 5 VM in no time?
I agree this is probably the best course of action if you want CentOS 5. virt-install will give you a working system with pygrub (and I think pygrub is keen.)
There are a lot of benefits to using jailtime images which are obvious to those who need them. One size doesn't fit all.
Christopher G. Stach II wrote on Thu, 22 May 2008 21:27:13 -0500:
There are a lot of benefits to using jailtime images which are obvious to those who need them.
Which would be? (Remember, we are talking of CentOS 5 images only!)
Kai
On Mon, May 26, 2008 at 11:31 PM, Kai Schaetzl maillists@conactive.com wrote:
Christopher G. Stach II wrote on Thu, 22 May 2008 21:27:13 -0500:
There are a lot of benefits to using jailtime images which are obvious to those who need them.
Which would be? (Remember, we are talking of CentOS 5 images only!)
Additionally, I would advice against using non-official CentOS 5 image. There is no guarantee for their integrity whatsoever. Yes, I know that jailtime has been providing images for a long time, but they are not developed by CentOS, nor QAed by CentOS.
Take care, Daniel