which as

interesting: I also don't have the specific llvm-as

which as

it's the local one where ports go, not the system one

man.freebsd.org/cgi/man.cgi?query=llvm-as&sektion=1&format=html and if nothing this manpage should exist atleast, which doesn't as well

Poly

sup

for some reason my freebsd-14.2-release system doesn't have llvm-as and for some reason llvm19 is a runtime dependency of telegram-desktop, xorg and various xorg related packages, would anyone know what could be the reason

https://freebsd-current.freebsd.narkive.com/Ph3KgGjm/llvm-llvm-as-llvm-ld-and-so-on-not-contained-in-freebsd-core-contrib so it seems that just is what it is

i am trying to follow the handbook to build a custom kernel with MODULES_OVERRIDE, and when i specify acpi in MODULES_OVERRIDE make says "make: don't know how to make acpi. Stop"

i randomly had a thought (and i believe i am missing part of it) is that since freebsd has pretty solid backward compat(from what i have heard), why do some modules and ports like drm-kmod and vbox ones break on minor upgrades

I have 2 laptops and 2 desktops, different Intel and Radeon. I always update the system (freebsd-update & pkg) and I've never had any problems with it breaking. But before updating the packages, I always check for database updates. I've never had any problems.

I've been using it since 13, going through all the dot versions. I'm currently on 14.2 with zero problems.

since 14 I've been running pure wayland

Now, if you work with a system compiled via src and ports, it is natural that you will have to recompile the drm modules, as they have to read the headers, know the state of the system to adapt to the new kernel.

but working with the packages I never really faced any problems.

i randomly had a thought (and i believe i am missing part of it) is that since freebsd has pretty solid backward compat(from what i have heard), why do some modules and ports like drm-kmod and vbox ones break on minor upgrades

Don't know if it has anything to do with freebsd, but I've had vbox break on its own updates on the same versions of linux and windows

Don't know if it has anything to do with freebsd, but I've had vbox break on its own updates on the same versions of linux and windows

Use Bhyve and vm-bhyve manager

Use Bhyve and vm-bhyve manager

bhyve just suck and there is no point hiding at this point, there is no other way to get graphical display in a bhyve vm without using rdp/vnc on a single gpu system, many OSes straight up either refuse to boot or boot broken, some OSes in bhyve also refuse to take input

bhyve just suck and there is no point hiding at this point, there is no other way to get graphical display in a bhyve vm without using rdp/vnc on a single gpu system, many OSes straight up either refuse to boot or boot broken, some OSes in bhyve also refuse to take input

This is MASSIVE misinformation and skill issue

You *dont* need direct graphics. There is Windows RDP, X11 over SSH, Wayvnc

This is MASSIVE misinformation and skill issue

it's not a skill issue if other tools work ootb fine

it's not a skill issue if other tools work ootb fine

Bhyve has built in VNC, with vga graphics device

You *dont* need direct graphics. There is Windows RDP, X11 over SSH, Wayvnc

it's not called direct graphics, it's vga emu

it's not called direct graphics, it's vga emu

ye

Bhyve has built in VNC, with vga graphics device

vnc and vga emulation have a sky and ground difference

These is difference between vbox toy VMs and datacenter virtualization that Bhyve tailored to

while most OSes work ootb on vbox fine, in bhyve win7 doesn't have input ootb, chimera straight up refuses to boot, and many linux distros are unable to properly startx without manual intervention

bhyve is just time waste for me, and in the end when everything works fine, bhyve won't be able to have a smooth experience with low latency due to the inherent way vnc/rdp works

while most OSes work ootb on vbox fine, in bhyve win7 doesn't have input ootb, chimera straight up refuses to boot, and many linux distros are unable to properly startx without manual intervention

heck, even ghostbsd can't without either using scfb driver or other manual interventions, while in vbox i just have to start the vm and it would automatically and with a breeze drop me into the live gui env

while most OSes work ootb on vbox fine, in bhyve win7 doesn't have input ootb, chimera straight up refuses to boot, and many linux distros are unable to properly startx without manual intervention

I had Windows Server 2019 booting without issues

where did you saw windows server 2019 in any of my sentences, genuinely curious

I was also running win 7

you still don't deny the fact that input doesn't work ootb for it

you still don't deny the fact that input doesn't work ootb for it

It does work, use Bhyve VNC

It does work, use Bhyve VNC

that's what i used

that's what i used

Issue solved

isn't

not that it is the only issue and not that it is automatically and magically solved

I was also running OPNsense with PCI NIC passthru. I see no problem. You're making one

I would agree that Proxmox VE is better than Bhyve from administrative and performance viewpoint. And thats what Im using rn

i see a problem because you are talking about completely different things while my use cases are different

Ok

i see a problem because you are talking about completely different things while my use cases are different

actually there is more than one problem but anyways i guess it's clear now that bhyve sucks since there is no telling when it will randomly give an issue

anyways

Don't know if it has anything to do with freebsd, but I've had vbox break on its own updates on the same versions of linux and windows

i think the vbox issues on freebsd are different since the packages are compiled for one previous release from the latest and compiling from src solves the issues

i think the reason is because of the reliance of these on linuxulator and linuxkpi since we don't have backward compat for linux stuff

and if that indeed is the case then the backward compat problems will increase in the future with the reliance of more and more on linuxkpi unless we implement backward compat for those syscalls as well

Have you tried using bhyvemgr to see if it helps you with the VM management process?

or the BVCP Application (Bhyve Virtual-Machine Control Panel). ?

Have you tried using bhyvemgr to see if it helps you with the VM management process?

I tried that as well and the results were same with same aforementioned issues requiring the same fixes as that of bhyve/vm-bhyve

and i am not really surprised since i am not the only one affected by issues like these and after hearing things like bhyve was a friday night hobby project from college kids

and i am not really surprised since i am not the only one affected by issues like these and after hearing things like bhyve was a friday night hobby project from college kids

Yes you are the only one. Sorry bhyve is not for you. Please stick to Linux and KVM.

and i am not really surprised since i am not the only one affected by issues like these and after hearing things like bhyve was a friday night hobby project from college kids

Linux, too, was a hobby project from a college kid

It doesn't matter, as long as it's well developed (not making any comments, positive, negative or otherwise about bhyve)

Linux, too, was a hobby project from a college kid

the difference is that bhyve was compared to a one friday night project by college kids

I would agree that Proxmox VE is better than Bhyve from administrative and performance viewpoint. And thats what Im using rn

Showvl me your numbers about performance

Yes you are the only one. Sorry bhyve is not for you. Please stick to Linux and KVM.

anything you are basing that on? there are numerous similar forum and posts on other places that are similar to mine

anything you are basing that on? there are numerous similar forum and posts on other places that are similar to mine

Its obviously a skill issue. I see no logs, no errors, no debugging. Just bitching. I think a point and click solution with a paid support is a better solution for you.

Its obviously a skill issue. I see no logs, no errors, no debugging. Just bitching. I think a point and click solution with a paid support is a better solution for you.

a skill issue is something when someone isn't able to follow a simple or tedious but reasonable process, a skill issue isn't something when someone encounters unexpected or unnecessary issues and have solved them using unnecessary debugging, you should work on your english vocabulary :)

and as i said before there's no point of showing logs, errors if first you want to help since i have solved them myself second if you want to verify my statements which can be easily done through a quick internet search

a skill issue is something when someone isn't able to follow a simple or tedious but reasonable process, a skill issue isn't something when someone encounters unexpected or unnecessary issues and have solved them using unnecessary debugging, you should work on your english vocabulary :)

Skill is not following blindly a random top 10 Google hit. Work on you debugging skills or pay for the result.

and as i said before there's no point of showing logs, errors if first you want to help since i have solved them myself second if you want to verify my statements which can be easily done through a quick internet search

Good for you! Now go use proxmox

actually there is more than one problem but anyways i guess it's clear now that bhyve sucks since there is no telling when it will randomly give an issue

Now imagine yourself using VMware ESXi or Xen.

Showvl me your numbers about performance

I havent measured it. It was related both to realtek, and my clogged FreeBSD install. Im soon planning upgrade from minipc to proper workstation hardware so realtek wont be issue anymore. I already got HP FLR Intel NIC, just needs FlexLOM adapter

Skill is not following blindly a random top 10 Google hit. Work on you debugging skills or pay for the result.

where does conclusion even come from? who said i was following blindly some random articles rather then looking at logs?

Good for you! Now go use proxmox

i will use whatever i want

where does conclusion even come from? who said i was following blindly some random articles rather then looking at logs?

My assumption. Based on experience

My assumption. Based on experience

you should have experienced people crying for help after following random articles as well then

i will use whatever i want

Why using tech that suck, heh? You deserve better. Don't look bavk. Don't stop

you should have experienced people crying for help after following random articles as well then

I'm glad you recognized yourself. First step

I'm glad you recognized yourself. First step

show me where i cried for help

Let's relax the conversation a bit guys (:

I havent measured it. It was related both to realtek, and my clogged FreeBSD install. Im soon planning upgrade from minipc to proper workstation hardware so realtek wont be issue anymore. I already got HP FLR Intel NIC, just needs FlexLOM adapter

I will be also moving some VMs back to FreeBSD as guest os due to software delivery (freebsd ports are just better) and performance tunings

It is anecdotal that I have to look into freebsd ports to figure out build options on Linux, when building from sources

Let's relax the conversation a bit guys (:

alr, it's just is always funny to see people defend bhyve despite when they themselves don't have any reason for why bhyve is better

so, couldn't help myself from getting some laughs from seeing yet again

I havent measured it. It was related both to realtek, and my clogged FreeBSD install. Im soon planning upgrade from minipc to proper workstation hardware so realtek wont be issue anymore. I already got HP FLR Intel NIC, just needs FlexLOM adapter

someone said that I can just cut a little to make it fit in regular PCIe. IIRC FlexLOM has some pins mismatched from regular PCIe, good thing that there are now adapters

freebsd's networking stack and performance really is something else, i recently setup jellyfin server in freebsd running on an ancient 15 year old pc with dual core i5 650 and did a test where two clients were running on server sided hevc transcoding and the third client was doing client sided hevc transcoding, the amazing thing is even after two running two simultaneous hevc transcoding jobs, the server was still reasonably usable, in fact this telegram message is coming from that ancient pc jellyfin server while those transcoding jobs are happening, and for the third client, the playback was instant despite the router and hdd being of very bad quality, there was no network congestion, no buffering on the client or any of that sort of issue, there were stable network transfers at speed of 100 MB/s(not Mb/s), amazing stuff

alr, it's just is always funny to see people defend bhyve despite when they themselves don't have any reason for why bhyve is better

It don't have to be. That's the point. It's kids like you that don't have the skill to get it running and whine all the time. Take you pissing contest to Linux groups. It's not the first time I catch you talking shit. Enough is enough

It don't have to be. That's the point. It's kids like you that don't have the skill to get it running and whine all the time. Take you pissing contest to Linux groups. It's not the first time I catch you talking shit. Enough is enough

look man, i have no problem with you or anything else, what sucks for my usecase sucks, i followed the handbook and the vm-bhyve and freebsd wiki properly, and the issues were despite that, that is why i called them unexpected, and time efficiency is a thing, needing to debug unexpected issues when someone wants an vm up and running instantly isn't very time efficient, now this doesn't speak about industrial or other usecases, i won't be surprised if bhyve works almost the same as proxmox, xen or just plain kvm and some other userspace program for those and your usecases , it's just is always funny to see people say bhyve is better without mentioning how

look man, i have no problem with you or anything else, what sucks for my usecase sucks, i followed the handbook and the vm-bhyve and freebsd wiki properly, and the issues were despite that, that is why i called them unexpected, and time efficiency is a thing, needing to debug unexpected issues when someone wants an vm up and running instantly isn't very time efficient, now this doesn't speak about industrial or other usecases, i won't be surprised if bhyve works almost the same as proxmox, xen or just plain kvm and some other userspace program for those and your usecases , it's just is always funny to see people say bhyve is better without mentioning how

Run VMware ESXi.