Re: [Xen-users] Problem booting domU

["Christopher G. Stach II" <cgs@xxxxxxxxx>]

Angel L. Mateo wrote:
> Hello,
> 
>       I have just installed xen 3.0.1 in a debian sarge system. After some
> days of trying with binary distribution of xen, I found a debian  sarge
> backport at http://packages.debianbase.de/sarge/i386/xen3, and this is
> the one I have installed.
> 
>       I have compiled my dom0's custom kernel (I had to do it because the
> "standard" one doesn't boot in my dell poweredge 750). Basically, the
> difference between the standard and mine is that I have included
> megaraid in the kernel, not as a module). With this custom kernel I have
> running my dom0.
> 
>       The problem I have is what domU. I created a debian system for domU
> (with debootsrap) and I compiled a new custom domU kernel. This kernel
> is the same as dom0 but I have also include raid support in the kernel
> (not as a module, in dom0 I have it as a module).
> 
>       The problem I have is that I can't boot this domU, because I get the
> error:
> 
> VFS: Cannot open root device "sda1" or unknown-block(8,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,1)
> 
>       I have tried to boot domU with the same kernel as dom0, but I get the
> same behaviour.
> 
>       Any help?
> 
> PS: attached is the full log I get when I try to boot domU and the
> configuration of this domU.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> felis:~# xm create dhcp1.cfg -c
> Using config file "/etc/xen/dhcp1.cfg".
> Started domain dhcp1
> Linux version 2.6.12.6-atica-xenu (root@galemys) (gcc versión 3.3.5 (Debian 
> 1:3.3.5-13)) #1 SMP Tue Mar 7 14:39:51 CET 2006
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 0000000010000000 (usable)
>  264MB LOWMEM available.
>  ACPI in unprivileged domain disabled
>  IRQ lockup detection disabled
>  Built 1 zonelists
>  Kernel command line:  root=/dev/sda1 ro
>  Initializing CPU#0
>  PID hash table entries: 2048 (order: 11, 32768 bytes)
>  Xen reported: 2800.096 MHz processor.
>  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-fbee7000, maxmem 34000000
>  Memory: 256000k/270336k available (1457k kernel code, 5836k reserved, 616k 
> data, 156k init, 0k highmem)
>  Checking if this processor honours the WP bit even in supervisor mode... Ok.
>  Security Framework v1.0.0 initialized
>  Mount-cache hash table entries: 512
>  CPU: Trace cache: 12K uops, L1 D cache: 16K
>  CPU: L2 cache: 1024K
>  Enabling fast FPU save and restore... done.
>  Enabling unmasked SIMD FPU exception support... done.
>  Checking 'hlt' instruction... disabled
>  Brought up 1 CPUs
>  Grant table initialized
>  NET: Registered protocol family 16
>  ACPI: Subsystem revision 20050309
>  ACPI: Interpreter disabled.
>  xen_mem: Initialising balloon driver.
>  PCI: Using ACPI for IRQ routing
>  PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a 
> report
>  PCI: System does not support PCI
>  PCI: System does not support PCI
>  Number of CPUs sharing cache didn't match any known set of CPUs
>  Number of CPUs sharing cache didn't match any known set of CPUs
>  VFS: Disk quotas dquot_6.5.1
>  Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>  devfs: 2004-01-31 Richard Gooch (rgooch@xxxxxxxxxxxxx)
>  devfs: boot_options: 0x0
>  Initializing Cryptographic API
>  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 8192K size 1024 blocksize
>  Xen virtual console successfully installed as tty1
>  Event-channel device installed.
>  blkif_init: reqs=64, pages=704, mmap_vstart=0xcf800000
>  netfront: Initialising virtual ethernet driver.
>  mice: PS/2 mouse device common for all mice
>  md: linear personality registered as nr 1
>  md: raid0 personality registered as nr 2
>  md: raid1 personality registered as nr 3
>  md: raid5 personality registered as nr 4
>  raid5: automatically using best checksumming function: pIII_sse
>     pIII_sse  :  2379.200 MB/sec
>       raid5: using function: pIII_sse (2379.200 MB/sec)
>       raid6: int32x1    737 MB/s
>       raid6: int32x2    731 MB/s
>       raid6: int32x4    615 MB/s
>       raid6: int32x8    483 MB/s
>       raid6: mmxx1     1605 MB/s
>       raid6: mmxx2     1837 MB/s
>       raid6: sse1x1     951 MB/s
>       raid6: sse1x2    1089 MB/s
>       raid6: sse2x1    1829 MB/s
>       raid6: sse2x2    1938 MB/s
>       raid6: using algorithm sse2x2 (1938 MB/s)
>       md: raid6 personality registered as nr 8
>       md: multipath personality registered as nr 7
>       md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
>       device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@xxxxxxxxxx
>       NET: Registered protocol family 2
>       Registering block device major 8
>       IP: routing cache hash table of 2048 buckets, 16Kbytes
>       TCP established hash table entries: 16384 (order: 5, 131072 bytes)
>       TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
>       TCP: Hash tables configured (established 16384 bind 16384)
>       NET: Registered protocol family 8
>       NET: Registered protocol family 20
>       devfs_mk_dev: could not append to parent for md/0
>       md: Autodetecting RAID arrays.
>       md: autorun ...
>       md: ... autorun DONE.
>       VFS: Cannot open root device "sda1" or unknown-block(8,1)
>       Please append a correct "root=" boot option
>       Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(8,1)
> 
> 
> 
> ------------------------------------------------------------------------
> 
> #kernel       = "/boot/xen-linux-2.6.12.6-atica-xen0-xenU"
> kernel = "/boot/xen-linux-2.6.12.6-atica-xenu"
> #kernel = "/boot/vmlinuz-2.6.12-xenU"
> 
> memory        = 256
> name  = "dhcp1"
> 
> vif = [ '' ]
> 
> disk  = ['phy:vm_volumes/root.dhcp1,sda1,w',
>                  'phy:vm_volumes/var.dhcp1,sda2,w',
>                  'phy:vm_volumes/swap.dhcp1,sda3,w']
> 
> root  = "/dev/sda1 ro"
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

dom0 DOES need megaraid
dom0 DOES need LVM
dom0 DOES need block device backend

domU DOES NOT need megaraid (or any other SCSI lowlevel drivers)
domU DOES NOT need LVM
domU DOES NOT need LVM RAID
domU DOES need block device frontend

After you rebuild your kernels and reboot, make sure that the volume
group(s) are recognized in dom0 and that you have /dev/<volume
group>/<logical volumes> available.  I suppose for your volume group,
based on your configuration, it would be /dev/vm_volumes/var.dhcp1, etc.
 If those are not available in dom0, it obviously won't work.  Also,
your configuration should be like:

phy:vm_volumes/root.dhcp1,sda1,w

NOT

phy:/vm_volumes/root.dhcp1,sda1,w

To avoid any future confusion with SCSI major numbers, I would use xvda1
instead of sda1 in your config (and the domU's fstab.)

-- 
Christopher G. Stach II


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