"Bundled JRE is not binary compatible with host OS/Arch or it is corrupt. Testing bundled JRE failed."

I was installing SUN STORAGE COMMON ARRAY MANAGER SOFTWARE 6.9, LINUX on a Centos 6 installation.
Such Centos 6 server was installed using the SmartOS image.

Running the script

./HostSoftwareCD_6.9.0.16/RunMe.bin -c

I got
 
"Bundled JRE is not binary compatible with host OS/Arch or it is 
corrupt.  Testing bundled JRE failed."

I've solved in that way:

yum install glibc.i686

vmadm destroy doesn't tell logadm to stop rotating logs #319

https://github.com/joyent/smartos-live/issues/319


logadm -n

logadm -n 2>&1|awk '{print $3}' |sed -e 's/://g' | xargs logadm -r

Apache Directory Studio "A fatal error has been detected by the Java Runtime Environment"

Ubuntu 14.04 64 bit
oracle-java7

Apache Directory Studio (ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628.tar.gz)

When I start the program from the command line (./ApacheDirectoryStudio), I get an error like this:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f518c1502a1, pid=18722, tid=139989739792128
#
# JRE version: Java(TM) SE Runtime Environment (7.0_55-b13) (build 1.7.0_55-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.55-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libsoup-2.4.so.1+0x6c2a1]  soup_session_feature_detach+0x11
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /opt/ApacheDirectoryStudio-linux-x86_64-2.0.0.v20130628/hs_err_pid18722.log
[thread 139988370728704 also had an error]
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#


To solve this issue, try to put this line

org.eclipse.swt.browser.DefaultType=mozilla

at the end of this file

configuration/config.ini

install gparted inside smartos Centos VM

Well. I'm not so virtuous to use parted inside a Centos VM to expand the filesystem.
By default the Centos Linux image dataset from SmartOS is large 10GB.
You can add another disk (it will be mounted in /data).
Or you can grow the ZFS volume related to disk0.

So, from the global zone grow the volume related to the Linux VM:

zfs set volsize=20G zones/<UUID>-disk0

I don't know, maybe you must stop the VM and start it again.

Now, from inside the VM, yes, you must install various rpms.
Firts of all the EPEL repository.

rpm --import https://fedoraproject.org/static/0608B895.txt
rpm -ivh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

yum install gparted
yum install xauth
yum install dejavu-lgc-sans-fonts.noarch

Now you can connect to the VM via ssh with the -X option (or -Y) and run gparted

Openindiana: "tree connect failed: syserr = No such file or directory"

I was trying to mount a CIFS (Samba) share from an Openindiana host,
 
-bash-4.0# mount -F smbfs //user:password@networkserver.my.domain/share /mnt/samba

I got this error

mount: //networkserver.my.domain/share: tree connect failed: syserr = No such file or directory

To solve this, I had to restart the samba client service.

svcadm restart svc:/network/smb/client:default

Fifo: vm reported as "provisioning", but it is false

Fifo: https://project-fifo.net

Why a VM status is reported as "Provisioning (Running)" even if it is already provisioned, and it is (only) running?

<killfill> that's because fifo knows if a vm is provisioning if the file 'provisioning' exists.
<killfill> Probably when creating the VM, the tools didn't wipe that file
<killfill> or maybe because you created it manually.. :P
<killfill> it's in /zones/:uuid/root/svc/ something like that.
<killfill> /zones/<uuid>/root/var/svc/provisioning

So, rm /zones/<uuid>/root/var/svc/provisioning
Et voilà.

SmartOS: add (modify) the gateway to a zone

I often forget to add the gateway to a new created zone.

So, get the nic MAC address.

vmadm get zone-uuid | json -a nics.0.mac

52:d9:d7:ab:c7:56

Create a file, like /var/tmp/updategw.json

{
   "update_nics": [
      {
         "mac": "52:d9:d7:ab:c7:56",
         "gateway": "192.168.0.1"
      }
   ]
}

Stop the zone, then issue an update.

vmadm update zone-uuid < /var/tmp/updategw.json

Verify.

vmadm get <zone-uuid> | json -a nics.0

Start the zone.