On Mon, Jan 20, 2025 at 04:39:02PM +0300, Antony Uspensky wrote:
If I remember correctly, installer offers MBR on BIOS environment, and
GPT on UEFI. Try run your vm as UEFI machine.
A.
That's interesting.
I guess vmrun.sh is 'BIOS' in this context.
The host runs other VMs for other OS guest
On Sat, 18 Jan 2025, void wrote:
Just checked - FreeBSD-14.2-RELEASE-amd64-disc1.iso installer still
automatically goes to MBR, one has to select GPT when installing auto-ufs.
Might be an idea to change the default to GPT if that's what FreeBSD would
like to promote? i have no idea how I'd do t
On Sat, Jan 18, 2025 at 06:15:25PM -0700, Warner Losh wrote:
Wierd. All the installs I've done in the last what feels like a decade have
defaulted to GPT. Are you installing onto media that's pre-formatted with MBR?
Nope. I install to an empty image created like this:
# truncate -s 64G vmimag
On Sat, Jan 18, 2025 at 4:44 PM void wrote:
> On Sat, Jan 18, 2025 at 01:18:20PM -0700, Warner Losh wrote:
>
> (snip)
>
> Just checked - FreeBSD-14.2-RELEASE-amd64-disc1.iso installer still
> automatically goes to MBR, one has to select GPT when installing auto-ufs.
>
> Might be an idea to change
On Sat, Jan 18, 2025 at 01:18:20PM -0700, Warner Losh wrote:
(snip)
Just checked - FreeBSD-14.2-RELEASE-amd64-disc1.iso installer still
automatically goes to MBR, one has to select GPT when installing auto-ufs.
Might be an idea to change the default to GPT if that's what FreeBSD would
like to p
Hi,
On Sat, 18 Jan 2025, at 20:18, Warner Losh wrote:
> It's expected.
>
> First, I'd skip using MBR. It's super limited, kinda hard and uses
> weird things. Using
> GPT will just work. MBR should generally only be used for legacy uses,
> but it should all
> work, once you do it correctly.
The
On Sat, Jan 18, 2025 at 10:49 AM void wrote:
> Hi,
>
> context is freebsd 14.2-releng vm (amd64) that has been upgraded with
> freebsd-update from 13.4.
>
> Decided to add another disk so invoking the vm looks like this:
>
> # sh vmrun.sh -c 4 -m 16G -t tap2 -d ./vm.img -d ./disk1.img vmname
>
>
Hi,
context is freebsd 14.2-releng vm (amd64) that has been upgraded with
freebsd-update from 13.4.
Decided to add another disk so invoking the vm looks like this:
# sh vmrun.sh -c 4 -m 16G -t tap2 -d ./vm.img -d ./disk1.img vmname
used gpart to create an MBR for disk1.img. tried to make sli
