I wonder what is the best way to migrate a Proxmox LXC to an OmniOS LX zone? Just rsync the root file system?

How does network configuration work for a LX zone? The Linux file system does not have any files related to it (e.g. Alpine Linux: no /etc/network/interfaces and no /etc/resolv.conf). The LXC containers have these files. Still the LX zone comes up with the IP, that was set during creation.

lx zones are in SmartOS, OmniOSCE (don't know about Oxide Helios and Openindiana) and SmartOS hypervisor has 'vmadm get ' to show active VM (lx zone) settings and ' vmadm update ' to update it form .json

zoneadm and zonecfg are for setting and updating zones if there is no vmadm

zonecfg has network add, see man. vmadm create uses .json definition where network also is (SmartOS wiki docs)

Hey everyone, I'm back with another question! Can you point me to some documentation about the utimesys syscall? I noticed that illumos doesn't have futimes and utimesat syscalls but there is utimesys and some comments bellow saying that it behaves as futimes or utimesat depending of the first parameter of the syscall

(github.com/illumos/illumos-gate/blo…r/src/uts/common/sys/syscall.h#L284), but I couldn't find any more information about this syscall online

GrayJack - the documented interface between userland and the kernel in illumos is libc, the syscalls that libc uses are effectively an implementation detail that should not generally be used directly. illumos has both futimes() and utimesat() - they're both documented in this manual illumos.org/man/2/futimes

*futimesat()/utimensat()

@richlowe mailed, pardon latency.

andyf - Yes, I agree, but I'm implementing a libc, for fun and learning, that was the reason of my question. I'm doing so I can both learn more about structuring a essential part of C lang and Unix interface as well learn more about the internals, and decision choices of the many UNIX/UNIX-like OS

you can search for stuff using src.illumos.org

so you can use that to see how those are implemented in terms of specific syscalls

e.g. src.illumos.org/source/xref/illumos…libc/port/sys/utimesys.c?r=2829495d

jbk - Thanks for the links, that helps a lot!

note that for some reason, it sometimes appends an extra '?r=......' to the url and you get a blank output

(some bug with opengrok i'd imagine)

if that happens, you can just remove the second one

[illumos-gate] 15960 ccidadm should use ilstr when building strings -- Joshua M. Clulow <josh⊙so>

[illumos-gate] 16512 xhci leaks oneshot interrupt IN transfers on pipe reset -- Joshua M. Clulow <josh⊙so>

out of curiosity, how tightly does bhyve in illumos follow bhyve in freebsd?

On the C userland side, fairly closely but through a sync up every 6 months or so. The kernel is maintained independently these days and has diverged in some areas.

It’s nearly time for another sync up IIRC

Andy knows where to find me for testing 😅

I have a branch done, but there is not really a lot of change. Lots of restructuring for adding aarch64 and riscv, but we have cherry picked all of the important fixes already I believe.

(and some of them originated in illumos and were then synced back to freebsd)

Would we technically be able to get the aarch64 stuff once we support aarch64?

I saw some ppt stuff wrt BAR happening recently? Or is that still in review ar freebsd side

Technically, yes, but it would be quite a lot of work

i'd imagine it'd basically require more or less writing a whole new aarch64 vmm driver

Ah right, I keep forgetting our vmm is very different from freebsd’s except the interface boundry

sjorge: sounds like a fun project :P