WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Cannot open root device for dom0

To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Cannot open root device for dom0
From: "Williamson, Mark A" <mark.a.williamson@xxxxxxxxx>
Date: Sat, 17 Jan 2004 04:04:52 -0000
Cc: <stevegt@xxxxxxxxxxxxx>
Delivery-date: Sat, 17 Jan 2004 04:09:51 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcPclsieufylljMPR/SY1T+oNj/LIQAFtXkQ
Thread-topic: [Xen-devel] Cannot open root device for dom0
Steve and I have discussed this off-list.  The problem disappeared so
it's appears to be just due to some local config issues and doesn't
appear to be something amiss with Xen / XenoLinux.  Nevertheless, if
anyone else experiencing similar problems, please do send e-mail to this
list.

Cheers,

Mark

-----Original Message-----
> From: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> stevegt@xxxxxxxxxxxxx
> Sent: 17 January 2004 01:07
> To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Cannot open root device for dom0
> 
> 
> 
> Hi All,
> 
> Getting "Cannot open root device" on a pretty vanilla setup.  
> Xen seems
> to see the device but xenolinux does not.  I'm stumped.
> 
> - Followed Bin's HOWTO, with 1.2 variations as in docs/Xeno-HOWTO
> 
> - /dev/hda1 is the ext3 root partition for a bootable native Linux
>   (debian woody)
> 
> - ext3 and ext2 drivers are both built into xenolinux (i.e. I'm using
>   the default xenolinux .config generated by 'make 
> menuconfig', and have
>   verified CONFIG_EXT3_FS=y)
> 
> Does anyone know why the (failed) modprobe attempt is 
> happening at all,
> since the ext3 driver is built in?
> 
> Steve
> 
> 
> root (hd0,0)
>  Filesystem type is ext2fs, partition type 0x83
> kernel /boot/xen.gz dom0_mem=80000 ser_baud=115200 noreboot 
> ignorebiostables
>    [Multiboot-elf, <0x100000:0x135354:0x1c2ec>, 
> shtab=0x252258, entry=0x100000]
> module /boot/xenolinux.gz root=/dev/hda1 ro 
>    [Multiboot-module @ 0x271000, 0x16992c bytes]
> 
>  __  __            _   ____              
>  \ \/ /___ _ __   / | |___ \    _ __ ___ 
>   \  // _ \ '_ \  | |   __) |__| '__/ __|
>   /  \  __/ | | | | |_ / __/|__| | | (__ 
>  /_/\_\___|_| |_| |_(_)_____|  |_|  \___|
>                                          
>  http://www.cl.cam.ac.uk/netos/xen
>  University of Cambridge Computer Laboratory
> 
>  Xen version 1.2-rc (stevegt@) (gcc version 3.0.4) Thu Jan 15 
> 20:18:59 PST 2004
> 
> Initialised all memory on a 320MB machine
> Reading BIOS drive-info tables at 0xfe761 and 0xfe771
> CPU0: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
> CPU caps: 0183f9ff 00000000 00000000 00000000
> Initialising domains
> Initialising schedulers
> Initializing CPU#0
> Detected 448.635 MHz processor.
> Local APIC disabled by BIOS -- reenabling.
> Found and enabled local APIC!
> enabled ExtINT on CPU#0
> ESR value before enabling vector: 00000000
> ESR value after enabling vector: 00000000
> Using local APIC timer interrupts.
> Calibrating APIC timer for CPU0...
> ..... CPU speed is 448.6109 MHz.
> ..... Bus speed is 99.6910 MHz.
> ..... bus_scale = 0x00006617
> ACT: Initialising Accurate timers
> Time init:
> .... System Time: 11910629ns
> .... cpu_freq:    00000000:1ABDA3D4
> .... scale:       00000002:3A9E617C
> .... Wall Clock:  1074300816s 0us
> Start schedulers
> PCI: PCI BIOS revision 2.10 entry at 0xfcaee, last bus=2
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
> Limiting direct PCI/PCI transfers.
> Intel(R) PRO/1000 Network Driver - version 5.2.16
> Copyright (c) 1999-2003 Intel Corporation.
> PCI: Found IRQ 11 for device 00:11.0
> PCI: Sharing IRQ 11 with 00:07.2
> PCI: Sharing IRQ 11 with 01:00.0
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:11.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xcc00. Vers LK1.1.16
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override 
> with idebus=xx
> PIIX4: IDE controller on PCI bus 00 dev 39
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
> hda: Maxtor 90640D4, ATA DISK drive
> hdb: Maxtor 52049U4, ATA DISK drive
> hdc: NEC CD-ROM DRIVE:28C, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hdc: ATAPI 32X CD-ROM drive, 128kB Cache
> Uniform CD-ROM driver Revision: 3.12
> hda: 12594960 sectors (6449 MB) w/256KiB Cache, 
> CHS=784/255/63, UDMA(33)
> hdb: 40020624 sectors (20491 MB) w/2048KiB Cache, 
> CHS=2491/255/63, UDMA(33)
> SCSI subsystem driver Revision: 1.00
> Red Hat/Adaptec aacraid driver (1.1.2 Jan 15 2004 20:21:59)
> Device eth0 opened and ready for use.
> DOM0: Guest OS virtual load address is c0000000
> DOM0: xen_console_init
> DOM0: Linux version 2.4.24-xeno (stevegt@pathfinder) (gcc 
> version 2.95.4 20011002 (Debian prerelease)) #1 Thu Jan 15 
> 22:17:22 PST 2004
> DOM0: On node 0 totalpages: 20000
> DOM0: zone(0): 4096 pages.
> DOM0: zone(1): 15904 pages.
> DOM0: zone(2): 0 pages.
> DOM0: Kernel command line: /boot/xenolinux.gz root=/dev/hda1 ro 
> DOM0: Initializing CPU#0
> DOM0: Xen reported: 448.635 MHz processor.
> DOM0: Console: colour VGA+ 80x25
> DOM0: Calibrating delay loop... 3670.01 BogoMIPS
> DOM0: Memory: 77304k/80000k available (1074k kernel code, 
> 2696k reserved, 309k data, 52k init, 0k highmem)
> DOM0: Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
> DOM0: Inode cache hash table entries: 8192 (order: 4, 65536 bytes)
> DOM0: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> DOM0: Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
> DOM0: Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
> DOM0: CPU: L1 I cache: 16K, L1 D cache: 16K
> DOM0: CPU: L2 cache: 512K
> DOM0: CPU: Intel Pentium II (Deschutes) stepping 02
> DOM0: POSIX conformance testing by UNIFIX
> DOM0: Linux NET4.0 for Linux 2.4
> DOM0: Based upon Swansea University Computer Society NET3.039
> DOM0: Initializing RT netlink socket
> DOM0: Starting kswapd
> DOM0: Journalled Block Device driver loaded
> DOM0: Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
> DOM0: Xeno console successfully installed
> DOM0: Successfully installed virtual firewall/router interface
> DOM0: Starting Xeno Balloon driver
> DOM0: Detected PS/2 Mouse Port.
> DOM0: pty: 256 Unix98 ptys configured
> DOM0: RAMDISK driver initialized: 16 RAM disks of 4096K size 
> 1024 blocksize
> DOM0: loop: loaded (max 8 devices)
> DOM0: NET4: Linux TCP/IP 1.0 for NET4.0
> DOM0: IP Protocols: ICMP, UDP, TCP
> DOM0: IP: routing cache hash table of 512 buckets, 4Kbytes
> DOM0: TCP: Hash tables configured (established 8192 bind 8192)
> DOM0: ip_conntrack version 2.1 (625 buckets, 5000 max) - 292 
> bytes per conntrack
> DOM0: ip_tables: (C) 2000-2002 Netfilter core team
> DOM0: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> DOM0: root_device_name = hda1
> DOM0: kmod: failed to exec /sbin/modprobe -s -k 
> block-major-3, errno = 2
> DOM0: VFS: Cannot open root device "hda1" or 03:01
> DOM0: Please append a correct "root=" boot option
> DOM0: Kernel panic: VFS: Unable to mount root fs on 03:01
> Domain 0 killed: rebooting machine!
> Reboot disabled on cmdline: require manual reset
> 
> 
> 
> 
> -- 
> Stephen G. Traugott  (KG6HDQ)
> UNIX/Linux Infrastructure Architect, TerraLuna LLC
> stevegt@xxxxxxxxxxxxx 
> http://www.stevegt.com -- http://Infrastructures.Org 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel