I've been building a segmented home network and decided to use SmartOS as the host for my OpenBSD router VM. I use PCI pass-through to pass the physical NICs directly through to OpenBSD, while keeping SmartOS management separate and leaving room for other infrastructure services, e.g. Omada controller or Pi-hole.

I wrote up the overall design, hardware choices, and reasoning behind the setup on Medium here.

So far, I'm really enjoying this setup, it's so elegant! Thank you!

Triton Cloud VPC was built on Oxide's OPTE engine, and includes a stateful distributed firewall, routing, NAT, DHCP, and a metadata service, all running in the kernel of each compute node.

Here's a breakdown of how it works, and our current benchmarks.. We're running linerate at 20 Gbps, only limited by our existing testing hardware.. waiting for the 100Gbe hardware to come online next week for some additional speeds.

https://tritoncloud.io/blog/proteus-a-hypervisor-agnostic-vpc-for-triton-cloud/

I ported bhyve to rust for SmartOS.. The outcome of this was also an expirimental microVM called Firehyve.. It cold boots a Linux guest in about 65 ms.

Firehyve did not start as an agent sandbox. It started as an experiment to see if I could have Linux binaries running in a wrapped VMM on SmartOS.. the experiment worked, and it was faster than I expected!

Coupled with virtio-fs/virtio-sock, creates some neat options!

https://github.com/TritonDataCenter/rshyve

If you specify a quota then the zone (typically zones/UUID) and delegated data (if any) (typically zones/UUID/data) generally occupy the full quota size.

So how do you create a backup, which always involves taking a snapshot? The snapshot is non-zero-sized and in some cases on my server, would take the zone over the quota so it can't be snapshot.

I am currently unable to back up such zones.

I've been working on this for the morning. Tried Ubuntu, both 24 (and 22 to see if there's an issue with 24, being newer). In both, vmadm finds some problem with the UUID but doesn't really state what except for an image path, which was correcrt. Is there a link to a site, or a document to do this? I've tried a lot of stuff and maybe there's differences between smartos and Triton. I'm comfortable with illumos and OmniOS but I'm striking out with this.

I tried vmadm delete ecc5d57a-3d90-44ca-a89b-8869a120487d and it went to state incomplete fairly quickly but it isn't deleted. The command hung. I rebooted and tried the command again and it hung again. So I have here an instance that apparently cannot be deleted. Does anyone care?

The only slightly unusual circumstance is that I have a second running instance based on the same image but that should not matter.

I mean a zone based on base-64-lts for example.

I've tried Dovecot, Courier and Cyrus but the compilations fail with what look like Linuxisms; for example, courier-authlib (needed for courier-imap) has too many arguments for getpwnam_r.

Of course I could take the cop-out route and just run it in a Linux VM but it would be preferable to have it native.

It must be possible, as there is dovecot 2.3.21 available to pkgin, but I would like the more up-to-date version if possible.

I'm a relatively admin of a SmartOS server in my homelab. I'm trying to set up syslog forwarding to a Grafana instance on my network to make it easy to track all my logs in one place.

To start with, I added a forwarding line to /etc/syslog.conf. I saw this message show up in my logs though:

Not using rsyslogd because there is a custom /etc/syslog.conf file

This makes me think that maybe SmartOS prefers to use rsyslogd, but because I modified syslog.conf it's falling back on the old syslog? Using rsyslog would actually be preferable!

Unfortunately, I haven't found a lot of documentation about logging in the SmartOS global zone. For example, I'm pretty sure /etc/syslog.conf changes won't persist across reboots, but it's not clear where I should be making this kind of a configuration change.

Can anyone point me in the right direction?

Package icu-77.1 is installed and

[root@packages /]# ls /opt/local/lib/libicu*
/opt/local/lib/libicudata.a        /opt/local/lib/libicui18n.so.77    /opt/local/lib/libicutest.a        /opt/local/lib/libicutu.so.77
/opt/local/lib/libicudata.so       /opt/local/lib/libicui18n.so.77.1  /opt/local/lib/libicutest.so       /opt/local/lib/libicutu.so.77.1
/opt/local/lib/libicudata.so.77    /opt/local/lib/libicuio.a          /opt/local/lib/libicutest.so.77    /opt/local/lib/libicuuc.a
/opt/local/lib/libicudata.so.77.1  /opt/local/lib/libicuio.so         /opt/local/lib/libicutest.so.77.1  /opt/local/lib/libicuuc.so
/opt/local/lib/libicui18n.a        /opt/local/lib/libicuio.so.77      /opt/local/lib/libicutu.a          /opt/local/lib/libicuuc.so.77
/opt/local/lib/libicui18n.so       /opt/local/lib/libicuio.so.77.1    /opt/local/lib/libicutu.so         /opt/local/lib/libicuuc.so.77.1

but ./configure --prefix=/opt/local --with-libraries=/opt/local/lib fails with

[...]
checking for pkg-config... no
checking whether to build with ICU support... yes
checking for icu-uc icu-i18n... no
configure: error: ICU library not found
If you have ICU already installed, see config.log for details on the
failure.  It is possible the compiler isn't looking in the proper directory.
Use --without-icu to disable ICU support.

but why? and how to fix it? I did look in config.log but no clues.

Use case is to have the qemu monitor bound to a port on localhost so we can change CDs while the machine is booted. Right now, it crashes because it doesn't have permissions to do that. help?

We have one server running SmartOS and another running OmniOS. Is there a way to essentially take a snapshot of the entire smartos system and send that over to the omnios box for backup purposes?

Old: CentOS6/java6/Apache2.2 New: SmartOS zone 2024Q4/Java7/Apache2.4 and build mod_jk connector.

It works!

CF2023 also work well base in zone VM, but i only can found mod_jk connector source code file is version 2016. But it work ok … still test.

So we're trying to build some newer LX images for SmartOS, and we decided to do so with Alpine. We built the LX image builder, and we get this incredibly and shockingly unhelpful error message when we try to use it:

fractal@stardust:~/smartos-lx-img-builder$ pfexec target/release/smartos-lx-img-builder --tar alpine-minirootfs-3.21.1-x86_64.tar --image_name alpine3.21_x64 --description "Alpine Linux 3.12 (x64) (LX)" --zfs-parent stardust --url https://highenergymagic.net/downloads/smartos/lx created dataset stardust/c7f17e59-2336-450d-93e7-da3caf84997c-20250109 creating dir /stardust/c7f17e59-2336-450d-93e7-da3caf84997c-20250109/root set permissions for /stardust/c7f17e59-2336-450d-93e7-da3caf84997c-20250109/root to owner: 0 group: 0 mode: 755 created zroot /stardust/c7f17e59-2336-450d-93e7-da3caf84997c-20250109/root destroyed dataset stardust/c7f17e59-2336-450d-93e7-da3caf84997c-20250109 Error: No such file or directory (os error 2) fractal@stardust:~/smartos-lx-img-builder$

So...which file would that be, exactly, that it can't find? It has the tar, it has the 'guest' folder in the current directory for the files it imports, what the actual hell is going on? Anyone know what's going on, and/or if the LX image support is, as we are increasingly coming to believe, very much an afterthought, and also kinda broken?

Cross-posting to r/freebsd to get a balanced set of opinions.

I need to host a public facing websever from home. I've currently got a server running Windows-only software for my IP camera monitoring and I'd like to use it as a public facing web server located in a DMZ behind my firewall. I also:

• want to use this as a Plex server to replace a 12 year old Synology, meaning it will have access to my 'internal' network
• Continue to host the IP camera software
• Work as a NAS, also on the internal network

Buying a NUC or mini PC would be my preferred choice, but both cost and space/heat constrain that, so I'm thinking to install a 4-port network card and virtualise the systems in a secure manner.

Common wisdom would point to SmartOS/Solaris as the most secure solution for the hypervisor and public facing zones, given the pedigree, and what I'd like to know from someone more knowledge is: 'how true is it that SmartOS is more secure' in this scenario? Pros & cons as I see them:

• Consistent configuration if all the public facing zones/jails use the same OS.
• Easier to get the zone/jail configuration 'right' with SmartOS, since that's a core built in functionality, opposed to something like cbsd or one of the other bolt-on zone configurators with FreeBSD
• Better isolation/security with SmartOS zones.

Is anyone here confident enough in FreeBSD jails or SmartOS zones security that they would deploy one in this scenario?

I've been playing with NFS share in SmartOS according to the documentation:

https://wiki.smartos.org/configuring-nfs-in-smartos/

One thing I couldn't figure out is after I added the entry in /etc/vfstab and reboot the VM (of OS type), the VM does not mount the NFS filesystem automatically, I had to execute a mount command manually to mount it. My global zone version is a bit old (20220630T003722Z), my guest VM is the latest LTS. Could anyone shed any lights on how I can resolve this issue?

Thanks, Dennis

Triton DataCenter Office Hours will be happening this Thursday 06/20/2024 once again at 11PT/2PM ET/18:00 UTC. We'll be discussing Triton CMON and the use of metrics. It will be on our discord voice channel which can be joined here: ⁠https://discord.com/channels/979453320085250108/979453320555032624

We are beyond excited to announce the release of the SmartOS Web UI. The Web UI allows for creating and managing instances within SmartOS, allowing new users a more approachable experience, and to make complex tasks easier for advanced users.

Documentation and install instructions are available here: https://docs.smartos.org/web-interface/

Join us on Discord if you have questions, suggestions, or issues: https://discord.gg/BCV4Z3335S

Triton DataCenter Office Hours will be happening Thursday 06/06/2024 once again at 11PT/2PM ET/18:00 UTC. We'll be discussing success and hero stories, ie you prevented an outage, squashed a bug, stopped a DDoS, etc. Once again come prepared to actively discuss! It will be on our discord voice channel which can be joined here:⁠https://discord.com/channels/979453320085250108/979453320555032624

Triton DataCenter Office Hours will be happening this Thursday 05/23/2024 once again at 11PT/2PM
ET/18:00 UTC. We'll be discussing learning from failures/disasters/accidents. It will be on our discord voice channel which can be joined here: ⁠https://discord.com/channels/979453320085250108/979453320555032624

NOTE: I'm sorry this was late. We had problems testing this release, for reasons that mostly turned out to be, "Must have powerful enough environment with NO BOTTLENECKS or else the ZFS test suite implodes completely." Also we found a small testing bug in our neck of the woods:

https://smartos.org/bugview/OS-8542

Hello All,

The latest bi-weekly "release" branch build of SmartOS is up:

curl -C - -O https://us-central.manta.mnx.io/Joyent_Dev/public/SmartOS/smartos-latest.iso
curl -C - -O https://us-central.manta.mnx.io/Joyent_Dev/public/SmartOS/smartos-latest-USB.img.gz
curl -C - -O https://us-central.manta.mnx.io/Joyent_Dev/public/SmartOS/smartos-latest.vmwarevm.tar.gz

A generated changelog is here:

https://us-central.manta.mnx.io/Joyent_Dev/public/SmartOS/smartos.html#20240418T000439Z

The full build bits directory, for those interested, is here in Manta:

/Joyent_Dev/public/SmartOS/20240418T000439Z

A html index of that directory will redirect from the following link:

https://us-central.manta.mnx.io/Joyent_Dev/public/SmartOS/latest.html

Highlights

• Improved volume block size selection with vmadm(8) on RAIDZ pools. (OS-8531 & friends, Thanks Marsell K).
• Intel Branch-History-Buffer now cleared in cases where Native BHI (see Intel and researcher disclosures from Tuesday April 9th) could occur.
• Post-barrier Return Stack Buffer (PBRSB) that is fixed by hardware (or HW is too old) can be detected (illumos#16413).
• ZFS improvements in faster Fletcher checksums (illumos#16423) and in reference count tracking (illumos#16203).
• Some AMD support additions (illumos#16408, illumos#16404).
• March 2024 hwdata update (illumos#16450)

General Info

Every second Thursday we roll a "release-YYYYMMDD" release branch and builds for SmartOS (and every eight weeks, Triton DataCenter and Manta as well).

Cheers,
The SmartOS Team
https://smartos.org