thr3ads.net - Xen devel - [Xen-devel] Cannot open root device for dom0 [Jan 2004]

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

stevegt@TerraLuna.Org

2004-Jan-17 01:06 UTC

[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@monad.swb.de).
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@TerraLuna.Org 
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Williamson, Mark A

2004-Jan-17 04:04 UTC

head link

RE: [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@lists.sourceforge.net 
> [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of 
> stevegt@TerraLuna.Org
> Sent: 17 January 2004 01:07
> To: xen-devel@lists.sourceforge.net
> 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@monad.swb.de).
> 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@TerraLuna.Org 
> 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@lists.sourceforge.net
> 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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

stevegt@TerraLuna.Org

2004-Jan-17 04:12 UTC

head link

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

Mark Williamson and I seem to have gotten this sorted out -- while my
xenolinux build was based on a 1.2 pull as of about 24 hours ago, he
built another from a more recent pull (within the last hour or two?),
tossed it to me, and that boots.  I made no other changes, just dropped
his xeno12linux.gz into /boot and told grub to go get it.  I haven''t
tried another pull/build myself, but I would expect it would work as
well.  I did notice that Mark''s xenolinux was about 80k larger than
mine.

Moral of the story: there may have been something in 1.2 yesterday which
was breaking some block device operations.  If you hit this, do another
pull, mkbuildtree, make clean, etc.

Possible alternative explanation:  I''m using gcc 3.0.  Mark''s
using
3.2.2.  I''ll make sure to post here when I next rebuild, to let folks
know if the compiler was an issue.

Steve

On Fri, Jan 16, 2004 at 05:06:59PM -0800,  wrote:> 
> 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@monad.swb.de).
> 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@TerraLuna.Org 
> http://www.stevegt.com -- http://Infrastructures.Org 
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Ian Pratt

2004-Jan-17 09:23 UTC

head link

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

> Getting "Cannot open root device" on a pretty vanilla setup.  Xen
seems
> to see the device but xenolinux does not.  I''m stumped.
Hmm very odd. The messages coming out of Xen look fine, but you
should be getting ''partition check'' messages something like
these
earlier in the DOM0 boot:

DOM0: Starting Xeno Balloon driver
DOM0: Detected PS/2 Mouse Port.
DOM0: pty: 256 Unix98 ptys configured

DOM0: Partition check:
DOM0:  hda: hda1 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13
hda14 hda15 hda16 >
DOM0:  hdc: hdc1 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 hdc13
hdc14 hdc15 hdc16 hdc17 hdc18 hdc19 hdc20 hdc21 hdc22 >
DOM0: Skipping partition check on cdrom /dev/hdd

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
> Does anyone know why the (failed) modprobe attempt is happening at all,
> since the ext3 driver is built in?
It''s actually the xenolinux block device driver that it''s
trying
to modprobe.

I''m grasping at straws here, but please can you try the pre-built
binaries in the install/boot directory in the following tar ball:

 http://www.cl.cam.ac.uk/netos/xen/downloads/xeno-1.2.tar.gz


Ian


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Steven Hand

2004-Jan-17 11:32 UTC

head link

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

>> Does anyone know why the (failed) modprobe attempt is happening at all,
>> since the ext3 driver is built in?
>
>It''s actually the xenolinux block device driver that it''s
trying
>to modprobe.
Indeed; in more detail, the modprobe happened because major device 3 (ide0) 
was not registered with the blkdev layer; and this happened because 
something was screwed in the xenolinux ''probe'' (where at start
of day it
asks Xen about what devices exist, etc). Given that this code has all just
been rewritten (in Xen) to use red-black trees in place of a hash table so
that order is deterministic, I reckon that''s the culprit. 

Anyway, that''s just for info -- I believe it''s fixed now,
right?

cheers, 

S.

stevegt@TerraLuna.Org

2004-Jan-17 16:13 UTC

head link

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

On Sat, Jan 17, 2004 at 09:23:11AM +0000, Ian Pratt
wrote:> 
> > Getting "Cannot open root device" on a pretty vanilla setup.
Xen seems
> > to see the device but xenolinux does not.  I''m stumped.
> 
> I''m grasping at straws here, but please can you try the pre-built
> binaries in the install/boot directory in the following tar ball:
> 
>  http://www.cl.cam.ac.uk/netos/xen/downloads/xeno-1.2.tar.gz
I would expect the prebuilt xenolinux to work -- see my earlier note
about the one Mark gave me; it works too.  My guesstimate right now is a
compiler problem (gcc 3.0); I will let you know.

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

stevegt@TerraLuna.Org

2004-Jan-17 17:33 UTC

head link

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

Okay, I''ve done another pull and rebuilt xenolinux 1.2 with both gcc
2.95.4 and gcc 3.0.  Both of these boot dom0 and find hda just fine.
The only thing that''s changed is the code changed by the pull.

(Note that I''m talking about xenolinux only here -- I''m still
using the
gcc 3.0 Xen -- haven''t tried Xen with gcc 2.95 since I hit those
parsing
errors on Thursday.)

On Sat, Jan 17, 2004 at 11:32:30AM +0000, Steven Hand
wrote:> >> Does anyone know why the (failed) modprobe attempt is happening at
all,
> >> since the ext3 driver is built in?
> >
> >It''s actually the xenolinux block device driver that
it''s trying
> >to modprobe.
> 
> Indeed; in more detail, the modprobe happened because major device 3 (ide0)
> was not registered with the blkdev layer; and this happened because 
> something was screwed in the xenolinux ''probe'' (where at
start of day it
> asks Xen about what devices exist, etc). Given that this code has all just
> been rewritten (in Xen) to use red-black trees in place of a hash table so
> that order is deterministic, I reckon that''s the culprit. 
I suspect this was in fact the culprit -- possibly I grabbed the code
when it was in an intermediate state (Thursday evening Pacific time).
 > Anyway, that''s just for info -- I believe it''s fixed now,
right?
We can call this fixed.  Thanks everyone for your help.  

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org

Keir Fraser

2004-Jan-19 19:53 UTC

head link

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

> Indeed; in more detail, the modprobe happened because major device 3 (ide0)
> was not registered with the blkdev layer; and this happened because 
> something was screwed in the xenolinux ''probe'' (where at
start of day it
> asks Xen about what devices exist, etc). Given that this code has all just
> been rewritten (in Xen) to use red-black trees in place of a hash table so
> that order is deterministic, I reckon that''s the culprit. 
So little faith ;-)
> Anyway, that''s just for info -- I believe it''s fixed now,
right?
It is fixed now. The bug had actually been present for a long while --
GCC wasn''t being told that memory is "clobbered" across a
block_io_op
hypercall. The result is that Xenolinux didn''t always pick up updates
to the block_io_op_t struct after the hypercall (It assumed the
initial value it wrote in there before the hypercall was still
valid). 

This bug bit certain versions of GCC in certain situations. Nice!

 -- Keir

Xen devel - Jan 2004 - Cannot open root device for dom0

[Xen-devel] Cannot open root device for dom0

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

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

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

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

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

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

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