GhostBSD IRC channel?

vimanuelt

I was online at 8:30 PM ADT / 23:30 UTC. I posted for comments, but it seemed only a few were around; mostly news hounds waiting for a morsel, not a conversation.

zephyrus

vimanuelt
I am sorry (really am), I screwed up. When I posted a few days ago, I completely forgot that we were invited for a Thanksgiving BBQ. f
Let's pick up the pieces and salvage this. I will drip in next Sunday at 4:30 PM Pacific Time / 8:30 PM your time.

brianthehughes

True IRC legends idle endlessly.

zephyrus

brianthehughes
Indeed!

I need to pick your brain. During our chat, you mentioned virtual machines. If you happen to run GhostBSD also as a VM, do you have network access? For some reason, I installed Virtmanager on CachyOS and there are issues with an inactive network. I also struggle to get a better then 1280x720 resolution.

If you have time tomorrow (same time as last time), we could have a quick IRC chat?

brianthehughes

zephyrus
In VirtualBox, I generally enable two network interfaces.

Host Only Network 192.168.56.*
This one provides access from the Host to the Machine but also between guest virtual machines on the host.
NAT 10.0.3.*
This one provides Internet to the guest virtual machines. In essence the Host acts like a router for the guest VMs.
Bridging -
I experimented with Bridging the guest and host network to enable my LAN addressing to show up in the guest virtual machine network but found performance to be inconsistent.

A core motivation was to NOT manually configure networking on guest VMs but utilize DHCP. With an array of brian@brian-ghostbsd machines for the series of testing VMs I recognized that enabling the guests to show up in my primary LAN did not add value to existing monitoring and actually added a noisy mess of VMs into the 30-50 client devices that the home/property already supports.

vimanuelt

Yes, I see their is a need for a new feature. You can submit a feature request to have it implemented. ghostbsd/issuesissues/new?assignees=&labels=feature&template=feature_request.yaml

# Treat virt-manager as QEMU. KVM vendor covers QEMU family.
  if [ "$hv" = "KVM" ] || [ "$gpu" = "qemu" ]; then
    setup_qemu
  else
    case "$gpu" in
      intel)  setup_intel ;;
      amd)    setup_amd ;;
      nvidia) setup_nvidia ;;
      scfb)   setup_scfb ;;
      unknown) setup_vesa ;;
      *) setup_vesa ;;
    esac
  fi

zephyrus

Clever detection logic. This one deserves a pull request plaque.

vimanuelt

s/their/there
:-)

zephyrus

Thank you @brianthehughes

Two days ago, I did the unthinkable and installed W11 Pro on my laptop. Then Virtualbox, and GhostBSD. No issues. I can even go fullscreen (3440 x 1440) and drag content from host > guest.

If you have time, we can chat some more about "this and that" in the ghost hangout 😉

GNU2BSD

I lurk and occasionally chat on some of the Linux and tech channels on Libera anyway, so I'll try to join next time you guys are active.

vimanuelt

Maybe having core hours would work well.
Daily: 0700 to 1100 UTC and 2200 to 0200 UTC.

Setting up a web bot for GhostBSD might be a nice idea, too.
If you missed a conversation, you can read the irc history.

zephyrus

vimanuelt
Love the "0700 to 1100 UTC" suggestion (midnight - 4AM for me). 🙂

« Previous Page