Re: Recent XEN3_DOM0 begaviour

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Thanks to both, that was it. Now I can switch between GENERIC and
XEN3_DOM0 without having to climb a grand total of thirteen steps to
get upstairs %^;}>...

DOMu's also autostart properly:

# xl list
Name                                     ID   Mem VCPUs  State   Time(s)
Domain-0                                0  2048     1         r-----      25.8
foo                                           1  1024     1
-b----       5.2
bar                                           2  2048     4
-b----      10.3
okn                                           3  2048     2
-b----       7.9



Happy New Year!

On Sun, 30 Dec 2018 at 22:03, Michael van Elst <mlelstv%serpens.de@localhost> wrote:
>
> ci4ic4%gmail.com@localhost (Chavdar Ivanov) writes:
>
> >Hi,
>
> >menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=2048M
>
> >Is there any means to force XEN3_DOMU to use wd0 as boot device? This
> >doesn't happen if I use the normal /netbsd kernel, it can see dk0/dk1
> >but proceeds to booot from wd0 by default.
>
> The xen kernel can't guess the boot disk and takes the first partition
> it finds, unless you tell it literally with, e.g.:
>
> menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc root=wd0a;multiboot /xen.gz dom0_mem=2048M
>
> For recent -current you can also specify a wedge by name with
>
>   root=wedge:name-of-the-wedge
>
> Greetings,
> --
> --
>                                 Michael van Elst
> Internet: mlelstv%serpens.de@localhost
>                                 "A potential Snark may lurk in every tree."



-- 
----