On Wed, Jun 14, 2006 at 11:45:00AM +0000, Christoph_Egger@gmx.de wrote:
> >Number:         33728
> >Category:       kern
> >Synopsis:       Trouble with /dev/ld*
> >Confidential:   no
> >Severity:       serious
> >Priority:       high
> >Responsible:    kern-bug-people
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   net
> >Arrival-Date:   Wed Jun 14 11:45:00 +0000 2006
> >Originator:     Christoph Egger
> >Release:        NetBSD 3.0
> >Organization:
> >Environment:
> NetBSD  3.0 NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005  builds@works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386
> >Description:
> 
> 
> I want to install a Xen Dom0. Following the instructions on the
> NetBSD/Xen Howto I want to install the bootmanager GRUB.
> 
> grub-install /dev/rld0d  says:
> /dev/rld0d does not have any corresponding BIOS drive.
> 
> I created my own /grub/device.map and retried:
> 
> echo "(ld0)  /dev/rld0d" >/grub/device.map

You want:
(hd0)   /dev/rld0d


> 
> Instead of reintroducing new disktypes you should make it
> accessable as SCSI. The LSI RAID Controller has SCSI Disks, why should
> they be accessed different?

Because you're not accessing SCSI disks (and some LSI megaraid have PATA
or SATA drives), but a virtual drive presented by the firmware adapter.
translating requests to SCSI commands, to then decode these SCSI commands
and translate them to the LSI firmware interface would just be a waste
of CPU cycle (and could eventually lead to less efficient usage of the
LSI capabilities). RAID volumes from others hardware RAID adapters shows
up as ld too.

grub should be fixed.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--