Czerwinski
2005-Jun-16 11:42 UTC
[Xen-users] Problems booting domian - unable to mount root device
Hi everybody,
i run SuSE 9.3 on a thinkpad T30, 1 GB RAM, 60 GB HDD, Pentium IV Mobile,
2 GHz.
For trying Xen i deviced to install debian on a file-backed VBD as
described in the chapters 5.2 and appendix A in the user''s
documentation
on http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html.
I have to do the installation on a VBD because my SuSE uses all the HD:
# fdisk -l /dev/hda
Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 131 1052226 82 Linux swap /
Solaris
/dev/hda2 * 132 7296 57552862+ 83 Linux
After some troubles I got my dom0 running (I allow 512 MB RAM):
# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 512 0 r---- 668.8
This is my xencfg:
# -*- mode: python; -*-
#===========================================================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#===========================================================================
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/vmlinuz-xen"
# Optional ramdisk.
ramdisk = "/boot/initrd-xen"
# The domain build function. Default is ''linux''.
builder=''linux''
# Initial memory allocation (in megabytes) for the new domain.
memory = 64
# A name for your domain. All domains must have different names.
name = "VM_Debian"
# Which CPU to start domain on?
cpu = -1 # leave to Xen to pick
#----------------------------------------------------------------------------
# Define network interfaces.
# Number of network interfaces. Default is 1.
nics=1
# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
#vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ]
#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.
disk = [ ''file:/usr/local/xenvm/vm1disk,hda1,w'']
#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).
# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
hostname= "vm1"
# Set root device.
#root = "/dev/hda1 ro"
root = "/dev/hda1 ro"
# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = ''169.254.1.0''
# Root directory on the nfs server.
#nfs_root = ''/full/path/to/root/directory''
# Sets runlevel 4.
extra = "4"
#----------------------------------------------------------------------------
# Set according to whether you want the domain restarted when it exits.
# The default is ''onreboot'', which restarts the domain when it
shuts down
# with exit code reboot.
# Other values are ''always'', and ''never''.
#restart = ''onreboot''
#===========================================================================
The debian-(guest-)system was installed via debootstrap.
When I start the domain the following happens:
# xm create -c xencfg
Using config file "/etc/xen/xencfg".
Started domain VM_Debian, console on port 9617
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.11.4-21.7-xen (geeko@buildhost) (gcc version 3.3.5
20050117 (prerelease) (SUSE Linux)) #1 Thu Jun 2 14:23:14 UTC 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
0MB HIGHMEM available.
64MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000)
Built 1 zonelists
Kernel command line: ip=:1.2.3.4:::vm1:eth0:dhcp root=/dev/hda1 ro 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 1993.584 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 58832k/65536k available (1902k kernel code, 6616k reserved, 568k
data, 136k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
checking if image is initramfs... it is
Freeing initrd memory: 2882k freed
NET: Registered protocol family 16
PCI: Using configuration type Xen
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
PCI: Probing PCI hardware
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
audit: initializing netlink socket (disabled)
audit(1118921503.069:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: abort, cannot reserve video memory at 0x0
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
Trying to free nonexistent resource <00000000-ffffffff>
vesafb: probe of vesafb.0 failed with error -5
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 8
NET: Registered protocol family 20
Freeing unused kernel memory: 136k freed
Starting udev
Creating devices
Loading kernel/drivers/ide/ide-core.ko
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Loading kernel/drivers/ide/pci/piix.ko
Loading kernel/drivers/ide/ide-disk.ko
Loading kernel/drivers/cdrom/cdrom.ko
Loading kernel/drivers/ide/ide-cd.ko
Loading kernel/fs/reiserfs/reiserfs.ko
Waiting for device /dev/hda1 to appear: ok
rootfs: major=3 minor=1 devn=769
Mounting root /dev/hda1
mount: No such device
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..Linux version 2.6.11.4-21.7-xen
(geeko@buildhost) (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux))
#1 Thu Jun 2 14:23:14 UTC 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
0MB HIGHMEM available.
64MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000)
Built 1 zonelists
Kernel command line: ip=:1.2.3.4:::vm1:eth0:dhcp root=/dev/hda1 ro 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 1993.584 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 58832k/65536k available (1902k kernel code, 6616k reserved, 568k
data, 136k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
checking if image is initramfs... it is
Freeing initrd memory: 2882k freed
NET: Registered protocol family 16
PCI: Using configuration type Xen
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
PCI: Probing PCI hardware
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
audit: initializing netlink socket (disabled)
audit(1118921508.329:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
vesafb: abort, cannot reserve video memory at 0x0
vesafb: abort, cannot ioremap video memory 0x0 @ 0x0
Trying to free nonexistent resource <00000000-ffffffff>
vesafb: probe of vesafb.0 failed with error -5
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 8
NET: Registered protocol family 20
Freeing unused kernel memory: 136k freed
Starting udev
Creating devices
Loading kernel/drivers/ide/ide-core.ko
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
Loading kernel/drivers/ide/pci/piix.ko
Loading kernel/drivers/ide/ide-disk.ko
Loading kernel/drivers/cdrom/cdrom.ko
Loading kernel/drivers/ide/ide-cd.ko
Loading kernel/fs/reiserfs/reiserfs.ko
Waiting for device /dev/hda1 to appear: ok
rootfs: major=3 minor=1 devn=769
Mounting root /dev/hda1
mount: No such device
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds.. ----------------
I checked the devs of the guest-installation:
# chroot /mnt/vm1disk/
# ls -lac /dev/h*
brw-r--r-- 1 root root 3, 0 Jun 16 10:47 /dev/hda
brw-r--r-- 1 root root 3, 1 Jun 16 10:45 /dev/hda1
brw-rw---- 1 root disk 3, 2 Jun 16 11:17 /dev/hda2
fstab of guest-installation:
# cat /etc/fstab
/dev/hda1 / ext3 acl,user_xattr
1 1
proc /proc proc defaults
0 0
usbfs /proc/bus/usb usbfs noauto
0 0
sysfs /sys sysfs noauto
0 0
/dev/cdrecorder /media/cdrecorder subfs
noauto,fs=cdfss,unhide,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
So, could anybody please give some hints where to look for the problem?
Thanks for any help!
Cz.
--
Using Opera''s revolutionary e-mail client: http://www.opera.com/m2/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Czerwinski
2005-Jun-16 15:22 UTC
Re: [Xen-users] Problems booting domian - unable to mount root device
err.... I did not find the mentioned solition, but: I could fix it: o I tried to install a SuSE-guest-domain - worked. o I tried both /boot and /dev from SuSE-guest on debian-guest - no success. o I disabled the ramdisk-statement in the xencfg-file (this is ESSENTIAL!) o Then I ran out of loop-devices that I need for mounting the VBD (mount -o loop /usr/local/xenvm/vm1disk /mnt/vm1disk) I don''t exactly know how this can happen, but I cound find out that loop devices can be free via losetup -d /dev/loop<no> I freed all loop-devs, since then debian boots. There are still some odd things happening, but I think the boot-problem should be solved now. All the best! Cz. On Thu, 16 Jun 2005 14:34:44 +0200, e&v <ervin23@gmail.com> wrote:> see the mails on the following subject and you''ll find the solution / > > "Suse 9.3 "kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block (8,1)" > > On 6/16/05, Czerwinski <czerwinski@inode.at> wrote: >> Hi everybody, >> >> i run SuSE 9.3 on a thinkpad T30, 1 GB RAM, 60 GB HDD, Pentium IV >> Mobile, >> 2 GHz. >> >> For trying Xen i deviced to install debian on a file-backed VBD as >> described in the chapters 5.2 and appendix A in the user''s documentation >> on >> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/readmes/user/user.html. >> >> I have to do the installation on a VBD because my SuSE uses all the HD: >> # fdisk -l /dev/hda >> >> Disk /dev/hda: 60.0 GB, 60011642880 bytes >> 255 heads, 63 sectors/track, 7296 cylinders >> Units = cylinders of 16065 * 512 = 8225280 bytes >> >> Device Boot Start End Blocks Id System >> /dev/hda1 1 131 1052226 82 Linux swap / >> Solaris >> /dev/hda2 * 132 7296 57552862+ 83 Linux >> >> After some troubles I got my dom0 running (I allow 512 MB RAM): >> # xm list >> Name Id Mem(MB) CPU State Time(s) Console >> Domain-0 0 512 0 r---- 668.8 >> >> This is my xencfg: >> # -*- mode: python; -*- >> #===========================================================================>> # Python configuration setup for ''xm create''. >> # This script sets the parameters used when a domain is created using >> ''xm >> create''. >> # You use a separate script for each domain you want to create, or >> # you can set the parameters for the domain on the xm command line. >> #===========================================================================>> >> #---------------------------------------------------------------------------- >> # Kernel image file. >> kernel = "/boot/vmlinuz-xen" >> >> # Optional ramdisk. >> ramdisk = "/boot/initrd-xen" >> >> # The domain build function. Default is ''linux''. >> builder=''linux'' >> >> # Initial memory allocation (in megabytes) for the new domain. >> memory = 64 >> >> # A name for your domain. All domains must have different names. >> name = "VM_Debian" >> >> # Which CPU to start domain on? >> cpu = -1 # leave to Xen to pick >> >> #---------------------------------------------------------------------------- >> # Define network interfaces. >> >> # Number of network interfaces. Default is 1. >> nics=1 >> >> # Optionally define mac and/or bridge for the network interfaces. >> # Random MACs are assigned if not given. >> #vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] >> >> #---------------------------------------------------------------------------- >> # Define the disk devices you want the domain to have access to, and >> # what you want them accessible as. >> # Each disk entry is of the form phy:UNAME,DEV,MODE >> # where UNAME is the device, DEV is the device name the domain will see, >> # and MODE is r for read-only, w for read-write. >> >> disk = [ ''file:/usr/local/xenvm/vm1disk,hda1,w''] >> >> #---------------------------------------------------------------------------- >> # Set the kernel command line for the new domain. >> # You only need to define the IP parameters and hostname if the domain''s >> # IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP. >> # You can use ''extra'' to set the runlevel and custom environment >> # variables used by custom rc scripts (e.g. VMID=, usr= ). >> >> # Set if you want dhcp to allocate the IP address. >> dhcp="dhcp" >> # Set netmask. >> #netmask>> # Set default gateway. >> #gateway>> # Set the hostname. >> hostname= "vm1" >> >> # Set root device. >> #root = "/dev/hda1 ro" >> root = "/dev/hda1 ro" >> >> # Root device for nfs. >> #root = "/dev/nfs" >> # The nfs server. >> #nfs_server = ''169.254.1.0'' >> # Root directory on the nfs server. >> #nfs_root = ''/full/path/to/root/directory'' >> >> # Sets runlevel 4. >> extra = "4" >> >> #---------------------------------------------------------------------------- >> # Set according to whether you want the domain restarted when it exits. >> # The default is ''onreboot'', which restarts the domain when it shuts >> down >> # with exit code reboot. >> # Other values are ''always'', and ''never''. >> >> #restart = ''onreboot'' >> >> #===========================================================================>> >> >> The debian-(guest-)system was installed via debootstrap. >> >> When I start the domain the following happens: >> # xm create -c xencfg >> Using config file "/etc/xen/xencfg". >> Started domain VM_Debian, console on port 9617 >> ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** >> Linux version 2.6.11.4-21.7-xen (geeko@buildhost) (gcc version 3.3.5 >> 20050117 (prerelease) (SUSE Linux)) #1 Thu Jun 2 14:23:14 UTC 2005 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000004000000 (usable) >> 0MB HIGHMEM available. >> 64MB LOWMEM available. >> DMI not present. >> IRQ lockup detection disabled >> Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000) >> Built 1 zonelists >> Kernel command line: ip=:1.2.3.4:::vm1:eth0:dhcp root=/dev/hda1 ro 4 >> Initializing CPU#0 >> PID hash table entries: 512 (order: 9, 8192 bytes) >> Xen reported: 1993.584 MHz processor. >> Using tsc for high-res timesource >> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) >> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >> Memory: 58832k/65536k available (1902k kernel code, 6616k reserved, 568k >> data, 136k init, 0k highmem) >> Checking if this processor honours the WP bit even in supervisor mode... >> Ok. >> Security Framework v1.0.0 initialized >> SELinux: Disabled at boot. >> Mount-cache hash table entries: 512 (order: 0, 4096 bytes) >> CPU: Trace cache: 12K uops, L1 D cache: 8K >> CPU: L2 cache: 512K >> CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz stepping 04 >> Enabling fast FPU save and restore... done. >> Enabling unmasked SIMD FPU exception support... done. >> Checking ''hlt'' instruction... disabled >> checking if image is initramfs... it is >> Freeing initrd memory: 2882k freed >> NET: Registered protocol family 16 >> PCI: Using configuration type Xen >> Linux Plug and Play Support v0.97 (c) Adam Belay >> xen_mem: Initialising balloon driver. >> PCI: Probing PCI hardware >> PCI: Probing PCI hardware >> PCI: Probing PCI hardware (bus 00) >> TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca) >> audit: initializing netlink socket (disabled) >> audit(1118921503.069:0): initialized >> Total HugeTLB memory allocated, 0 >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) >> Initializing Cryptographic API >> vesafb: abort, cannot reserve video memory at 0x0 >> vesafb: abort, cannot ioremap video memory 0x0 @ 0x0 >> Trying to free nonexistent resource <00000000-ffffffff> >> vesafb: probe of vesafb.0 failed with error -5 >> isapnp: Scanning for PnP cards... >> isapnp: No Plug & Play device found >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered >> RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize >> loop: loaded (max 8 devices) >> Xen virtual console successfully installed as tty >> Event-channel device installed. >> xen_blk: Initialising virtual block device driver >> xen_net: Initialising virtual ethernet driver. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> NET: Registered protocol family 2 >> IP: routing cache hash table of 512 buckets, 4Kbytes >> TCP established hash table entries: 4096 (order: 3, 32768 bytes) >> TCP bind hash table entries: 4096 (order: 2, 16384 bytes) >> TCP: Hash tables configured (established 4096 bind 4096) >> NET: Registered protocol family 1 >> NET: Registered protocol family 8 >> NET: Registered protocol family 20 >> Freeing unused kernel memory: 136k freed >> Starting udev >> Creating devices >> Loading kernel/drivers/ide/ide-core.ko >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with >> idebus=xx >> Loading kernel/drivers/ide/pci/piix.ko >> Loading kernel/drivers/ide/ide-disk.ko >> Loading kernel/drivers/cdrom/cdrom.ko >> Loading kernel/drivers/ide/ide-cd.ko >> Loading kernel/fs/reiserfs/reiserfs.ko >> Waiting for device /dev/hda1 to appear: ok >> rootfs: major=3 minor=1 devn=769 >> Mounting root /dev/hda1 >> mount: No such device >> Kernel panic - not syncing: Attempted to kill init! >> <0>Rebooting in 1 seconds..Linux version 2.6.11.4-21.7-xen >> (geeko@buildhost) (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)) >> #1 Thu Jun 2 14:23:14 UTC 2005 >> BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000004000000 (usable) >> 0MB HIGHMEM available. >> 64MB LOWMEM available. >> DMI not present. >> IRQ lockup detection disabled >> Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000) >> Built 1 zonelists >> Kernel command line: ip=:1.2.3.4:::vm1:eth0:dhcp root=/dev/hda1 ro 4 >> Initializing CPU#0 >> PID hash table entries: 512 (order: 9, 8192 bytes) >> Xen reported: 1993.584 MHz processor. >> Using tsc for high-res timesource >> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) >> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >> Memory: 58832k/65536k available (1902k kernel code, 6616k reserved, 568k >> data, 136k init, 0k highmem) >> Checking if this processor honours the WP bit even in supervisor mode... >> Ok. >> Security Framework v1.0.0 initialized >> SELinux: Disabled at boot. >> Mount-cache hash table entries: 512 (order: 0, 4096 bytes) >> CPU: Trace cache: 12K uops, L1 D cache: 8K >> CPU: L2 cache: 512K >> CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz stepping 04 >> Enabling fast FPU save and restore... done. >> Enabling unmasked SIMD FPU exception support... done. >> Checking ''hlt'' instruction... disabled >> checking if image is initramfs... it is >> Freeing initrd memory: 2882k freed >> NET: Registered protocol family 16 >> PCI: Using configuration type Xen >> Linux Plug and Play Support v0.97 (c) Adam Belay >> xen_mem: Initialising balloon driver. >> PCI: Probing PCI hardware >> PCI: Probing PCI hardware >> PCI: Probing PCI hardware (bus 00) >> TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca) >> audit: initializing netlink socket (disabled) >> audit(1118921508.329:0): initialized >> Total HugeTLB memory allocated, 0 >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) >> Initializing Cryptographic API >> vesafb: abort, cannot reserve video memory at 0x0 >> vesafb: abort, cannot ioremap video memory 0x0 @ 0x0 >> Trying to free nonexistent resource <00000000-ffffffff> >> vesafb: probe of vesafb.0 failed with error -5 >> isapnp: Scanning for PnP cards... >> isapnp: No Plug & Play device found >> PNP: No PS/2 controller found. Probing ports directly. >> i8042.c: No controller found. >> io scheduler noop registered >> io scheduler anticipatory registered >> io scheduler deadline registered >> io scheduler cfq registered >> RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize >> loop: loaded (max 8 devices) >> Xen virtual console successfully installed as tty >> Event-channel device installed. >> xen_blk: Initialising virtual block device driver >> xen_net: Initialising virtual ethernet driver. >> mice: PS/2 mouse device common for all mice >> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27 >> NET: Registered protocol family 2 >> IP: routing cache hash table of 512 buckets, 4Kbytes >> TCP established hash table entries: 4096 (order: 3, 32768 bytes) >> TCP bind hash table entries: 4096 (order: 2, 16384 bytes) >> TCP: Hash tables configured (established 4096 bind 4096) >> NET: Registered protocol family 1 >> NET: Registered protocol family 8 >> NET: Registered protocol family 20 >> Freeing unused kernel memory: 136k freed >> Starting udev >> Creating devices >> Loading kernel/drivers/ide/ide-core.ko >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 >> ide: Assuming 50MHz system bus speed for PIO modes; override with >> idebus=xx >> Loading kernel/drivers/ide/pci/piix.ko >> Loading kernel/drivers/ide/ide-disk.ko >> Loading kernel/drivers/cdrom/cdrom.ko >> Loading kernel/drivers/ide/ide-cd.ko >> Loading kernel/fs/reiserfs/reiserfs.ko >> Waiting for device /dev/hda1 to appear: ok >> rootfs: major=3 minor=1 devn=769 >> Mounting root /dev/hda1 >> mount: No such device >> Kernel panic - not syncing: Attempted to kill init! >> <0>Rebooting in 1 seconds.. ---------------- >> >> I checked the devs of the guest-installation: >> # chroot /mnt/vm1disk/ >> # ls -lac /dev/h* >> brw-r--r-- 1 root root 3, 0 Jun 16 10:47 /dev/hda >> brw-r--r-- 1 root root 3, 1 Jun 16 10:45 /dev/hda1 >> brw-rw---- 1 root disk 3, 2 Jun 16 11:17 /dev/hda2 >> >> fstab of guest-installation: >> # cat /etc/fstab >> /dev/hda1 / ext3 acl,user_xattr >> 1 1 >> proc /proc proc defaults >> 0 0 >> usbfs /proc/bus/usb usbfs noauto >> 0 0 >> sysfs /sys sysfs noauto >> 0 0 >> /dev/cdrecorder /media/cdrecorder subfs >> noauto,fs=cdfss,unhide,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 >> >> So, could anybody please give some hints where to look for the problem? >> >> Thanks for any help! >> >> Cz. >> -- >> Using Opera''s revolutionary e-mail client: http://www.opera.com/m2/ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > >-- Using Opera''s revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users