|This page can move to the normal documentation space after we clean it up.|
- Getting Started
- Cool Tech Demos
- X11 forwarding
- Random Notes
For best results, run the latest SmartOS release available.
The lx zone images are on images.joyent.com so make sure that's one of your image sources. Then you can import images:
Create a zone (replace the nic values with ones appropriate for your network)
|If you're not sure what these values mean or what units they are in, check out the vmadm man page|
|A selection of impressive demonstrations of the LX brand's capabilities. Please add your favorites here.|
Show your friends:
- X11 forwarded Firefox and Thunderbird in lx32 zone
- Plex Media Server usable on lx32 and lx64 (DLNA and some other bits broken still)
- dtrace a linux binary
- Video of docker in SDC (coming soon to the JPC)
- (your favorite demo here)
AF_INET and AF_INET6 mostly working (2014-12-19). Still have some sockopts missing.
ipadm is not working inside the lx brand, /native/sbin/ifconfig is usable.
Add "addrconf" to the "ips" array for the NIC to perform SLAAC and/or DHCPv6 as appropriate.
This is working fine on both 32-bit and 64-bit. After pmooney's AF_INET6 commit this is working fine out of the box!
If debugging LX branded zones, first watch this video: Debugging LX branded zones on SmartOS
As the video above mentioned, probes associated with lx_debug (that is, output associated with the LX_DEBUG environment variable) are turned on it LX_DTRACE is set to a non-zero value in the environment. However, this is not helpful if in a context that is hard to set environment variable (e.g., early in boot). The video above neglected to mention how to enable DTrace probes in this case. To do this, you must first change the disposition of the brand to enable these by default by modifying the binary. From the global zone, do the following:
(If debugging 32-bit, the lx_brand.so.1 that should be copied and mounted over should be /usr/lib/lx_brand.so.1 not /usr/lib/amd64/lx_brand.so.1.)
At that point, lx[pid]:::debug probes should show up as processes start, which will allow you to see where things are failing:
(String size and switch rate should be adjusted up if truncated strings or drops are seen.)
When debugging a new distro or otherwise debugging the death of processes before you can login, you can
These need to be run from the GZ:
|harmless unsupported syscalls|
|prctl(PR_SET_DUMPABLE)|| allow process to enable coredumps, should have no functional impact
| prctl option 4
||same as PR_SET_DUMPABLE|
|set_robust_list / get_robust_list||part of libc initialization, but if the feature is never used, then it doesn't really end up mattering.|
|futex 0x9|| usespace mutex call, mostly harmless
|socket flag MSG_CMSG_CLOEXEC|| auto close fd's... dbus spams these a lot. Looks like they get closed anyway.
|ioctl 0xc020660b (fiemap)|| used to find holes in files by querying the inode extend info, apt tries to use this. have not noticed any impact.
This is handy for figuring out why a networking app is not behaving properly.
Initial support for lx brand is complete:
Now truss should work. Note that some native binaries try to execute other native binaries. (For example, arp tries to execute netstat.) For programs written in C, this can be fixed, so please file a ticket if it doesn't work in a recent release.
If you run into a new bug, someone might ask you to try the latest CI build after it's been fixed. This is how.
The Joyent CI system constantly rebuilds the platform tarball when there are new commits.
You can extract that image and put into place on e.g. an existing SmartOS USB stick to obtain the latest and greatest code from Joyent.
You can download that platform tarball like so:
To update an existing SmartOS USB stick:
- Extract that tarball onto your USB stick (you'll get a directory named "platform-<datestamp>")
- Move aside the directory named "platform" to e.g. "platform-orig"
- Rename "platform-<datestamp>" to "platform"
- Boot from your USB stick