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

Re: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)

In default config, blkfront is built in the kernel. So there is no xenblk.ko in 
modules.
Do I have to make it as a module?

Thanks.

BTW: This is copied from menuconfig of XenU kernel:
[ ] Privileged Guest (domain 0)                                                 
    
< > Backend driver support                                          
<*> Block-device frontend driver
<*> Network-device frontend driver                                              
                  
[*] Scrub memory before freeing it to Xen                                       
                  
[*] Disable serial port drivers                                                 
                   
<*> Export Xen attributes in sysfs                                              
                   
Xen version compatibility (3.0.2 and later)  --->       

======= 2006-12-13 02:39:04 you wrote:=======

>you can find the module in
>/lib/modules/<kernelversion>/kernel/drivers/xen/blkfront
>for me it's here :
>/lib/modules/2.6.18-1.2798.fc6xen/kernel/drivers/xen/blkfront/xenblk.ko
>
>copy that file to /initrd/lib
>then add insmod /lib/xenblk.ko to the init file
>
>re-create the initrd file from your /initrd directory, and change the VM
>config to use this initrd, instead of the one in /boot.
>
>
>
>
>Zhang Binbin wrote:
>
>>Thanks for your suggestion!
>>I changed initrd for DomU, and lvm problem has been resolved.
>>but kernel still panic when creating DomU:
>>
>>================================================================================================
>># xm create domUconfig
>>Using config file "dom1_config".
>>Started domain Dom1
>>Bootdata ok (command line is  root=/dev/hda1,ro)
>>Linux version 2.6.16.29-xen (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.6 
>>20060404 (Red Hat 3.4.6
>>
>>-3)) #3 SMP Tue Dec 12 15:59:19 CST 2006
>>BIOS-provided physical RAM map:
>> Xen: 0000000000000000 - 0000000010800000 (usable)
>>No mptable found.
>>Built 1 zonelists
>>Kernel command line:  root=/dev/hda1,ro
>>Initializing CPU#0
>>PID hash table entries: 2048 (order: 11, 65536 bytes)
>>Xen reported: 1862.322 MHz processor.
>>Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
>>Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
>>Software IO TLB disabled
>>Memory: 249944k/270336k available (2000k kernel code, 11868k reserved, 883k 
>>data, 172k init)
>>Calibrating delay using timer specific routine.. 3726.62 BogoMIPS 
>>(lpj=18633142)
>>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
>>Brought up 1 CPUs
>>migration_cost=0
>>checking if image is initramfs... it is
>>Freeing initrd memory: 2141k freed
>>DMI not present or invalid.
>>Grant table initialized
>>NET: Registered protocol family 16
>>Brought up 1 CPUs
>>PCI: setting up Xen PCI frontend stub
>>ACPI: Subsystem revision 20060127
>>ACPI: Interpreter disabled.
>>Linux Plug and Play Support v0.97 (c) Adam Belay
>>pnp: PnP ACPI: disabled
>>xen_mem: Initialising balloon driver.
>>SCSI subsystem initialized
>>PCI: System does not support PCI
>>PCI: System does not support PCI
>>IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
>>IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
>>audit: initializing netlink socket (disabled)
>>audit(1165911995.790: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
>>PNP: No PS/2 controller found. Probing ports directly.
>>i8042.c: No controller found.
>>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
>>Registering block device major 3
>>netfront: device eth0 has flipping receive path.
>>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 2
>>IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
>>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)
>>TCP reno registered
>>NET: Registered protocol family 1
>>NET: Registered protocol family 17
>>Red Hat nash version 4.2.1.8 starting
>>Mounted /proc filesystem
>>Mounting sysfs
>>Creating /dev
>>Starting udev
>>Loading sd_mod.ko module
>>Loading libata.ko module
>>Loading ahci.ko module
>>Loading ata_piix.ko module
>>Loading ide-disk.ko module
>>Loading dm-mod.ko module
>>device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@xxxxxxxxxx
>>Loading jbd.ko module
>>Loading ext3.ko module
>>Creating root device
>>Mounting root filesystem
>>mount: error 6 mounting ext3
>>mount: error 2 mounting none
>>Switching to new root
>>switchroot: mount failed: 22
>>umount /initrd/dev failed: 2
>>Kernel panic - not syncing: Attempted to kill init!
>>================================================================================================
>>
>>I decompressed the initrd-xenU, this is init script:
>>================================================================================================
>>#!/bin/nash
>>mount -t proc /proc /proc
>>setquiet
>>echo Mounted /proc filesystem
>>echo Mounting sysfs
>>mount -t sysfs none /sys
>>echo Creating /dev
>>mount -o mode=0755 -t tmpfs none /dev
>>mknod /dev/console c 5 1
>>mknod /dev/null c 1 3
>>mknod /dev/zero c 1 5
>>mkdir /dev/pts
>>mkdir /dev/shm
>>echo Starting udev
>>/sbin/udevstart
>>echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug
>>echo "Loading libata.ko module"
>>insmod /lib/libata.ko
>>echo "Loading ahci.ko module"
>>insmod /lib/ahci.ko
>>echo "Loading ata_piix.ko module"
>>insmod /lib/ata_piix.ko
>>echo "Loading dm-mod.ko module"
>>insmod /lib/dm-mod.ko
>>/sbin/udevstart
>>echo Creating root device
>>mkrootdev /dev/root
>>umount /sys
>>echo Mounting root filesystem
>>mount -o defaults --ro -t ext3 /dev/root /sysroot
>>mount -t tmpfs --bind /dev /sysroot/dev
>>echo Switching to new root
>>switchroot /sysroot
>>umount /initrd/dev
>>================================================================================================
>>And there is no xenbk module in /initrd/lib/.
>>where can I find it please?
>>
>>Thanks.
>>
>>======= 2006-12-12 17:51:41 you wrote:=======
>>
>>  
>>
>>>>I did figure out the howtos of mkinird and the ramdisk concepts, the 
>>>>problem is I do not know what to put/modify inside to make it work.
>>>>This is very frustrating.
>>>>
>>>>      
>>>>
>>>Try adding insmod xenbk to the init script in the initrd. You will have 
>>>to copy that module into the /lib directory of the initrd as well.
>>>I believe the fc6 xen kernel has the back end block driver compiled as a 
>>>module, and because dom0 doesn't need this module, it's not in the dom0 
>>>initrd.
>>>
>>>Greetz,
>>>
>>>Mark
>>>
>>>
>>>_______________________________________________
>>>Xen-users mailing list
>>>Xen-users@xxxxxxxxxxxxxxxxxxx
>>>http://lists.xensource.com/xen-users
>>>
>>>    
>>>
>>
>>= = = = = = = = = = = = = = = = = = = =
>>                      
>>
>>
>>
>>
>>  
>>
>

= = = = = = = = = = = = = = = = = = = =
                        





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users