thr3ads.net - Xen users - [Xen-users] Kernel Panic on trying to boot domU [Mar 2008]

If this information is useful, please help other people find it:
Share via:

Girish V

2008-Mar-20 02:43 UTC

[Xen-users] Kernel Panic on trying to boot domU

Hello,
I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system).

After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I
modified the conf.grub as shown below. With this, I was able to boot xen.

---------------------------------------------------------------------------------------------------------------

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,0)
#          kernel /boot/vmlinuz-version ro root=/dev/sda1
#          initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Xen 3.2 (2.6.18.8-xen)
      root (hd0,0)
      kernel /boot/xen.gz dom0_mem=1024M console=vga
      module /boot/vmlinuz-2.6.18.8-xen ro root=LABEL=/1 console=tty0
      module /boot/initrd-3.2-xen.img
title Fedora Core (2.6.18-1.2798.fc6)
      root (hd0,0)
      kernel /boot/vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/1 rhgb quiet
      initrd /boot/initrd-2.6.18-1.2798.fc6.img
---------------------------------------------------------------------------------------------------------------



Then, I created a domU image as in the uer manual for v3.0.

1) I created a blank discimage fc6_domudisk and monted in in /mnt
2) I copied /{root, dev,var,etc,usr,bin,sbin,lib} to /mnt
3) I makde the {home, proc, sys, tmp} directories inside /mnt
4) I modified the mnt/etc/fstab as follows
----------------------------------------------------------------------------------------------------------------

/dev/sda1                /                       ext3    defaults        1 1
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
---------------------------------------------------------------------------------------------------------------

5) With this I tried to bring up the domU using the following configuration
file. From what I understand, I can use the dom0 kernel itself for domU.

----------------------------------------------------------------------------------------------------------------

kernel = "/boot/vmlinuz-2.6.18.8-xen"
memory = 256
name = "fc6"
vif = [ ''bridge=xenbr0'' ]
disk = [ ''file:/second/fc6_domudisk,sda1,w'' ]
root = "/dev/sda1 ro"
----------------------------------------------------------------------------------------------------------------

But the boot fails with a kernel panic. The boot messages are listed below.

-----------------------------------------------------------------------------------------------------------------

Using config file "./file-config-rh9_diskimg".
Started domain fc6_new
                      Linux version 2.6.18.8-xen (root@localhost.localdomain)
(gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)) #1 SMP Mon Mar 17 20:26:25
EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
Detected 4232.073 MHz processor.
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/sda1 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: 3200.118 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-f51fe000, maxmem 2d7fe000
Memory: 255340k/270336k available (2056k kernel code, 6800k reserved, 716k
data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy.
Probably due to long platform interrupts. Consider using "lpj=" boot
option.
Security Framework v1.0.0 initialized
Capability LSM initialized
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
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: 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
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1423925502.304:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: Unable to grab DMA2 for the floppy driver
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
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
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as
ext2
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 196k freed
Kernel panic - not syncing: Attempted to kill init!
-----------------------------------------------------------------------------------------------------------------

It would be great if someone could help me out.

Thanks,
Girish


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

Igor Chubin

2008-Mar-22 18:09 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:> Hello,
Hello Girish, 

...


Try to specify ramdisk here:

(check path in my example)
> 
>
----------------------------------------------------------------------------------------------------------------
> 
> kernel = "/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd.img-2.6.18.8-xen"> memory = 256
> name = "fc6"
> vif = [ ''bridge=xenbr0'' ]
> disk = [ ''file:/second/fc6_domudisk,sda1,w'' ]
> root = "/dev/sda1 ro"
>
----------------------------------------------------------------------------------------------------------------
> -- 
WBR, i.m.chubin


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

Girish V

2008-Mar-23 04:30 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

Hi Igor.
Thanks for the suggestion. I did try using a ramdisk - and the bootup of the
domU goes a little bit furter, but init still crashes with the same message
as before.
Any idea what I should do further?
Thanks,
Girish

On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin <igor@chub.in> wrote:
> On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > Hello,
>
> Hello Girish,
>
> ...
>
>
> Try to specify ramdisk here:
>
> (check path in my example)
>
> >
> >
>
----------------------------------------------------------------------------------------------------------------
> >
> > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > memory = 256
> > name = "fc6"
> > vif = [ ''bridge=xenbr0'' ]
> > disk = [ ''file:/second/fc6_domudisk,sda1,w'' ]
> > root = "/dev/sda1 ro"
> >
>
----------------------------------------------------------------------------------------------------------------
> >
> --
> WBR, i.m.chubin
>
>

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

Igor Chubin

2008-Mar-23 10:17 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:> Hi Igor.
> Thanks for the suggestion. I did try using a ramdisk - and the bootup of
the
> domU goes a little bit furter, but init still crashes with the same message
> as before.
> Any idea what I should do further?

What the last printed lines now?
> Thanks,
> Girish
> 
> On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin <igor@chub.in> wrote:
> 
> > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > > Hello,
> >
> > Hello Girish,
> >
> > ...
> >
> >
> > Try to specify ramdisk here:
> >
> > (check path in my example)
> >
> > >
> > >
> >
----------------------------------------------------------------------------------------------------------------
> > >
> > > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > memory = 256
> > > name = "fc6"
> > > vif = [ ''bridge=xenbr0'' ]
> > > disk = [ ''file:/second/fc6_domudisk,sda1,w'' ]
> > > root = "/dev/sda1 ro"
> > >
> >
----------------------------------------------------------------------------------------------------------------
> > >
> > --
> > WBR, i.m.chubin
> >
> >
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
WBR, i.m.chubin


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

Girish V

2008-Mar-25 13:35 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

The bootup message after using the ramdisk is shown below.
Thanks
Girish
--------------------------------------------------------------------------------------------------------

[root@localhost second]# xm create -c file-config-rh9_diskimg
Using config file "./file-config-rh9_diskimg".
Started domain fc6_new
                      Linux version 2.6.18.8-xen (root@localhost.localdomain)
(gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)) #2 SMP Thu Mar 20 17:40:00
EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
Detected 3202.737 MHz processor.
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
Memory: 251788k/270336k available (2056k kernel code, 10352k reserved, 712k
data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6447.39 BogoMIPS
(lpj=32236972)
Security Framework v1.0.0 initialized
Capability LSM initialized
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
checking if image is initramfs... it is
Freeing initrd memory: 3552k 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: 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
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1206452738.073:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: Unable to grab DMA2 for the floppy driver
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
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
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Freeing unused kernel memory: 196k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!


--------------------------------------------------------------------------------------------------------

On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@chub.in> wrote:
> On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > Hi Igor.
> > Thanks for the suggestion. I did try using a ramdisk - and the bootup
of
> the
> > domU goes a little bit furter, but init still crashes with the same
> message
> > as before.
> > Any idea what I should do further?
>
>
> What the last printed lines now?
>
> > Thanks,
> > Girish
> >
> > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin <igor@chub.in>
wrote:
> >
> > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > > > Hello,
> > >
> > > Hello Girish,
> > >
> > > ...
> > >
> > >
> > > Try to specify ramdisk here:
> > >
> > > (check path in my example)
> > >
> > > >
> > > >
> > >
>
----------------------------------------------------------------------------------------------------------------
> > > >
> > > > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > > memory = 256
> > > > name = "fc6"
> > > > vif = [ ''bridge=xenbr0'' ]
> > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > root = "/dev/sda1 ro"
> > > >
> > >
>
----------------------------------------------------------------------------------------------------------------
> > > >
> > > --
> > > WBR, i.m.chubin
> > >
> > >
>
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
> --
> WBR, i.m.chubin
>
>

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

weiming

2008-Mar-25 14:29 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

seems that the driver for your hard driver controllers was not included in
the image file.

On Tue, Mar 25, 2008 at 9:35 AM, Girish V <girish.xen@gmail.com> wrote:
> The bootup message after using the ramdisk is shown below.
> Thanks
> Girish
>
>
--------------------------------------------------------------------------------------------------------
>
> [root@localhost second]# xm create -c file-config-rh9_diskimg
> Using config file "./file-config-rh9_diskimg".
> Started domain fc6_new
>                       Linux version 2.6.18.8-xen (
> root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-13))
> #2 SMP Thu Mar 20 17:40:00 EDT 2008
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000010800000 (usable)
> 0MB HIGHMEM available.
> 264MB LOWMEM available.
> ACPI in unprivileged domain disabled
> Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
> Detected 3202.737 MHz processor.
> Built 1 zonelists.  Total pages: 67584
> Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> Memory: 251788k/270336k available (2056k kernel code, 10352k reserved,
> 712k data, 196k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok.
> Calibrating delay using timer specific routine.. 6447.39 BogoMIPS
> (lpj=32236972)
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> 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
> checking if image is initramfs... it is
> Freeing initrd memory: 3552k 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: 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
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1206452738.073:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> (usb?)
> Failed to obtain physical IRQ 6
> floppy0: Unable to grab DMA2 for the floppy driver
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> Xen virtual console successfully installed as xvc0
> 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
> Using IPI No-Shortcut mode
> xen-vbd: registered block device major 8
> blkfront: sda1: barriers enabled
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 196k freed
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> USB Universal Host Controller Interface driver v3.0
> SCSI subsystem initialized
> register_blkdev: cannot get major 8 for sd
> Fusion MPT base driver 3.04.01
> Copyright (c) 1999-2005 LSI Logic Corporation
> Fusion MPT SPI Host driver 3.04.01
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Kernel panic - not syncing: Attempted to kill init!
>
>
>
>
--------------------------------------------------------------------------------------------------------
>
> On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@chub.in> wrote:
>
> > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > > Hi Igor.
> > > Thanks for the suggestion. I did try using a ramdisk - and the
bootup
> > of the
> > > domU goes a little bit furter, but init still crashes with the
same
> > message
> > > as before.
> > > Any idea what I should do further?
> >
> >
> > What the last printed lines now?
> >
> > > Thanks,
> > > Girish
> > >
> > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin <igor@chub.in>
wrote:
> > >
> > > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > > > > Hello,
> > > >
> > > > Hello Girish,
> > > >
> > > > ...
> > > >
> > > >
> > > > Try to specify ramdisk here:
> > > >
> > > > (check path in my example)
> > > >
> > > > >
> > > > >
> > > >
> >
----------------------------------------------------------------------------------------------------------------
> > > > >
> > > > > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > > > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > > > memory = 256
> > > > > name = "fc6"
> > > > > vif = [ ''bridge=xenbr0'' ]
> > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > root = "/dev/sda1 ro"
> > > > >
> > > >
> >
----------------------------------------------------------------------------------------------------------------
> > > > >
> > > > --
> > > > WBR, i.m.chubin
> > > >
> > > >
> >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
> > --
> > WBR, i.m.chubin
> >
> >
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

weiming

2008-Mar-25 16:21 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

sorry. I missed the "DomU" in the subject. :D

On Tue, Mar 25, 2008 at 12:22 PM, Igor Chubin <igor@chub.in> wrote:
> On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:
> > seems that the driver for your hard driver controllers was not
included
> in
> > the image file.
>
>
> Real hard disk controller is not (and should not be!)
> visible in a guest domain.
> Guest domain uses PV-interfaces to the domain 0
> to access devices.
>
> Try to edit your config
> and change sda to hda:
>
> ===================================================> kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> memory = 256
> name = "fc6"
> vif = [ ''bridge=xenbr0'' ]
> disk = [ ''file:/second/fc6_domudisk,hda1,w'' ]
> root = "/dev/hda1 ro"
> ===================================================>
>
>
> >
> > On Tue, Mar 25, 2008 at 9:35 AM, Girish V <girish.xen@gmail.com>
wrote:
> >
> > > The bootup message after using the ramdisk is shown below.
> > > Thanks
> > > Girish
> > >
> > >
>
--------------------------------------------------------------------------------------------------------
> > >
> > > [root@localhost second]# xm create -c file-config-rh9_diskimg
> > > Using config file "./file-config-rh9_diskimg".
> > > Started domain fc6_new
> > >                       Linux version 2.6.18.8-xen (
> > > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat
> 4.1.2-13))
> > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > BIOS-provided physical RAM map:
> > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > 0MB HIGHMEM available.
> > > 264MB LOWMEM available.
> > > ACPI in unprivileged domain disabled
> > > Allocating PCI resources starting at 20000000 (gap:
10800000:ef800000)
> > > Detected 3202.737 MHz processor.
> > > Built 1 zonelists.  Total pages: 67584
> > > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > > Memory: 251788k/270336k available (2056k kernel code, 10352k
reserved,
> > > 712k data, 196k init, 0k highmem)
> > > Checking if this processor honours the WP bit even in supervisor
> mode...
> > > Ok.
> > > Calibrating delay using timer specific routine.. 6447.39 BogoMIPS
> > > (lpj=32236972)
> > > Security Framework v1.0.0 initialized
> > > Capability LSM initialized
> > > 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
> > > checking if image is initramfs... it is
> > > Freeing initrd memory: 3552k 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: 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
> > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > audit: initializing netlink socket (disabled)
> > > audit(1206452738.073:1): initialized
> > > VFS: Disk quotas dquot_6.5.1
> > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > Initializing Cryptographic API
> > > io scheduler noop registered
> > > io scheduler anticipatory registered
> > > io scheduler deadline registered
> > > io scheduler cfq registered (default)
> > > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown
type 15
> > > (usb?)
> > > Failed to obtain physical IRQ 6
> > > floppy0: Unable to grab DMA2 for the floppy driver
> > > floppy0: no floppy controllers found
> > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
blocksize
> > > loop: loaded (max 8 devices)
> > > Xen virtual console successfully installed as xvc0
> > > 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
> > > Using IPI No-Shortcut mode
> > > xen-vbd: registered block device major 8
> > > blkfront: sda1: barriers enabled
> > > XENBUS: Device with no driver: device/console/0
> > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > > EDD information not available.
> > > Freeing unused kernel memory: 196k freed
> > > usbcore: registered new driver usbfs
> > > usbcore: registered new driver hub
> > > USB Universal Host Controller Interface driver v3.0
> > > SCSI subsystem initialized
> > > register_blkdev: cannot get major 8 for sd
> > > Fusion MPT base driver 3.04.01
> > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > Fusion MPT SPI Host driver 3.04.01
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > Kernel panic - not syncing: Attempted to kill init!
> > >
> > >
> > >
> > >
>
--------------------------------------------------------------------------------------------------------
> > >
> > > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@chub.in>
wrote:
> > >
> > > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > > > > Hi Igor.
> > > > > Thanks for the suggestion. I did try using a ramdisk -
and the
> bootup
> > > > of the
> > > > > domU goes a little bit furter, but init still crashes
with the
> same
> > > > message
> > > > > as before.
> > > > > Any idea what I should do further?
> > > >
> > > >
> > > > What the last printed lines now?
> > > >
> > > > > Thanks,
> > > > > Girish
> > > > >
> > > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin
<igor@chub.in> wrote:
> > > > >
> > > > > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V
wrote:
> > > > > > > Hello,
> > > > > >
> > > > > > Hello Girish,
> > > > > >
> > > > > > ...
> > > > > >
> > > > > >
> > > > > > Try to specify ramdisk here:
> > > > > >
> > > > > > (check path in my example)
> > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > >
> > > > > > > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > > > > > ramdisk =
"/boot/initrd.img-2.6.18.8-xen"
> > > > > > > memory = 256
> > > > > > > name = "fc6"
> > > > > > > vif = [ ''bridge=xenbr0'' ]
> > > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > > root = "/dev/sda1 ro"
> > > > > > >
> > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > >
> > > > > > --
> > > > > > WBR, i.m.chubin
> > > > > >
> > > > > >
> > > >
> > > > > _______________________________________________
> > > > > Xen-users mailing list
> > > > > Xen-users@lists.xensource.com
> > > > > http://lists.xensource.com/xen-users
> > > >
> > > > --
> > > > WBR, i.m.chubin
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > >
>
> --
> WBR, i.m.chubin
>
>

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

Igor Chubin

2008-Mar-25 16:22 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:> seems that the driver for your hard driver controllers was not included in
> the image file.

Real hard disk controller is not (and should not be!) 
visible in a guest domain.
Guest domain uses PV-interfaces to the domain 0 
to access devices.

Try to edit your config
and change sda to hda:

===================================================kernel =
"/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd.img-2.6.18.8-xen"
memory = 256
name = "fc6"
vif = [ ''bridge=xenbr0'' ]
disk = [ ''file:/second/fc6_domudisk,hda1,w'' ]
root = "/dev/hda1 ro"
===================================================

> 
> On Tue, Mar 25, 2008 at 9:35 AM, Girish V <girish.xen@gmail.com>
wrote:
> 
> > The bootup message after using the ramdisk is shown below.
> > Thanks
> > Girish
> >
> >
--------------------------------------------------------------------------------------------------------
> >
> > [root@localhost second]# xm create -c file-config-rh9_diskimg
> > Using config file "./file-config-rh9_diskimg".
> > Started domain fc6_new
> >                       Linux version 2.6.18.8-xen (
> > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat
4.1.2-13))
> > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > BIOS-provided physical RAM map:
> >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > 0MB HIGHMEM available.
> > 264MB LOWMEM available.
> > ACPI in unprivileged domain disabled
> > Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
> > Detected 3202.737 MHz processor.
> > Built 1 zonelists.  Total pages: 67584
> > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > Memory: 251788k/270336k available (2056k kernel code, 10352k reserved,
> > 712k data, 196k init, 0k highmem)
> > Checking if this processor honours the WP bit even in supervisor
mode...
> > Ok.
> > Calibrating delay using timer specific routine.. 6447.39 BogoMIPS
> > (lpj=32236972)
> > Security Framework v1.0.0 initialized
> > Capability LSM initialized
> > 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
> > checking if image is initramfs... it is
> > Freeing initrd memory: 3552k 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: 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
> > IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> > audit: initializing netlink socket (disabled)
> > audit(1206452738.073:1): initialized
> > VFS: Disk quotas dquot_6.5.1
> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > Initializing Cryptographic API
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> > (usb?)
> > Failed to obtain physical IRQ 6
> > floppy0: Unable to grab DMA2 for the floppy driver
> > floppy0: no floppy controllers found
> > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> > loop: loaded (max 8 devices)
> > Xen virtual console successfully installed as xvc0
> > 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
> > Using IPI No-Shortcut mode
> > xen-vbd: registered block device major 8
> > blkfront: sda1: barriers enabled
> > XENBUS: Device with no driver: device/console/0
> > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > EDD information not available.
> > Freeing unused kernel memory: 196k freed
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > USB Universal Host Controller Interface driver v3.0
> > SCSI subsystem initialized
> > register_blkdev: cannot get major 8 for sd
> > Fusion MPT base driver 3.04.01
> > Copyright (c) 1999-2005 LSI Logic Corporation
> > Fusion MPT SPI Host driver 3.04.01
> > kjournald starting.  Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with ordered data mode.
> > Kernel panic - not syncing: Attempted to kill init!
> >
> >
> >
> >
--------------------------------------------------------------------------------------------------------
> >
> > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@chub.in>
wrote:
> >
> > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > > > Hi Igor.
> > > > Thanks for the suggestion. I did try using a ramdisk - and
the bootup
> > > of the
> > > > domU goes a little bit furter, but init still crashes with
the same
> > > message
> > > > as before.
> > > > Any idea what I should do further?
> > >
> > >
> > > What the last printed lines now?
> > >
> > > > Thanks,
> > > > Girish
> > > >
> > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin
<igor@chub.in> wrote:
> > > >
> > > > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > > > > > Hello,
> > > > >
> > > > > Hello Girish,
> > > > >
> > > > > ...
> > > > >
> > > > >
> > > > > Try to specify ramdisk here:
> > > > >
> > > > > (check path in my example)
> > > > >
> > > > > >
> > > > > >
> > > > >
> > >
----------------------------------------------------------------------------------------------------------------
> > > > > >
> > > > > > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > > > > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > > > > memory = 256
> > > > > > name = "fc6"
> > > > > > vif = [ ''bridge=xenbr0'' ]
> > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > root = "/dev/sda1 ro"
> > > > > >
> > > > >
> > >
----------------------------------------------------------------------------------------------------------------
> > > > > >
> > > > > --
> > > > > WBR, i.m.chubin
> > > > >
> > > > >
> > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@lists.xensource.com
> > > > http://lists.xensource.com/xen-users
> > >
> > > --
> > > WBR, i.m.chubin
> > >
> > >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
-- 
WBR, i.m.chubin


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

Girish V

2008-Mar-25 17:12 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

Hello Igor and Weiming,
Thnaks for the replies.

I tried changing "sda" to "hda" in the config file, but the
kernel still
panics. The output is listed below. From a quick scan, it seems to be no
different from when  I use sda (except for vbd 3 being used instead of vbd8)

--------------------------------------------------------------------------------------------------

[root@localhost second]# xm create -c file-config-rh9_diskimg
Using config file "./file-config-rh9_diskimg".
Started domain fc6_new
                      Linux version 2.6.18.8-xen (root@localhost.localdomain)
(gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)) #2 SMP Thu Mar 20 17:40:00
EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
Detected 6396.277 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: 3200.122 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-f51fe000, maxmem 2d7fe000
Memory: 251788k/270336k available (2056k kernel code, 10352k reserved, 712k
data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
calibrate_delay_direct() failed to get a good estimate for loops_per_jiffy.
Probably due to long platform interrupts. Consider using "lpj=" boot
option.
Security Framework v1.0.0 initialized
Capability LSM initialized
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
checking if image is initramfs... it is
Freeing initrd memory: 3552k 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: 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
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1206465527.468:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
(usb?)
Failed to obtain physical IRQ 6
floppy0: Unable to grab DMA2 for the floppy driver
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
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
Using IPI No-Shortcut mode
xen-vbd: registered block device major 3
blkfront: hda1: barriers enabled
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Freeing unused kernel memory: 196k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!

------------------------------------------------------------------------------------------------------------------------
Thanks,
Girish


On Tue, Mar 25, 2008 at 12:22 PM, Igor Chubin <igor@chub.in> wrote:
> On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:
> > seems that the driver for your hard driver controllers was not
included
> in
> > the image file.
>
>
> Real hard disk controller is not (and should not be!)
> visible in a guest domain.
> Guest domain uses PV-interfaces to the domain 0
> to access devices.
>
> Try to edit your config
> and change sda to hda:
>
> ===================================================> kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> memory = 256
> name = "fc6"
> vif = [ ''bridge=xenbr0'' ]
> disk = [ ''file:/second/fc6_domudisk,hda1,w'' ]
> root = "/dev/hda1 ro"
> ===================================================>
>
>
> >
> > On Tue, Mar 25, 2008 at 9:35 AM, Girish V <girish.xen@gmail.com>
wrote:
> >
> > > The bootup message after using the ramdisk is shown below.
> > > Thanks
> > > Girish
> > >
> > >
>
--------------------------------------------------------------------------------------------------------
> > >
> > > [root@localhost second]# xm create -c file-config-rh9_diskimg
> > > Using config file "./file-config-rh9_diskimg".
> > > Started domain fc6_new
> > >                       Linux version 2.6.18.8-xen (
> > > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat
> 4.1.2-13))
> > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > BIOS-provided physical RAM map:
> > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > 0MB HIGHMEM available.
> > > 264MB LOWMEM available.
> > > ACPI in unprivileged domain disabled
> > > Allocating PCI resources starting at 20000000 (gap:
10800000:ef800000)
> > > Detected 3202.737 MHz processor.
> > > Built 1 zonelists.  Total pages: 67584
> > > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > > Memory: 251788k/270336k available (2056k kernel code, 10352k
reserved,
> > > 712k data, 196k init, 0k highmem)
> > > Checking if this processor honours the WP bit even in supervisor
> mode...
> > > Ok.
> > > Calibrating delay using timer specific routine.. 6447.39 BogoMIPS
> > > (lpj=32236972)
> > > Security Framework v1.0.0 initialized
> > > Capability LSM initialized
> > > 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
> > > checking if image is initramfs... it is
> > > Freeing initrd memory: 3552k 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: 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
> > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > audit: initializing netlink socket (disabled)
> > > audit(1206452738.073:1): initialized
> > > VFS: Disk quotas dquot_6.5.1
> > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > Initializing Cryptographic API
> > > io scheduler noop registered
> > > io scheduler anticipatory registered
> > > io scheduler deadline registered
> > > io scheduler cfq registered (default)
> > > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown
type 15
> > > (usb?)
> > > Failed to obtain physical IRQ 6
> > > floppy0: Unable to grab DMA2 for the floppy driver
> > > floppy0: no floppy controllers found
> > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
blocksize
> > > loop: loaded (max 8 devices)
> > > Xen virtual console successfully installed as xvc0
> > > 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
> > > Using IPI No-Shortcut mode
> > > xen-vbd: registered block device major 8
> > > blkfront: sda1: barriers enabled
> > > XENBUS: Device with no driver: device/console/0
> > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > > EDD information not available.
> > > Freeing unused kernel memory: 196k freed
> > > usbcore: registered new driver usbfs
> > > usbcore: registered new driver hub
> > > USB Universal Host Controller Interface driver v3.0
> > > SCSI subsystem initialized
> > > register_blkdev: cannot get major 8 for sd
> > > Fusion MPT base driver 3.04.01
> > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > Fusion MPT SPI Host driver 3.04.01
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > Kernel panic - not syncing: Attempted to kill init!
> > >
> > >
> > >
> > >
>
--------------------------------------------------------------------------------------------------------
> > >
> > > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@chub.in>
wrote:
> > >
> > > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > > > > Hi Igor.
> > > > > Thanks for the suggestion. I did try using a ramdisk -
and the
> bootup
> > > > of the
> > > > > domU goes a little bit furter, but init still crashes
with the
> same
> > > > message
> > > > > as before.
> > > > > Any idea what I should do further?
> > > >
> > > >
> > > > What the last printed lines now?
> > > >
> > > > > Thanks,
> > > > > Girish
> > > > >
> > > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin
<igor@chub.in> wrote:
> > > > >
> > > > > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V
wrote:
> > > > > > > Hello,
> > > > > >
> > > > > > Hello Girish,
> > > > > >
> > > > > > ...
> > > > > >
> > > > > >
> > > > > > Try to specify ramdisk here:
> > > > > >
> > > > > > (check path in my example)
> > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > >
> > > > > > > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > > > > > ramdisk =
"/boot/initrd.img-2.6.18.8-xen"
> > > > > > > memory = 256
> > > > > > > name = "fc6"
> > > > > > > vif = [ ''bridge=xenbr0'' ]
> > > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > > root = "/dev/sda1 ro"
> > > > > > >
> > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > >
> > > > > > --
> > > > > > WBR, i.m.chubin
> > > > > >
> > > > > >
> > > >
> > > > > _______________________________________________
> > > > > Xen-users mailing list
> > > > > Xen-users@lists.xensource.com
> > > > > http://lists.xensource.com/xen-users
> > > >
> > > > --
> > > > WBR, i.m.chubin
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > >
>
> --
> WBR, i.m.chubin
>
>

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

weiming

2008-Mar-25 17:42 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

Did you check the process of creating the virtual partition?

On Tue, Mar 25, 2008 at 1:12 PM, Girish V <girish.xen@gmail.com> wrote:
> Hello Igor and Weiming,
> Thnaks for the replies.
>
> I tried changing "sda" to "hda" in the config file, but
the kernel still
> panics. The output is listed below. From a quick scan, it seems to be no
> different from when  I use sda (except for vbd 3 being used instead of
vbd8)
>
>
>
--------------------------------------------------------------------------------------------------
>
> [root@localhost second]# xm create -c file-config-rh9_diskimg
> Using config file "./file-config-rh9_diskimg".
> Started domain fc6_new
>                       Linux version 2.6.18.8-xen (
> root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-13))
> #2 SMP Thu Mar 20 17:40:00 EDT 2008
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000010800000 (usable)
> 0MB HIGHMEM available.
> 264MB LOWMEM available.
> ACPI in unprivileged domain disabled
> Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
> Detected 6396.277 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: 3200.122 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-f51fe000, maxmem 2d7fe000
> Memory: 251788k/270336k available (2056k kernel code, 10352k reserved,
> 712k data, 196k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok.
> calibrate_delay_direct() failed to get a good estimate for
> loops_per_jiffy.
> Probably due to long platform interrupts. Consider using "lpj="
boot
> option.
>
> Security Framework v1.0.0 initialized
> Capability LSM initialized
> 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
> checking if image is initramfs... it is
> Freeing initrd memory: 3552k 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: 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
> IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> audit: initializing netlink socket (disabled)
> audit(1206465527.468:1): initialized
>
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered (default)
> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> (usb?)
> Failed to obtain physical IRQ 6
> floppy0: Unable to grab DMA2 for the floppy driver
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> loop: loaded (max 8 devices)
> Xen virtual console successfully installed as xvc0
> 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
> Using IPI No-Shortcut mode
> xen-vbd: registered block device major 3
> blkfront: hda1: barriers enabled
> XENBUS: Device with no driver: device/console/0
> BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> EDD information not available.
> Freeing unused kernel memory: 196k freed
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> USB Universal Host Controller Interface driver v3.0
> SCSI subsystem initialized
> Fusion MPT base driver 3.04.01
> Copyright (c) 1999-2005 LSI Logic Corporation
> Fusion MPT SPI Host driver 3.04.01
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Kernel panic - not syncing: Attempted to kill init!
>
>
>
------------------------------------------------------------------------------------------------------------------------
> Thanks,
> Girish
>
>
>
> On Tue, Mar 25, 2008 at 12:22 PM, Igor Chubin <igor@chub.in> wrote:
>
> > On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:
> > > seems that the driver for your hard driver controllers was not
> > included in
> > > the image file.
> >
> >
> > Real hard disk controller is not (and should not be!)
> > visible in a guest domain.
> > Guest domain uses PV-interfaces to the domain 0
> > to access devices.
> >
> > Try to edit your config
> > and change sda to hda:
> >
> > ===================================================> > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > memory = 256
> > name = "fc6"
> > vif = [ ''bridge=xenbr0'' ]
> > disk = [ ''file:/second/fc6_domudisk,hda1,w'' ]
> > root = "/dev/hda1 ro"
> > ===================================================> >
> >
> >
> > >
> > > On Tue, Mar 25, 2008 at 9:35 AM, Girish V
<girish.xen@gmail.com>
> > wrote:
> > >
> > > > The bootup message after using the ramdisk is shown below.
> > > > Thanks
> > > > Girish
> > > >
> > > >
> >
--------------------------------------------------------------------------------------------------------
> > > >
> > > > [root@localhost second]# xm create -c
file-config-rh9_diskimg
> > > > Using config file "./file-config-rh9_diskimg".
> > > > Started domain fc6_new
> > > >                       Linux version 2.6.18.8-xen (
> > > > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red
Hat
> > 4.1.2-13))
> > > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > > BIOS-provided physical RAM map:
> > > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > > 0MB HIGHMEM available.
> > > > 264MB LOWMEM available.
> > > > ACPI in unprivileged domain disabled
> > > > Allocating PCI resources starting at 20000000 (gap:
> > 10800000:ef800000)
> > > > Detected 3202.737 MHz processor.
> > > > Built 1 zonelists.  Total pages: 67584
> > > > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > > > Memory: 251788k/270336k available (2056k kernel code, 10352k
> > reserved,
> > > > 712k data, 196k init, 0k highmem)
> > > > Checking if this processor honours the WP bit even in
supervisor
> > mode...
> > > > Ok.
> > > > Calibrating delay using timer specific routine.. 6447.39
BogoMIPS
> > > > (lpj=32236972)
> > > > Security Framework v1.0.0 initialized
> > > > Capability LSM initialized
> > > > 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
> > > > checking if image is initramfs... it is
> > > > Freeing initrd memory: 3552k 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: 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
> > > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > > audit: initializing netlink socket (disabled)
> > > > audit(1206452738.073:1): initialized
> > > > VFS: Disk quotas dquot_6.5.1
> > > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > > Initializing Cryptographic API
> > > > io scheduler noop registered
> > > > io scheduler anticipatory registered
> > > > io scheduler deadline registered
> > > > io scheduler cfq registered (default)
> > > > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is
unknown type
> > 15
> > > > (usb?)
> > > > Failed to obtain physical IRQ 6
> > > > floppy0: Unable to grab DMA2 for the floppy driver
> > > > floppy0: no floppy controllers found
> > > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
> > blocksize
> > > > loop: loaded (max 8 devices)
> > > > Xen virtual console successfully installed as xvc0
> > > > 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
> > > > Using IPI No-Shortcut mode
> > > > xen-vbd: registered block device major 8
> > > > blkfront: sda1: barriers enabled
> > > > XENBUS: Device with no driver: device/console/0
> > > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > > > EDD information not available.
> > > > Freeing unused kernel memory: 196k freed
> > > > usbcore: registered new driver usbfs
> > > > usbcore: registered new driver hub
> > > > USB Universal Host Controller Interface driver v3.0
> > > > SCSI subsystem initialized
> > > > register_blkdev: cannot get major 8 for sd
> > > > Fusion MPT base driver 3.04.01
> > > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > > Fusion MPT SPI Host driver 3.04.01
> > > > kjournald starting.  Commit interval 5 seconds
> > > > EXT3-fs: mounted filesystem with ordered data mode.
> > > > Kernel panic - not syncing: Attempted to kill init!
> > > >
> > > >
> > > >
> > > >
> >
--------------------------------------------------------------------------------------------------------
> > > >
> > > > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin
<igor@chub.in> wrote:
> > > >
> > > > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> > > > > > Hi Igor.
> > > > > > Thanks for the suggestion. I did try using a
ramdisk - and the
> > bootup
> > > > > of the
> > > > > > domU goes a little bit furter, but init still
crashes with the
> > same
> > > > > message
> > > > > > as before.
> > > > > > Any idea what I should do further?
> > > > >
> > > > >
> > > > > What the last printed lines now?
> > > > >
> > > > > > Thanks,
> > > > > > Girish
> > > > > >
> > > > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin
<igor@chub.in>
> > wrote:
> > > > > >
> > > > > > > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish
V wrote:
> > > > > > > > Hello,
> > > > > > >
> > > > > > > Hello Girish,
> > > > > > >
> > > > > > > ...
> > > > > > >
> > > > > > >
> > > > > > > Try to specify ramdisk here:
> > > > > > >
> > > > > > > (check path in my example)
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > >
> >
----------------------------------------------------------------------------------------------------------------
> > > > > > > >
> > > > > > > > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > > > > > > ramdisk =
"/boot/initrd.img-2.6.18.8-xen"
> > > > > > > > memory = 256
> > > > > > > > name = "fc6"
> > > > > > > > vif = [
''bridge=xenbr0'' ]
> > > > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > > > root = "/dev/sda1 ro"
> > > > > > > >
> > > > > > >
> > > > >
> >
----------------------------------------------------------------------------------------------------------------
> > > > > > > >
> > > > > > > --
> > > > > > > WBR, i.m.chubin
> > > > > > >
> > > > > > >
> > > > >
> > > > > > _______________________________________________
> > > > > > Xen-users mailing list
> > > > > > Xen-users@lists.xensource.com
> > > > > > http://lists.xensource.com/xen-users
> > > > >
> > > > > --
> > > > > WBR, i.m.chubin
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@lists.xensource.com
> > > > http://lists.xensource.com/xen-users
> > > >
> >
> > --
> > WBR, i.m.chubin
> >
> >
>

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

Igor Chubin

2008-Mar-25 21:04 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On Di, Mär 25, 2008 at 01:42:16 -0400, weiming wrote:> Did you check the process of creating the virtual partition?

You can check 
your domain U filesystem
with the commands:

mount -o loop /second/fc6_domudisk /mnt
chroot /mnt
(try to work with the chrooted system)
ls -l /sbin/init # (in chroot)

> 
> On Tue, Mar 25, 2008 at 1:12 PM, Girish V <girish.xen@gmail.com>
wrote:
> 
> > Hello Igor and Weiming,
> > Thnaks for the replies.
> >
> > I tried changing "sda" to "hda" in the config
file, but the kernel still
> > panics. The output is listed below. From a quick scan, it seems to be
no
> > different from when  I use sda (except for vbd 3 being used instead of
vbd8)
> >
> >
> >
--------------------------------------------------------------------------------------------------
> >
> > [root@localhost second]# xm create -c file-config-rh9_diskimg
> > Using config file "./file-config-rh9_diskimg".
> > Started domain fc6_new
> >                       Linux version 2.6.18.8-xen (
> > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat
4.1.2-13))
> > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > BIOS-provided physical RAM map:
> >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > 0MB HIGHMEM available.
> > 264MB LOWMEM available.
> > ACPI in unprivileged domain disabled
> > Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
> > Detected 6396.277 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: 3200.122 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-f51fe000, maxmem 2d7fe000
> > Memory: 251788k/270336k available (2056k kernel code, 10352k reserved,
> > 712k data, 196k init, 0k highmem)
> > Checking if this processor honours the WP bit even in supervisor
mode...
> > Ok.
> > calibrate_delay_direct() failed to get a good estimate for
> > loops_per_jiffy.
> > Probably due to long platform interrupts. Consider using
"lpj=" boot
> > option.
> >
> > Security Framework v1.0.0 initialized
> > Capability LSM initialized
> > 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
> > checking if image is initramfs... it is
> > Freeing initrd memory: 3552k 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: 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
> > IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
> > audit: initializing netlink socket (disabled)
> > audit(1206465527.468:1): initialized
> >
> > VFS: Disk quotas dquot_6.5.1
> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > Initializing Cryptographic API
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15
> > (usb?)
> > Failed to obtain physical IRQ 6
> > floppy0: Unable to grab DMA2 for the floppy driver
> > floppy0: no floppy controllers found
> > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> > loop: loaded (max 8 devices)
> > Xen virtual console successfully installed as xvc0
> > 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
> > Using IPI No-Shortcut mode
> > xen-vbd: registered block device major 3
> > blkfront: hda1: barriers enabled
> > XENBUS: Device with no driver: device/console/0
> > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > EDD information not available.
> > Freeing unused kernel memory: 196k freed
> > usbcore: registered new driver usbfs
> > usbcore: registered new driver hub
> > USB Universal Host Controller Interface driver v3.0
> > SCSI subsystem initialized
> > Fusion MPT base driver 3.04.01
> > Copyright (c) 1999-2005 LSI Logic Corporation
> > Fusion MPT SPI Host driver 3.04.01
> > kjournald starting.  Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with ordered data mode.
> > Kernel panic - not syncing: Attempted to kill init!
> >
> >
> >
------------------------------------------------------------------------------------------------------------------------
> > Thanks,
> > Girish
> >
> >
> >
> > On Tue, Mar 25, 2008 at 12:22 PM, Igor Chubin <igor@chub.in>
wrote:
> >
> > > On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:
> > > > seems that the driver for your hard driver controllers was
not
> > > included in
> > > > the image file.
> > >
> > >
> > > Real hard disk controller is not (and should not be!)
> > > visible in a guest domain.
> > > Guest domain uses PV-interfaces to the domain 0
> > > to access devices.
> > >
> > > Try to edit your config
> > > and change sda to hda:
> > >
> > > ===================================================> > >
kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > memory = 256
> > > name = "fc6"
> > > vif = [ ''bridge=xenbr0'' ]
> > > disk = [ ''file:/second/fc6_domudisk,hda1,w'' ]
> > > root = "/dev/hda1 ro"
> > > ===================================================> > >
> > >
> > >
> > > >
> > > > On Tue, Mar 25, 2008 at 9:35 AM, Girish V
<girish.xen@gmail.com>
> > > wrote:
> > > >
> > > > > The bootup message after using the ramdisk is shown
below.
> > > > > Thanks
> > > > > Girish
> > > > >
> > > > >
> > >
--------------------------------------------------------------------------------------------------------
> > > > >
> > > > > [root@localhost second]# xm create -c
file-config-rh9_diskimg
> > > > > Using config file
"./file-config-rh9_diskimg".
> > > > > Started domain fc6_new
> > > > >                       Linux version 2.6.18.8-xen (
> > > > > root@localhost.localdomain) (gcc version 4.1.2 20070626
(Red Hat
> > > 4.1.2-13))
> > > > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > > > BIOS-provided physical RAM map:
> > > > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > > > 0MB HIGHMEM available.
> > > > > 264MB LOWMEM available.
> > > > > ACPI in unprivileged domain disabled
> > > > > Allocating PCI resources starting at 20000000 (gap:
> > > 10800000:ef800000)
> > > > > Detected 3202.737 MHz processor.
> > > > > Built 1 zonelists.  Total pages: 67584
> > > > > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > > > > Memory: 251788k/270336k available (2056k kernel code,
10352k
> > > reserved,
> > > > > 712k data, 196k init, 0k highmem)
> > > > > Checking if this processor honours the WP bit even in
supervisor
> > > mode...
> > > > > Ok.
> > > > > Calibrating delay using timer specific routine..
6447.39 BogoMIPS
> > > > > (lpj=32236972)
> > > > > Security Framework v1.0.0 initialized
> > > > > Capability LSM initialized
> > > > > 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
> > > > > checking if image is initramfs... it is
> > > > > Freeing initrd memory: 3552k 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: 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
> > > > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > > > audit: initializing netlink socket (disabled)
> > > > > audit(1206452738.073:1): initialized
> > > > > VFS: Disk quotas dquot_6.5.1
> > > > > Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
> > > > > Initializing Cryptographic API
> > > > > io scheduler noop registered
> > > > > io scheduler anticipatory registered
> > > > > io scheduler deadline registered
> > > > > io scheduler cfq registered (default)
> > > > > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is
unknown type
> > > 15
> > > > > (usb?)
> > > > > Failed to obtain physical IRQ 6
> > > > > floppy0: Unable to grab DMA2 for the floppy driver
> > > > > floppy0: no floppy controllers found
> > > > > RAMDISK driver initialized: 16 RAM disks of 16384K size
1024
> > > blocksize
> > > > > loop: loaded (max 8 devices)
> > > > > Xen virtual console successfully installed as xvc0
> > > > > 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
> > > > > Using IPI No-Shortcut mode
> > > > > xen-vbd: registered block device major 8
> > > > > blkfront: sda1: barriers enabled
> > > > > XENBUS: Device with no driver: device/console/0
> > > > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > > > > EDD information not available.
> > > > > Freeing unused kernel memory: 196k freed
> > > > > usbcore: registered new driver usbfs
> > > > > usbcore: registered new driver hub
> > > > > USB Universal Host Controller Interface driver v3.0
> > > > > SCSI subsystem initialized
> > > > > register_blkdev: cannot get major 8 for sd
> > > > > Fusion MPT base driver 3.04.01
> > > > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > > > Fusion MPT SPI Host driver 3.04.01
> > > > > kjournald starting.  Commit interval 5 seconds
> > > > > EXT3-fs: mounted filesystem with ordered data mode.
> > > > > Kernel panic - not syncing: Attempted to kill init!
> > > > >
> > > > >
> > > > >
> > > > >
> > >
--------------------------------------------------------------------------------------------------------
> > > > >
> > > > > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin
<igor@chub.in> wrote:
> > > > >
> > > > > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish V
wrote:
> > > > > > > Hi Igor.
> > > > > > > Thanks for the suggestion. I did try using a
ramdisk - and the
> > > bootup
> > > > > > of the
> > > > > > > domU goes a little bit furter, but init still
crashes with the
> > > same
> > > > > > message
> > > > > > > as before.
> > > > > > > Any idea what I should do further?
> > > > > >
> > > > > >
> > > > > > What the last printed lines now?
> > > > > >
> > > > > > > Thanks,
> > > > > > > Girish
> > > > > > >
> > > > > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin
<igor@chub.in>
> > > wrote:
> > > > > > >
> > > > > > > > On Mi, Mär 19, 2008 at 10:43:25 -0400,
Girish V wrote:
> > > > > > > > > Hello,
> > > > > > > >
> > > > > > > > Hello Girish,
> > > > > > > >
> > > > > > > > ...
> > > > > > > >
> > > > > > > >
> > > > > > > > Try to specify ramdisk here:
> > > > > > > >
> > > > > > > > (check path in my example)
> > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > >
> > >
----------------------------------------------------------------------------------------------------------------
> > > > > > > > >
> > > > > > > > > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > > > > > > > ramdisk =
"/boot/initrd.img-2.6.18.8-xen"
> > > > > > > > > memory = 256
> > > > > > > > > name = "fc6"
> > > > > > > > > vif = [
''bridge=xenbr0'' ]
> > > > > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > > > > root = "/dev/sda1 ro"
> > > > > > > > >
> > > > > > > >
> > > > > >
> > >
----------------------------------------------------------------------------------------------------------------
> > > > > > > > >
> > > > > > > > --
> > > > > > > > WBR, i.m.chubin
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > > >
_______________________________________________
> > > > > > > Xen-users mailing list
> > > > > > > Xen-users@lists.xensource.com
> > > > > > > http://lists.xensource.com/xen-users
> > > > > >
> > > > > > --
> > > > > > WBR, i.m.chubin
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Xen-users mailing list
> > > > > Xen-users@lists.xensource.com
> > > > > http://lists.xensource.com/xen-users
> > > > >
> > >
> > > --
> > > WBR, i.m.chubin
> > >
> > >
> >
-- 
WBR, i.m.chubin


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

Girish V

2008-Mar-25 21:30 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

I checked by mounting and chrooting to the guest image and it worked. In
fact I have used this same image with other versions of Xen (3.1.3) for
instance and it works - so I am not sure if it is a problem with the image.
Girish

Weiming, to answer your question, I created the guest image following the
guidelines in the xen user manual. And that is the same way I have created
guest images for other versions of Xen.

Girish


On Tue, Mar 25, 2008 at 5:04 PM, Igor Chubin <igor@chub.in> wrote:
> On Di, Mär 25, 2008 at 01:42:16 -0400, weiming wrote:
> > Did you check the process of creating the virtual partition?
>
>
> You can check
> your domain U filesystem
> with the commands:
>
> mount -o loop /second/fc6_domudisk /mnt
> chroot /mnt
> (try to work with the chrooted system)
> ls -l /sbin/init # (in chroot)
>
>
> >
> > On Tue, Mar 25, 2008 at 1:12 PM, Girish V <girish.xen@gmail.com>
wrote:
> >
> > > Hello Igor and Weiming,
> > > Thnaks for the replies.
> > >
> > > I tried changing "sda" to "hda" in the config
file, but the kernel
> still
> > > panics. The output is listed below. From a quick scan, it seems
to be
> no
> > > different from when  I use sda (except for vbd 3 being used
instead of
> vbd8)
> > >
> > >
> > >
>
--------------------------------------------------------------------------------------------------
> > >
> > > [root@localhost second]# xm create -c file-config-rh9_diskimg
> > > Using config file "./file-config-rh9_diskimg".
> > > Started domain fc6_new
> > >                       Linux version 2.6.18.8-xen (
> > > root@localhost.localdomain) (gcc version 4.1.2 20070626 (Red Hat
> 4.1.2-13))
> > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > BIOS-provided physical RAM map:
> > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > 0MB HIGHMEM available.
> > > 264MB LOWMEM available.
> > > ACPI in unprivileged domain disabled
> > > Allocating PCI resources starting at 20000000 (gap:
10800000:ef800000)
> > > Detected 6396.277 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: 3200.122 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-f51fe000, maxmem 2d7fe000
> > > Memory: 251788k/270336k available (2056k kernel code, 10352k
reserved,
> > > 712k data, 196k init, 0k highmem)
> > > Checking if this processor honours the WP bit even in supervisor
> mode...
> > > Ok.
> > > calibrate_delay_direct() failed to get a good estimate for
> > > loops_per_jiffy.
> > > Probably due to long platform interrupts. Consider using
"lpj=" boot
> > > option.
> > >
> > > Security Framework v1.0.0 initialized
> > > Capability LSM initialized
> > > 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
> > > checking if image is initramfs... it is
> > > Freeing initrd memory: 3552k 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: 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
> > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > audit: initializing netlink socket (disabled)
> > > audit(1206465527.468:1): initialized
> > >
> > > VFS: Disk quotas dquot_6.5.1
> > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > Initializing Cryptographic API
> > > io scheduler noop registered
> > > io scheduler anticipatory registered
> > > io scheduler deadline registered
> > > io scheduler cfq registered (default)
> > > Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown
type 15
> > > (usb?)
> > > Failed to obtain physical IRQ 6
> > > floppy0: Unable to grab DMA2 for the floppy driver
> > > floppy0: no floppy controllers found
> > > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
blocksize
> > > loop: loaded (max 8 devices)
> > > Xen virtual console successfully installed as xvc0
> > > 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
> > > Using IPI No-Shortcut mode
> > > xen-vbd: registered block device major 3
> > > blkfront: hda1: barriers enabled
> > > XENBUS: Device with no driver: device/console/0
> > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
> > > EDD information not available.
> > > Freeing unused kernel memory: 196k freed
> > > usbcore: registered new driver usbfs
> > > usbcore: registered new driver hub
> > > USB Universal Host Controller Interface driver v3.0
> > > SCSI subsystem initialized
> > > Fusion MPT base driver 3.04.01
> > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > Fusion MPT SPI Host driver 3.04.01
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > Kernel panic - not syncing: Attempted to kill init!
> > >
> > >
> > >
>
------------------------------------------------------------------------------------------------------------------------
> > > Thanks,
> > > Girish
> > >
> > >
> > >
> > > On Tue, Mar 25, 2008 at 12:22 PM, Igor Chubin
<igor@chub.in> wrote:
> > >
> > > > On Di, Mär 25, 2008 at 10:29:25 -0400, weiming wrote:
> > > > > seems that the driver for your hard driver controllers
was not
> > > > included in
> > > > > the image file.
> > > >
> > > >
> > > > Real hard disk controller is not (and should not be!)
> > > > visible in a guest domain.
> > > > Guest domain uses PV-interfaces to the domain 0
> > > > to access devices.
> > > >
> > > > Try to edit your config
> > > > and change sda to hda:
> > > >
> > > > ===================================================> >
> > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > > > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > > memory = 256
> > > > name = "fc6"
> > > > vif = [ ''bridge=xenbr0'' ]
> > > > disk = [
''file:/second/fc6_domudisk,hda1,w'' ]
> > > > root = "/dev/hda1 ro"
> > > > ===================================================> >
> >
> > > >
> > > >
> > > > >
> > > > > On Tue, Mar 25, 2008 at 9:35 AM, Girish V
<girish.xen@gmail.com>
> > > > wrote:
> > > > >
> > > > > > The bootup message after using the ramdisk is
shown below.
> > > > > > Thanks
> > > > > > Girish
> > > > > >
> > > > > >
> > > >
>
--------------------------------------------------------------------------------------------------------
> > > > > >
> > > > > > [root@localhost second]# xm create -c
file-config-rh9_diskimg
> > > > > > Using config file
"./file-config-rh9_diskimg".
> > > > > > Started domain fc6_new
> > > > > >                       Linux version 2.6.18.8-xen (
> > > > > > root@localhost.localdomain) (gcc version 4.1.2
20070626 (Red Hat
> > > > 4.1.2-13))
> > > > > > #2 SMP Thu Mar 20 17:40:00 EDT 2008
> > > > > > BIOS-provided physical RAM map:
> > > > > >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > > > > > 0MB HIGHMEM available.
> > > > > > 264MB LOWMEM available.
> > > > > > ACPI in unprivileged domain disabled
> > > > > > Allocating PCI resources starting at 20000000
(gap:
> > > > 10800000:ef800000)
> > > > > > Detected 3202.737 MHz processor.
> > > > > > Built 1 zonelists.  Total pages: 67584
> > > > > > Kernel command line: root=/dev/sda1 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: 3200.114 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-f51fe000, maxmem 2d7fe000
> > > > > > Memory: 251788k/270336k available (2056k kernel
code, 10352k
> > > > reserved,
> > > > > > 712k data, 196k init, 0k highmem)
> > > > > > Checking if this processor honours the WP bit even
in supervisor
> > > > mode...
> > > > > > Ok.
> > > > > > Calibrating delay using timer specific routine..
6447.39BogoMIPS
> > > > > > (lpj=32236972)
> > > > > > Security Framework v1.0.0 initialized
> > > > > > Capability LSM initialized
> > > > > > 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
> > > > > > checking if image is initramfs... it is
> > > > > > Freeing initrd memory: 3552k 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: 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
> > > > > > IA-32 Microcode Update Driver: v1.14a-xen
<tigran@veritas.com>
> > > > > > audit: initializing netlink socket (disabled)
> > > > > > audit(1206452738.073:1): initialized
> > > > > > VFS: Disk quotas dquot_6.5.1
> > > > > > Dquot-cache hash table entries: 1024 (order 0,
4096 bytes)
> > > > > > Initializing Cryptographic API
> > > > > > io scheduler noop registered
> > > > > > io scheduler anticipatory registered
> > > > > > io scheduler deadline registered
> > > > > > io scheduler cfq registered (default)
> > > > > > Floppy drive(s): fd0 is unknown type 15 (usb?),
fd1 is unknown
> type
> > > > 15
> > > > > > (usb?)
> > > > > > Failed to obtain physical IRQ 6
> > > > > > floppy0: Unable to grab DMA2 for the floppy driver
> > > > > > floppy0: no floppy controllers found
> > > > > > RAMDISK driver initialized: 16 RAM disks of 16384K
size 1024
> > > > blocksize
> > > > > > loop: loaded (max 8 devices)
> > > > > > Xen virtual console successfully installed as xvc0
> > > > > > 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
> > > > > > Using IPI No-Shortcut mode
> > > > > > xen-vbd: registered block device major 8
> > > > > > blkfront: sda1: barriers enabled
> > > > > > XENBUS: Device with no driver: device/console/0
> > > > > > BIOS EDD facility v0.16 2004-Jun-25, 0 devices
found
> > > > > > EDD information not available.
> > > > > > Freeing unused kernel memory: 196k freed
> > > > > > usbcore: registered new driver usbfs
> > > > > > usbcore: registered new driver hub
> > > > > > USB Universal Host Controller Interface driver
v3.0
> > > > > > SCSI subsystem initialized
> > > > > > register_blkdev: cannot get major 8 for sd
> > > > > > Fusion MPT base driver 3.04.01
> > > > > > Copyright (c) 1999-2005 LSI Logic Corporation
> > > > > > Fusion MPT SPI Host driver 3.04.01
> > > > > > kjournald starting.  Commit interval 5 seconds
> > > > > > EXT3-fs: mounted filesystem with ordered data
mode.
> > > > > > Kernel panic - not syncing: Attempted to kill
init!
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
>
--------------------------------------------------------------------------------------------------------
> > > > > >
> > > > > > On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin
<igor@chub.in>
> wrote:
> > > > > >
> > > > > > > On So, Mär 23, 2008 at 12:30:11 -0400, Girish
V wrote:
> > > > > > > > Hi Igor.
> > > > > > > > Thanks for the suggestion. I did try
using a ramdisk - and
> the
> > > > bootup
> > > > > > > of the
> > > > > > > > domU goes a little bit furter, but init
still crashes with
> the
> > > > same
> > > > > > > message
> > > > > > > > as before.
> > > > > > > > Any idea what I should do further?
> > > > > > >
> > > > > > >
> > > > > > > What the last printed lines now?
> > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Girish
> > > > > > > >
> > > > > > > > On Sat, Mar 22, 2008 at 2:09 PM, Igor
Chubin <igor@chub.in>
> > > > wrote:
> > > > > > > >
> > > > > > > > > On Mi, Mär 19, 2008 at 10:43:25
-0400, Girish V wrote:
> > > > > > > > > > Hello,
> > > > > > > > >
> > > > > > > > > Hello Girish,
> > > > > > > > >
> > > > > > > > > ...
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Try to specify ramdisk here:
> > > > > > > > >
> > > > > > > > > (check path in my example)
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > > > > >
> > > > > > > > > > kernel =
"/boot/vmlinuz-2.6.18.8-xen"
> > > > > > > > > ramdisk =
"/boot/initrd.img-2.6.18.8-xen"
> > > > > > > > > > memory = 256
> > > > > > > > > > name = "fc6"
> > > > > > > > > > vif = [
''bridge=xenbr0'' ]
> > > > > > > > > > disk = [
''file:/second/fc6_domudisk,sda1,w'' ]
> > > > > > > > > > root = "/dev/sda1
ro"
> > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
>
----------------------------------------------------------------------------------------------------------------
> > > > > > > > > >
> > > > > > > > > --
> > > > > > > > > WBR, i.m.chubin
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > > >
_______________________________________________
> > > > > > > > Xen-users mailing list
> > > > > > > > Xen-users@lists.xensource.com
> > > > > > > > http://lists.xensource.com/xen-users
> > > > > > >
> > > > > > > --
> > > > > > > WBR, i.m.chubin
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Xen-users mailing list
> > > > > > Xen-users@lists.xensource.com
> > > > > > http://lists.xensource.com/xen-users
> > > > > >
> > > >
> > > > --
> > > > WBR, i.m.chubin
> > > >
> > > >
> > >
>
> --
> WBR, i.m.chubin
>
>

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

Igor Chubin

2008-Mar-25 21:46 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On Di, Mär 25, 2008 at 05:30:17 -0400, Girish V wrote:> I checked by mounting and chrooting to the guest image and it worked. In
> fact I have used this same image with other versions of Xen (3.1.3) for
> instance and it works - so I am not sure if it is a problem with the image.
> Girish

Can you take the kernel and the initrd from that system where domain
starts fine and try to use it here (for domU only!)?

-- 
WBR, i.m.chubin


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

Girish V

2008-Mar-27 14:59 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

Thanks for continuting to help me.
Tried what you suggested (boot the domU with an earlier version of the xen
kernel and intird) that, but it still panics with exactly the same messages.
Girish


On Tue, Mar 25, 2008 at 5:46 PM, Igor Chubin <igor@chub.in> wrote:
> On Di, Mär 25, 2008 at 05:30:17 -0400, Girish V wrote:
> > I checked by mounting and chrooting to the guest image and it worked.
In
> > fact I have used this same image with other versions of Xen (3.1.3)
for
> > instance and it works - so I am not sure if it is a problem with the
> image.
> > Girish
>
>
> Can you take the kernel and the initrd from that system where domain
> starts fine and try to use it here (for domU only!)?
>
> --
> WBR, i.m.chubin
>
>

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

weiming

2008-Mar-27 15:14 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

This is weird.
Since your image file once worked for xen 3.1, it should be no problem.

So the problem might stem from the kernel. Did you build the kernel by
yourself or it iss shipped by some linux distribution?


On Thu, Mar 27, 2008 at 10:59 AM, Girish V <girish.xen@gmail.com> wrote:
> Thanks for continuting to help me.
> Tried what you suggested (boot the domU with an earlier version of the xen
> kernel and intird) that, but it still panics with exactly the same
messages.
> Girish
>
>
>
> On Tue, Mar 25, 2008 at 5:46 PM, Igor Chubin <igor@chub.in> wrote:
>
> > On Di, Mär 25, 2008 at 05:30:17 -0400, Girish V wrote:
> > > I checked by mounting and chrooting to the guest image and it
worked.
> > In
> > > fact I have used this same image with other versions of Xen
(3.1.3)
> > for
> > > instance and it works - so I am not sure if it is a problem with
the
> > image.
> > > Girish
> >
> >
> > Can you take the kernel and the initrd from that system where domain
> > starts fine and try to use it here (for domU only!)?
> >
> > --
> > WBR, i.m.chubin
> >
> >
>

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

Girish V

2008-Mar-28 11:57 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

Compiled it from source.
Girish

On Thu, Mar 27, 2008 at 11:14 AM, weiming <zephyr.zhao@gmail.com> wrote:
> This is weird.
> Since your image file once worked for xen 3.1, it should be no problem.
>
> So the problem might stem from the kernel. Did you build the kernel by
> yourself or it iss shipped by some linux distribution?
>
>
>
> On Thu, Mar 27, 2008 at 10:59 AM, Girish V <girish.xen@gmail.com>
wrote:
>
> > Thanks for continuting to help me.
> > Tried what you suggested (boot the domU with an earlier version of the
> > xen kernel and intird) that, but it still panics with exactly the same
> > messages.
> > Girish
> >
> >
> >
> > On Tue, Mar 25, 2008 at 5:46 PM, Igor Chubin <igor@chub.in>
wrote:
> >
> > > On Di, Mär 25, 2008 at 05:30:17 -0400, Girish V wrote:
> > > > I checked by mounting and chrooting to the guest image and
it
> > > worked. In
> > > > fact I have used this same image with other versions of Xen
(3.1.3)
> > > for
> > > > instance and it works - so I am not sure if it is a problem
with the
> > > image.
> > > > Girish
> > >
> > >
> > > Can you take the kernel and the initrd from that system where
domain
> > > starts fine and try to use it here (for domU only!)?
> > >
> > > --
> > > WBR, i.m.chubin
> > >
> > >
> >
>

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

Igor Chubin

2008-Mar-31 23:38 UTC

head link

Re: [Xen-users] Kernel Panic on trying to boot domU

On Fr, Mär 28, 2008 at 07:57:28 -0400, Girish V wrote:> Compiled it from source.
> Girish

Can you send me the kernel config file and 
describe build procedure you used?
> 
> On Thu, Mar 27, 2008 at 11:14 AM, weiming <zephyr.zhao@gmail.com>
wrote:
> 
> > This is weird.
> > Since your image file once worked for xen 3.1, it should be no
problem.
> >
> > So the problem might stem from the kernel. Did you build the kernel by
> > yourself or it iss shipped by some linux distribution?
> >
> >
> >
> > On Thu, Mar 27, 2008 at 10:59 AM, Girish V
<girish.xen@gmail.com> wrote:
> >
> > > Thanks for continuting to help me.
> > > Tried what you suggested (boot the domU with an earlier version
of the
> > > xen kernel and intird) that, but it still panics with exactly the
same
> > > messages.
> > > Girish
> > >
> > >
> > >
> > > On Tue, Mar 25, 2008 at 5:46 PM, Igor Chubin <igor@chub.in>
wrote:
> > >
> > > > On Di, Mär 25, 2008 at 05:30:17 -0400, Girish V wrote:
> > > > > I checked by mounting and chrooting to the guest image
and it
> > > > worked. In
> > > > > fact I have used this same image with other versions of
Xen (3.1.3)
> > > > for
> > > > > instance and it works - so I am not sure if it is a
problem with the
> > > > image.
> > > > > Girish
> > > >
> > > >
> > > > Can you take the kernel and the initrd from that system
where domain
> > > > starts fine and try to use it here (for domU only!)?
> > > >
> > > > --
> > > > WBR, i.m.chubin
> > > >
> > > >
> > >
> >
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
-- 
WBR, i.m.chubin


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

Xen users - Mar 2008 - Kernel Panic on trying to boot domU

[Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU

Re: [Xen-users] Kernel Panic on trying to boot domU