Recent XEN3_DOM0 begaviour

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

Hi,

I recently restored my earlier NetBSD/XEN setup on an old(ish) HP
EliteBook laptop; it all went rather well using xen packages for 4.11.
I then added a couple of disks to the system (one - the internal
mSATA, the other - on the tray replacing the DVD) with the intention
to use the second one as storage for XEN guests. I formatted this one
as GPT and added a couple of disks:
.....
# gpt show wd1

       18-12-30 - 18:23:55
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34       4062         Unused
       4096    4194304      1  GPT part - NetBSD swap
    4198400   67108864      2  GPT part - NetBSD FFSv1/FFSv2
   71307264  417089871         Unused
  488397135         32         Sec GPT table
  488397167          1         Sec GPT header

root@ymir:/home/xci
# dkctl wd1 listwedges

       18-12-30 - 18:24:06
/dev/rwd1: 2 wedges:
dk0: swap_03, 4194304 blocks at 4096, type: swap
dk1: root_03, 67108864 blocks at 4198400, type: ffs

root@ymir:/home/xci
# cat /usr/pkg/etc/xen/okn.cfg

       18-12-30 - 18:24:18
# -*- mode: python; -*-

name  = "okn"
kernel = "/netbsd-XEN3_DOMU-amd64-bar.gz"
vcpus = 2
memory = 2048
vif = [ 'mac=aa:bc:0e:d1:0e:09,bridge=bridge0' ]
disk = [ 'phy:/dev/dk1,0x1,w', 'phy:/dev/dk0,0x2,w' ]
....

It all works well, with the exception that when I reboot the host
under XEN using the usual

menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=2048M

the kernel decides that it has been booted from dk0, instead of wd0,
and I have to be present for the boot and point wd0 to be the boot
disk (BTW if I point at this moment to dk1/dk0 I am able to boot the
guest on bare metal using the same XEN3_DOM0 kernel... ).

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.

Or perhaps I have to modify XEN3_DOM0 ?


Chavdar


-- 
----