Re: Dom0 - fatal page fault in supervisor mode when root FS is on a slice of disklabel lying on a raidframe device, built up from two GPT wedges

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Thu, Aug 23, 2018 at 01:11:28PM +0200, Matthias Petermann wrote:
> Am 23.08.2018 um 13:01 schrieb Manuel Bouyer:
> > On Thu, Aug 23, 2018 at 12:58:32PM +0200, Matthias Petermann wrote:
> > > Do you have pointer for me where the root= argument is documented?
> > 
> > It used to be in the howto, I didn't check recently.
> > 
> > > I just tried with this boot.cfg line:
> > > 
> > > menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz
> > > dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin root=/dev/raid0a
> > 
> > should be:
> > menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc root=raid0a;multiboot /xen.gz dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin
> > 
> 
> That was it! Thank you - you saved my day! The system is booting now and I'm
> looking forward to setting up the VMs. I owe you a drink.

Actually, if you can set up a serial console I'm still interested in
the details of the panic, and a stack trace. It would be better to have the
kernel ask for its root filesystem than panic ...

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