I'm SURE u didn't used someone else's config(8.7 / 10 I don't like green)

is caring if a config is original or not a thing that matters in the arch community?

Oh btw how do I make a login screen with UI In free bsd?

Personally i dont, i boot into text mode and then just type hyperland when i want a desktop

Oh btw how do I make a login screen with UI In free bsd?

hey so i was trying to install pip and i cant do it for some reason and here are the logs: # pkg install python Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-kmods repository catalogue... FreeBSD-kmods repository is up to date. All repositories are up to date. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: python: 3.11_3,2 [FreeBSD] python3: 3_4 [FreeBSD] Number of packages to be installed: 2 2 KiB to be downloaded. Proceed with this action? [y/N]: y [1/2] Fetching python3-3_4.pkg: 100% 1 KiB 1.2kB/s 00:01 [2/2] Fetching python-3.11_3,2.pkg: 100% 1 KiB 1.1kB/s 00:01 Checking integrity... done (0 conflicting) [1/2] Installing python3-3_4... [1/2] Extracting python3-3_4: 100% [2/2] Installing python-3.11_3,2... [2/2] Extracting python-3.11_3,2: 100% # pip zsh: command not found: pip # pkg install py38-pip Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating FreeBSD-kmods repository catalogue... FreeBSD-kmods repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'py38-pip' have been found in the repositories

And the last line , minus 1 GB

Out of space?

That's how df always works.

lol.. where is gnome ?

i need help, my freebsd 15 current vm is acting weird

Is this on zfs? Was compression enabled?

this is a ufs vm on a zfs compressed dataset yes but it still isn't a good thing if it starts to go in negative, this doesn't happen on a zfs vm or any linux fs vm

Did you find an explanation?

Or how to reproduce

i need help, my freebsd 15 current vm is acting weird

Try these to empty some space and figure out why. pkg clean rm -r /usr/src rm -r /usr/obj rm -r /usr/ports

If I understand your problem correctly, the issue is not the hypervisor. Your guest vm won't understand how much actually allocated under its disks.

a zfs vm or any linux fs vm calculates avail storage properly in the same environment

From the FreeBSD FAQ: 9.27. How is it possible for a partition to be more than 100% full? A portion of each UFS partition (8%, by default) is reserved for use by the operating system and the root user. df(1) does not count that space when calculating the Capacity column, so it can exceed 100%. Also, you will notice that the Blocks column is always greater than the sum of the Used and Avail columns, usually by a factor of 8%.

From the FreeBSD FAQ: 9.27. How is it possible for a partition to be more than 100% full? A portion of each UFS partition (8%, by default) is reserved for use by the operating system and the root user. df(1) does not count that space when calculating the Capacity column, so it can exceed 100%. Also, you will notice that the Blocks column is always greater than the sum of the Used and Avail columns, usually by a factor of 8%.

this causes problem with pkg, pkg doesn't understand that there is more storage available than reported to it and considers the system out of storage when avail reaches 0

The reserved space is not for pkg to use.

what i mean is do dd if=/dev/random of=/root/a.txt status=progress and dd will stop way after the avail storage has gone into negative do pkg install, pkg will fail as soon as avail storage is 0 i am sure there would be other examples but the pkg one is the most pronounced for me

pkg checks the available space. dd would not. This is reasonable behavior to me.

Because it couldn't write more, the kernel refuses to allow it to write. pkg asks about the available storage, while dd will continue to write until someone stops it.

or perhaps make the avail storage measure take the reservation in account