Updating src tree:
P src/build.sh
P src/distrib/sets/lists/xbase/mi
P src/distrib/sets/lists/xdebug/md.alpha
P src/distrib/sets/lists/xdebug/md.amd64
P src/distrib/sets/lists/xdebug/md.bebox
P src/distrib/sets/lists/xdebug/md.cats
P src/distrib/sets/lists/xdebug/md.i386
P src/distrib/sets/lists/x
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
ci4...@gmail.com (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
Chavdar Ivanov writes:
> 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 t
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 a
