Re: DragonFly on VirtualBox

2018-03-10 Thread Matthew Dillon
Though generally speaking we should probably be thinking about EFI-first
now, particularly with larger storage capacities causing mass confusion in
legacy-formatted drives.   I have several systems whos BIOSes implode
completely if *any* large-capacity drive (2TB or larger) is formatted with
fdisk, for example.  It doesn't even have to be the boot drive.  They
refuse to boot.

-Matt
‚Äč


Re: DragonFly on VirtualBox

2018-03-09 Thread Aaron LI
On Thu, 08 Mar 2018 23:58:35 -0500
Pierre Abbat  wrote:

> On Friday, 2 March 2018 20.54.08 EST Aaron LI wrote:
> > 
> > For EFI boot, you need to make sure that file "/EFI/boot/bootx64.efi" file
> > exists on your EFI partition (i.e., ad0s0), which is the default boot
> > code. If that file doesn't exist, you can copy "/boot/boot1.efi" over.
> 
> The file is there, but it's /EFI/BOOT/BOOTX64.EFI,
> not /EFI/boot/bootx64.efi.
> 

Since the EFI partition is FAT32, so the filename is case-insensitive.

As Peeter suggested, Legacy BIOS is sufficient for DFly on a virtual box.

I may try to install DFly on a VirtualBox machine with EFI, and will report
back.


Cheers,
-- 
Aaron


pgpV4vZdDR1p_.pgp
Description: OpenPGP digital signature


Re: DragonFly on VirtualBox

2018-03-09 Thread karu.pruun
On Fri, Mar 9, 2018 at 6:58 AM, Pierre Abbat  wrote:
>
> The file is there, but it's /EFI/BOOT/BOOTX64.EFI, not /EFI/boot/bootx64.efi.
>
> Is there a way in VirtualBox to install DragonFly without EFI?


Yes, BIOS boot seems to be the default setting. If you want EFI boot
you need to tick the box

Settings -> System -> Motherboard -> Extended features -> Enable EFI

or else your system won't boot with your EFI/GPT installation.

As a quick test, I installed DragonFly on Virtualbox, everything works fine.

You don't need EFI on Virtualbox though, it's handy when you have
multiple systems on the same disk. On virtual installations you
typically want one system per disk and then legacy BIOS boot is fine.

Cheers

Peeter

--


Re: DragonFly on VirtualBox

2018-03-08 Thread Pierre Abbat
On Friday, 2 March 2018 20.54.08 EST Aaron LI wrote:
> Hi Pierre,
> 
> You're using EFI with VirtualBox to boot the DFly guest, which I haven't
> tried.
> 
> For EFI boot, you need to make sure that file "/EFI/boot/bootx64.efi" file
> exists on your EFI partition (i.e., ad0s0), which is the default boot code.
> If that file doesn't exist, you can copy "/boot/boot1.efi" over.
> 
> You can also refer to the example installation script:
> /usr/share/examples/rconfig/hammer_uefi.sh
> 
> But I'm not sure whether VirtualBox's EFI implementation works with DFly's
> EFI boot loader...

The file is there, but it's /EFI/BOOT/BOOTX64.EFI, not /EFI/boot/bootx64.efi.

Is there a way in VirtualBox to install DragonFly without EFI?

Pierre
-- 
The Black Garden on the Mountain is not on the Black Mountain.



Re: DragonFly on VirtualBox

2018-03-02 Thread Aaron LI
On Fri, 02 Mar 2018 14:32:47 -0500
Pierre Abbat  wrote:
> 
> fdisk -B results in "Missing operating system".
> 
> The disk is laid out like this, according to file:
> ad0: boot sector, pt 1 type ee
> ad0s0: boot sector, 32-bit FAT, label "EFI"
> ad0s1: boot sector
> ad0s1a: FFS /boot
> ad0s1b: swap
> ad0s1d: HAMMER /
> 

Hi Pierre,

You're using EFI with VirtualBox to boot the DFly guest, which I haven't
tried.

For EFI boot, you need to make sure that file "/EFI/boot/bootx64.efi" file
exists on your EFI partition (i.e., ad0s0), which is the default boot code.
If that file doesn't exist, you can copy "/boot/boot1.efi" over.

You can also refer to the example installation script:
/usr/share/examples/rconfig/hammer_uefi.sh

But I'm not sure whether VirtualBox's EFI implementation works with DFly's
EFI boot loader...


Cheers,
-- 
Aaron


pgpWKIzMav4_e.pgp
Description: OpenPGP digital signature


Re: DragonFly on VirtualBox

2018-03-02 Thread Pierre Abbat
On Friday, 2 March 2018 00.24.48 EST Aaron LI wrote:
> I've installed DragonFly BSD (4.8, 5.0, and master) in VirtualBox (on Debian
> Linux) using the installer, and all work well.
> 
> Maybe you can try:
> 
> 1. Boot into DFly through the ISO
> 2. Find the disk into which DFly is installed, e.g., "ad0" (for me) or "da0"
> 3. Install the boot code: fdisk -B /dev/ad0 (change to your disk)
>(According to the installer, "fdisk -B" is used instead of "boot0cfg",
>which installs the /non-interactive/ boot code as described in the
>EXAMPLES in boot0cfg(8).
>Could somebody explain in more detail about these two boot codes??)
> 4. Try reboot from the disk (you may need adjust the booting orders)
> 
> Hope this helps solve your problem.

fdisk -B results in "Missing operating system".

The disk is laid out like this, according to file:
ad0: boot sector, pt 1 type ee
ad0s0: boot sector, 32-bit FAT, label "EFI"
ad0s1: boot sector
ad0s1a: FFS /boot
ad0s1b: swap
ad0s1d: HAMMER /

Pierre
-- 
ve ka'a ro klaji la .romas. se jmaji



Re: DragonFly on VirtualBox

2018-03-01 Thread Aaron LI
On Thu, 01 Mar 2018 21:14:21 -0500
Pierre Abbat  wrote:

> On my new laptop (which came with Linux) I made two VirtualBoxen and
> installed DragonFly on one and OpenBSD on the other. The OpenBSD install
> worked fine. The DragonFly came up with "Missing operating system" or the
> like. I rebooted it from the ISO file and ran boot0cfg. It looks like all
> files are installed, but when I rebooted it this time, it came up "F1 ??"
> and wouldn't boot. I think it's supposed to say "F1 DF/BSD". Did I skip a
> step, or am I missing a file or something?
> 

Hi Pierre,

I've installed DragonFly BSD (4.8, 5.0, and master) in VirtualBox (on Debian
Linux) using the installer, and all work well.

Maybe you can try:

1. Boot into DFly through the ISO
2. Find the disk into which DFly is installed, e.g., "ad0" (for me) or "da0"
3. Install the boot code: fdisk -B /dev/ad0 (change to your disk)
   (According to the installer, "fdisk -B" is used instead of "boot0cfg",
   which installs the /non-interactive/ boot code as described in the
   EXAMPLES in boot0cfg(8).
   Could somebody explain in more detail about these two boot codes??)
4. Try reboot from the disk (you may need adjust the booting orders)

Hope this helps solve your problem.


Cheers,
-- 
Aaron


pgpjPF9Fckso6.pgp
Description: OpenPGP digital signature