#Installing arch from a vm onto disk, cant see free space

74 messages · Page 1 of 1 (latest)

marble knoll
#

You see the 40GB of space, I cant find that on anything other than parted, I had to select the disk using parted only to see the 40gbs of space, is there any way to mark it so i can access it later onwards, would a flag work
(im trying to duel boot arch)
Also this is running in virtualbox, i added the disk image to my vm, like this:
https://unix.stackexchange.com/questions/67445/install-arch-linux-to-external-hard-disk-using-a-virtual-machine

I created the image using vbox commands, then i added it, so i have access to the whole disk and it can see 40gbs, I just need to be able to use it

tepid pike
marble knoll
tepid pike
marble knoll
#

like I dont think i can create partitions using it

#

or anything

#

if with cfdisk i cant really see it

#

Like only on parted its showing my sdb disk

#

so my end goal is to create arch

#

on the 40gbs of free space

#

my user and boot

tepid pike
marble knoll
#

"Are you trying to install Arch from a VM onto a physical drive?"

#

yes

tepid pike
marble knoll
#

to install arch

#

from a vm

#

onto a physical drive

#

it does not go deeper than that

tepid pike
# marble knoll I told you my end goal

Sorry for any frustration caused. I would suggest editing the original post and title to more accurately convey your goal, as I mentioned the XY problem because the original post was unclear regarding your goal of installing Arch Linux on a physical drive from within a virtual machine. Thanks for understanding.

left egretBOT
#

realspiderunderyourbed received a thank you cookie!

marble knoll
#

Installing arch from a vm onto disk, cant see free space

tepid pike
# marble knoll

This is the partition layout of /dev/sda, did you notice? In the original post, the parted output is from /dev/sdb

marble knoll
#

cfdisk only shows sda

tepid pike
#

As you can see there are two different discs, sda is 256GB and sdb is 32GB.

tepid pike
#

Can you post the output from

fdisk -l
marble knoll
#

Here is what windows shows

marble knoll
tepid pike
marble knoll
tepid pike
marble knoll
#

Ah that works

#

so is the free space

#

being treated as space between partitions

tepid pike
marble knoll
#

Thank you

marble knoll
#

Uhh

#

can I duelbooth without efi support @tepid pike

#

im testing inside virtualbox

#

idk if they just dont have it

#

in virtual machines

tepid pike
#

Virtual machine does not have access to your host nvram

marble knoll
#

maybe smthin from windows

#

i have uefi

#

ah

tepid pike
#

The fallback path is \EFI\boot\bootx64.efi

#

on the ESP

marble knoll
#

i can install as normal

#

right?

tepid pike
marble knoll
#

i mean

#

do i really have a choice

tepid pike
#

If you don't want to bother with boot loaders, the Linux kernel can boot without one.

marble knoll
#

i think i could set up libreboot if i wanted too

marble knoll
#

pressing f12 works

#

for me

tepid pike
# marble knoll yeah i rather that

You can use this mkinitcpio preset to generate a UKI to fallback path

# mkinitcpio preset file for the 'linux' package
# vi: ft=bash
# shellcheck disable=SC2034

### OPTIONS
_kernel=linux
_esp="/boot/efi"
###

_efi_dir="$_esp/efi/boot"
[[ ! -d "$_efi_dir" ]] && mkdir -p "$_efi_dir"

PRESETS=("default")
ALL_kver="/boot/vmlinuz-$_kernel"
ALL_microcode=(/boot/*-ucode.img)

default_image="/boot/initramfs-${_kernel}.img"
default_uki="$_esp/efi/boot/bootx64.efi"
default_options="--splash /usr/share/systemd/bootctl/splash-arch.bmp"
#

The system would boot regardless of the state of the nvram.

marble knoll
tepid pike
marble knoll