libre #smartos

6 Sep 2022

SmartOS -- A Modern, Open Source, Datacenter Operating System | smartos.org | github.com/TritonDataCenter/smartos-live | github.com/TritonDataCenter/triton | Security -- TritonDataCenter.com/security-issues | Channel logs - log.omnios.org/smartos

• 04:26
  nikolam
  I always wondered why normal terminal options, like using arrow to go to the left (in ftp for example) does not work under SmartOS console (or screen session for that matter)
• 04:27
  nikolam
  Or how delete key does not work as expected etc
• 04:28
  nikolam
  arrow up gives ^[[A etc.
• 04:32
  nikolam
  Pageup, Pagedown don't work too..
• 06:09
  tsoome
  it is not built to support it.
• 06:10
  tsoome
  I did add tftp to use libtecla for command line editing, but rest of those could have some love too
• 06:11
  tsoome
  I was just needing to test tftp client and got tired of its bad command line:D
• 14:57
  bahamat
  tsoome: You can use rlwrap for those.
• 14:58
  b-rex
  is bhyve objectively better than kvm in terms of performance?
• 14:58
  bahamat
  b-rex: It depends!
• 14:58
  b-rex
  i want to run linux and opnsense VMs
• 14:59
  bahamat
  In most cases yes, but there are some people who have stated that their workload happens to perform better with kvm.
• 14:59
  bahamat
  You're probably better off with bhyve.
• 14:59
  b-rex
  so far i haven't been able to get opnsense to work with bhyve
• 14:59
  bahamat
  What is it about it that doesn't work?
• 14:59
  bahamat
  Does it boot?
• 14:59
  b-rex
  got it to boot and install after a lot of experimenting.
• 15:00
  b-rex
  one second i will paste the config that worked for install
• 15:00
  b-rex
  (not in the channel)
• 15:01
  b-rex
  dpaste.com/3YC45LQBS
• 15:02
  b-rex
  i'm having to use the usb image because i could not figure out how to boot the iso under bhyve
• 15:03
  b-rex
  this works and it is able to install. then i update the disks to make the 32GB disk bootable. it boots but is unable to mount /dev/gpt/root
• 15:03
  bahamat
  Sounds like the boot loader didn't get set up properly.
• 15:04
  b-rex
  i tried entering in the device names manually in the mountroot and it's like they're not there
• 15:05
  b-rex
  so there's this egg to crack. and then there's the debian 11 under bhyve egg to crack (no network interface gets detected)
• 15:05
  bahamat
  it might help to explicitly assign the pci_slot to your disks
• 15:05
  bahamat
  that way they won't be changing between boots.
• 15:06
  bahamat
  I'm not 100% sure on this, but I think that maybe the devices are getting re-enumerated because you removed the installer
• 15:07
  b-rex
  yes i suspect that's what it is
• 15:07
  b-rex
  trying that real quick
• 15:12
  » b-rex crosses fingers
• 15:20
  b-rex
  bahamat: yep that was it :)
• 15:21
  bahamat
  Glad to hear!
• 15:22
  bahamat
  b-rex: FWIW, Triton automatically sets the pci_slot on bhyve. But then again, it's also not as easy to boot from an installer image then switch the boot disk later.
• 15:23
  b-rex
  ok now... i found some stuff about older debians not having any network interface detected under bhyve
• 15:23
  b-rex
  some of the posts claim that it was fixed in new debians, and that doesn't appear to be the case
• 15:24
  b-rex
  if i simply switch to a rockylinux iso, everything works fine - thus i know that my config is partially correct
• 15:24
  b-rex
  but i'd really like to figure out what about my config makes debian have no net
• 15:25
  b-rex
  some of them said use the e1000 model - that did not work
• 15:26
  bahamat
  Images need to have cloud-init to auto detect networking. And it's possible some older versions of cloud-init don't support SmartOS metadata properly
• 15:33
  b-rex
  cloud-init will detect hardware that isn't there?
• 15:33
  b-rex
  the vm doesn't see a nic at all
• 15:52
  jfqd1
  jperkin: sorry for the delay, here is the link to the pkgin.db from the machine with the zabbix-4.0.24nb7 install issues related to python310: nc2.qutic.com/s/JegmR3Qa6ZHJnoT
• 18:38
  Smithx10
  There should be a thread on the internet called
• 18:38
  Smithx10
  "Trying to interface or communicate with the networking team"
• 18:39
  Smithx10
  aka... tales from the crypt
• 18:39
  Smithx10
  aka... mission impossible
• 18:52
  danmcd
  Distinct networking and systems teams are an organizational failure. Fight me. (It's why Sun merged the OS gate and the Networking gate into ON back in 1990-before-I-got-there.)
• 19:14
  jbk
  the first rule of the networking team is that the network is never responsible, even when it is
• 19:14
  jbk
  (very much like mainframes)
• 19:29
  danmcd
  <sigh>
• 20:00
  sjorge
  jbk: oof that sounds very relatable
• 20:12
  nbjoerg
  danmcd: almost as useful as a backup group having no overlap with the systems team :)
• 21:21
  jbk
  sjorge: my favorite memory of that was when two systems couldn't talk to each other, they were on two different vlans, each vlan only had 1 gateway (i.e. each system only needed a default route)
• 21:21
  jbk
  they could reach other stuff on other vlans
• 21:21
  jbk
  but it was a 'static arp problem on my server'
• 21:22
  jbk
  i was like '.... that's not how ARP works'
• 23:26
  tozhu
  hello all, is there any tools / template to monitor Triton/CN/SmartOS? with Prometheus? a big thanks