Re: [smartos-discuss] Debugging SmartOS host unresponsiveness

[Jorge Schrauwen]

To only kill the VM the only thing I can think of is doing a shutdown from the 
guest side. (You said you were still able to login)

The other option would be to indeed have it dump and then start going to the 
dead body one the node is back online.

Regards

Jorge

August 16, 2018 2:03 PM, "Nick" mailto:darknovan...@gmail.com?to=%22Nick%22%20)> wrote:
  I've been using SmartOS for about 5 years and occasionally (probably 1-2 
times per year, per server) I encounter an issue where the SmartOS host becomes 
unresponsive and the machine needs to be hard reset. When this happened last 
week I was able to SSH into one of the KVM VMs running on the machine and issue 
commands, however, the VM was obviously not running right as the load average 
was 800+ on a VM that is normally about 0.2.  The SmartOS host would echo my 
keystrokes but was not responsive to showing a logon prompt or anything. The 
SmartOS host would not accept a SSH connection either.  The HDD light was 
flashing a couple of times a second (I've seen this both on a machine that has 
only SSDs and on a machine that has only HDDs).  Does anyone have any input on 
what kind of situations could cause this kind of issue, where the host machine 
is not responsive but a KVM VM could still respond enough to allow SSH and 
commands?  Also is there any better course of action I can take next time to 
debug this, before I hard reset the machine? Should I do a IPMI crash like:  $ 
ipmitool -I lan -H  chassis power drag  and see what is in the dump? 
Or is there some way to do sysrq commands to kill the VMs but leave the host 
running for live debugging? Thank you,  Nick  

smartos-discuss | Archives 
(https://www.listbox.com/member/archive/184463/=now) | Modify 
(https://www.listbox.com/member/?) Your Subscription
 (https://www.listbox.com)



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com

Re: [smartos-discuss] bhyve: 'old' virtual machine images, network, vnc

[Jorge Schrauwen]

August 15, 2018 3:43 PM, "Stefan"  wrote:

> Dear list,
> 
> we started experimenting with bhyve recently (joyent_20180802T002654Z)
> and ran into some issues and open questions:
> 
> 1. Are the 'old' SmartOS virtual machines images, e.g.
> 
> 47f66e34-2c6d-11e8-bef9-4780fac9ac03 centos-7 
> 20180320 linux zvol 2018-03-20
> 
> supposed to be usable under bhyve? I have tested installing the centos-7
> image using b6-json

Sort of, most of those will have there network configured for DHCP. The KVM 
brand had a built in DHCP server to hand out the addresses configured via 
vmadm. Bhyve does not and relies on cloud-init to do the configuration. You 
should be able to use the old images, if you configure the network manually. At 
least for linux images.

> 
> https://gist.github.com/mgerdts/2fa6f05d3c6edd6bb7f7a9842af0579e#file-b6-json
> 
> with the image uuid replaced by that of the centos-7 image. This VM
> comes up, vmadm console works, but it does not get its network settings.

They not getting network settings is expected, see above.

> 
> 2. Is there a migration path from TYPE=KVM to TYPE=BHYV? I modified the
> brand attribute in /etc/zones/...xml file of an a earlier installed
> instance (image uuid 6aac0370-56b8-11e7-a29b-df1de8b42795 = centos-6
> 20170621) and startet the VM. It comes up, network is up, I can ssh
> into the VM. But
> 

Some attribute are not supported or ignored by bhyve (e.g. model other than 
virtio for nics) ...
bhyve also wants a few extra ones to configure the serial console. The easiest 
way I have found to migrated an existing KVM is:
- configure the network statically while it is still booted via KVM
- halt the KVM zone
- (remove the nics - to avoid conflict of IPs, optionally remove the hostname 
value)
- create a bhyve zone with same disk/network config
- zfs destroy zones/NEW_ZONE_UUID/disk0
- zfs rename zones/OLD_ZONE_UUID-disk0 zones/NEW_ZONE_UUID/disk0
- boot the bhyve zone and see if everything works.

I believe eventually joyent wants to add an auto convert of sorts.


> - there is no output on vmadm console
> - mdata-get sdc:net hangs and repeats "plat_recv timeout"
> - a start script hangs:
> 
> |-rc,757 /etc/rc.d/rc 3
> | `-bash,1485 /etc/rc3.d/S99local start
> | `-mdata-get,1495 dummykey

If you just swapped the type from KVM -> bhyve using zonecfg/editing the xml, 
that is to be expected as the serial consoles are set up differently.

> 
> - vncviewer connects to the vnc port but does not ask
> for the password and shows only a black screen.

There is no password support or VNC yet (I think it is planned in the future 
though, but don't quote me on that).
I never had any success with vnc + uefi-csm-rom.bin (what is shipped 
currently), the soon to come PI will have both uefi-rom.bin and 
uefi-csm-rom.bin shipped, you can select the uefi only one by setting 
bootrom=uefi, that way vnc should work.

> 
> 3. I added vnc_port and vnc_password to the b6-json and installed the
> 462d1d03-8457-e134-a408-cf9ea2b9be96 centos-bhyve-7 image. This starts
> fine, has network and vmadm console but the vnc is not working as noted
> above.

You will still hit rough spots here and there so now might not be the time to 
switch over all your VMs. I myself hit a nasty issue with bhyve and netwerk 
traffic to zones on the same CN which can hang the bhyve guest. For now I have 
a CN dedicated for testing with bhyve, none of my guests are based on pre made 
images though.

> 
> Any suggestion is appreciated.
> 
> Kind Regards,
> Stefan

Regards and good luck!

Jorge

> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com

Re: [smartos-discuss] anyone know a SmartOS friendly Mini-ITX motherboard?

[Jorge Schrauwen]

I ran a SmartOS computenode on a 
https://www.supermicro.com/products/motherboard/atom/A2SDi-8C-HLN4F.cfm for a 
few years.
Sadly it died earlier this year due to the hardware bug in the Avaton series 
CPU's.

Other that, the board and atom CPU performed decently. Not as powerfull 
compared to a 2x Ivy Bridge based board. But well enough given the hardware 
specs.

Regards

Jorge

July 21, 2018 7:25 PM, "Michal Nowak"  wrote:

> On 07/21/18 01:51 PM, Robert Fisher wrote:
> 
>> I've given up on the idea of any Illumos flavour ever running on my
>> little home server, so I'm planning to swap out the main board.
>> 
>> The backstory of this is that I successfully ran Solaris 11 on it
>> (encrypted ZFS -- I'm paranoid) and when I upgraded the BIOS (I know,
>> never upgrade the BIOS, but I was hoping to fix a NIC oddity) it no
>> longer booted. I found if I disabled all but one core, Solaris would
>> still boot, and I still run it that way, which is pretty unsatisfactory.
>> SmartOS will not boot whatever I do. All other unix-like OSes run fine
>> across all cores. I have posted about this on the list before, but to no
>> avail.
>> 
>> I don't want to buy a whole new machine, so I need a Mini ITX
>> motherboard that'll take an i5 6400 (so 6th gen) CPU. Anyone got
>> anything that's known to work? The one that doesn't is an ASUS H110I-Plus.
>> 
>> thanks in advance
>> 
>> Rob
> 
> Hi Rob,
> 
> I don't know of a suitable mini ITX motherboard but it seems that there
> were three BIOS updates since your original February post regarding the
> motherboard. Perhaps you can take a chance updating to the latest BIOS?
> Or perhaps you can downgrade to a known working one?
> 
> Good luck,
> Michal
> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com

Re: [smartos-discuss] Smartos bhyve support on AMD Sun Fire X4140

[Jorge Schrauwen]

Yeah, no support as of yet. Although there does seem to be some interest in 
adding it eventually. (Based on conversations on IRC)

July 3, 2018 6:38 PM, "Ján Poctavek" mailto:jan.pocta...@erigones.com?to=%22J%C3%A1n%20Poctavek%22%20)>
 wrote:
Hi, 

Just to be sure - so no AMD support again?
Jan
On 3. 7. 2018 11:42, Jorge Schrauwen wrote: For now bhyve support on SmartOS 
requires VMX and EPT to work.
So older intel CPU without EPT or AMD CPU that use SVM are not support.

Regards

Jorge

July 3, 2018 11:15 AM, "Paolo Marcheschi" mailto:paolo.marches...@ftgm.it?to=%22paolo%20marcheschi%22%20%3cpaolo.marches...@ftgm.it%3E)>
 wrote:
Hi 

Today I tried to run a bhyve VM on the latest Smartos: 

SunOS 5.11 joyent_20180629T143106Z i86pc i386 i86pc 

The server is an AMD Opteron Sun Fire X4140 : 

psrinfo -vp The physical processor has 6 virtual processors (0-5) x86 
(AuthenticAMD 100F80 family 16 model 8 step 0 clock 2200 MHz) Six-Core AMD 
Opteron(tm) Processor 2427 [ Socket: F(1207) ] The physical processor has 6 
virtual processors (6-11) x86 (AuthenticAMD 100F80 family 16 model 8 step 0 
clock 2200 MHz) Six-Core AMD Opteron(tm) Processor 2427 [ Socket: F(1207) ] 
when I try to create a bhyve VM I get: 
#vmadm create -f centos.json 
Bhyve not supported  
Why ? 
Thank you 
Paolo  
smartos-discuss | Archives 
(https://www.listbox.com/member/archive/184463/=now) | Modify 
(https://www.listbox.com/member/?) Your Subscription
 (http://www.listbox.com)



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Smartos bhyve support on AMD Sun Fire X4140

[Jorge Schrauwen]

For now bhyve support on SmartOS requires VMX and EPT to work.
So older intel CPU without EPT or AMD CPU that use SVM are not support.

Regards

Jorge

July 3, 2018 11:15 AM, "Paolo Marcheschi" mailto:paolo.marches...@ftgm.it?to=%22Paolo%20Marcheschi%22%20)>
 wrote:
Hi 

Today I tried to run a bhyve VM on the latest Smartos: 

SunOS 5.11 joyent_20180629T143106Z i86pc i386 i86pc 

The server is an AMD Opteron Sun Fire X4140 : 

psrinfo -vp The physical processor has 6 virtual processors (0-5) x86 
(AuthenticAMD 100F80 family 16 model 8 step 0 clock 2200 MHz) Six-Core AMD 
Opteron(tm) Processor 2427 [ Socket: F(1207) ] The physical processor has 6 
virtual processors (6-11) x86 (AuthenticAMD 100F80 family 16 model 8 step 0 
clock 2200 MHz) Six-Core AMD Opteron(tm) Processor 2427 [ Socket: F(1207) ] 
when I try to create a bhyve VM I get: 
#vmadm create -f centos.json 
Bhyve not supported  
Why ? 
Thank you 
Paolo 
smartos-discuss | Archives 
(https://www.listbox.com/member/archive/184463/=now) | Modify 
(https://www.listbox.com/member/?) Your Subscription
 (http://www.listbox.com)



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Error in Smartos Build: Connection timed out

[Jorge Schrauwen]

These are a bit out of date, but mostly still apply.
https://docu.blackdot.be/snipets/solaris/smartos-nat 
(https://docu.blackdot.be/snipets/solaris/smartos-nat)
https://docu.blackdot.be/snipets/solaris/smartos-ipv6 
(https://docu.blackdot.be/snipets/solaris/smartos-ipv6)

Regards

Jorge

June 27, 2018 4:47 PM, "Paolo Marcheschi" mailto:paolo.marches...@ftgm.it?to=%22Paolo%20Marcheschi%22%20)>
 wrote:
Hi 

I'm trying to build a smartos image following the Building instructions 
(https://wiki.smartos.org/display/DOC/Building+SmartOS+on+SmartOS) 

It starts fine but after a while it stops with an error of connection 
timeout: /home/paolo/smartos-live/proto/usr/bin/gcc -o 
build/ia32/mdb_v8_version.o -c -g -Werror -Wall -Wextra -fPIC 
-fno-omit-frame-pointer -g -O -Wno-unused-parameter 
-Wno-missing-field-initializers -Wno-sign-compare -Wno-unknown-pragmas -m32 
-isystem /home/paolo/smartos-live/proto//usr/include 
-DMDBV8_VERS_TAG='"release, from 28f2bfa"' -Ideps/illumos-libavl/include 
build/mdb_v8_version.c
git submodule update --init deps/illumos-libavl
error: index file 
.git/objects/pack/._pack-d52084469b7d1b24e3f8a9b06c58e14cc89487a8.idx is too 
small
error: index file 
.git/objects/pack/._pack-d52084469b7d1b24e3f8a9b06c58e14cc89487a8.idx is too 
small
Submodule 'deps/illumos-libavl' (git://github.com/joyent/illumos-libavl 
(http://github.com/joyent/illumos-libavl)) registered for path 
'deps/illumos-libavl'
error: index file 
.git/objects/pack/._pack-d52084469b7d1b24e3f8a9b06c58e14cc89487a8.idx is too 
small
error: index file 
.git/objects/pack/._pack-d52084469b7d1b24e3f8a9b06c58e14cc89487a8.idx is too 
small
Cloning into 'deps/illumos-libavl'...
fatal: unable to connect to github.com (http://github.com):
github.com (http://github.com)[0: 192.30.253.112]: errno=Connection timed out
github.com (http://github.com)[1: 192.30.253.113]: errno=Connection timed out
Clone of 'git://github.com/joyent/illumos-libavl 
(http://github.com/joyent/illumos-libavl)' into submodule path 
'deps/illumos-libavl' failed
Makefile.targ:159: recipe for target 'deps/illumos-libavl/.git' failed
gmake: *** [deps/illumos-libavl/.git] Error 1
Makefile:48: recipe for target 'all' failed
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory 
'/home/paolo/smartos-live/projects/illumos-extra/mdb_v8'
Makefile:150: recipe for target 'mdb_v8' failed
gmake[1]: *** [mdb_v8] Error 2
gmake[1]: Leaving directory '/home/paolo/smartos-live/projects/illumos-extra'
Makefile:307: recipe for target '1-extra-stamp' failed
gmake: *** [1-extra-stamp] Error 2 
uname -a 
SunOS xxx 5.11 joyent_20171221T020409Z i86pc i386 i86pc Solaris  
I can do a git clone of git://github.com/joyent/illumos-libavl 
(http://github.com/joyent/illumos-libavl) without any problem from the same 
zone. 
How can I do to solve this problem ? 
Thank you 
Paolo 
smartos-discuss | Archives 
(https://www.listbox.com/member/archive/184463/=now) | Modify 
(https://www.listbox.com/member/?) Your Subscription
 (http://www.listbox.com)



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KVM built-in DHCP server

[Jorge Schrauwen]

Hi Rob,

You do not need to do anything special.
If you have 'dhcp' in the ips property it will just get an IP from your normal 
DHCP server.

The build in DHCP server you mentioned only comes into play with static IP's 
are set in the ips array, rereading that it still looks a bit confusing...

'dhcp' in nics.X.ips => gets IP from normal DHCP server
'172.16.123.8' in nics.X.ips => gets '172.16.123.8' from KVM's mini DHCP server 
(you can ofcourse use any static-ip here)

It's been a very long while but I do believe that KVM will pxe boot, you need 
to set the boot order to 'n' if I remember correctly.

Regards

Jorge

June 11, 2018 10:19 PM, "Rob Seastrom"  wrote:

> In a recent thread, Brian mentioned the "mini DHCP server" in the KVM brand 
> zone.
> 
> I had a couple of questions about that that have been rattling around in the 
> back of my head for a
> while...
> 
> First off, is there a way to turn this off and allow the guest in the KVM 
> zone to DHCP from another
> server elsewhere on the vlan? Some combination of nics.*.allow_dhcp_spoofing 
> and configuring the
> NIC with no IP address? I don't see any nics.*.dhcp_client in the vmadm man 
> page...
> 
> Second, assuming the above is feasible, does the SeaBIOS (which I think is 
> what we're running in
> qemu) know enough to PXEboot? I want to netboot http://ipxe.org and chain on 
> to doing other things.
> 
> Goal here is development environment for custom ipxe builds and preseeds for 
> bare metal imaging.
> 
> Anyone done anything like this before? I've been using vmware as a dev 
> environment and it is
> wearing thin because of what a pain it is to do my repeated pave-and-rebuild 
> cycles.
> 
> Thanks,
> 
> -r
> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB Passthrough

[Jorge Schrauwen]

It wont work in LX or KVM either. 

Given LX is a branded zone that does ABI emulation, there is no linux
kernel/linux drivers to hook up to the device either. 

The qemu that works with our KVM is also quite old, I have not got USB
or PCI passthrough to work with that. You can add the device with
zonecfg but it will be passed as a disk to qemu and that obviously won't
work.

You might be able to use a RasberryPi and some software to expose the
USB device over TCP. But I have not looked into that very much. 

Regards 

Jorge 

On 2018-05-17 17:38, j...@sonlawrence.com wrote:

> What are the possibilities and limitations of passing through USB devices to 
> zones? Are there obvious differences between how native, LX, and KVM zones 
> handle this? 
> 
> From what I've read it seems unsupported, but possible by manually adding a 
> 'device' entry via zonecfg. The USB device is detected but does not have 
> drivers in the global zone (and therefore won't in a native zone either). I'd 
> like to expose it to an Ubuntu zone (either LX or KVM). Has anyone had 
> success and can provide guidance? 
> 
> --jason 
> 
> SMARTOS-DISCUSS | Archives [1] | Modify [2] Your Subscription
> [3]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/?
[3] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] dedicate PCI card to non-global zone

[Jorge Schrauwen]

You can pass through devices using zonecfg -z zone-uuid but this is 
unsupported.


I have used it to pass through my APC upsd USB ugen device and it worked 
fine.


Regards

Jorge



On 2018-05-14 18:31, Dan McDonald wrote:
On May 14, 2018, at 12:13 PM, Mat Schreiber via smartos-discuss 
 wrote:


Hi,

I want to install in one of the smartos machines a TV to IP Server... 
for that I have to "share" or "dedicate" the PCI card to that zone.

Is that possible? I do not find anything related to that.
Does not import if it is with a native smartos zone or a KVM zone. Or 
does it work just for NICs and things like that?


PCI passthrough is what you want, and I think you'll need bhyve for
that.

Dan




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] DIY pkgsrc?

[Jorge Schrauwen]

It’s possible, I run one for my own packages.
All the info should be here https://github.com/joyent/pkgsrc/wiki

(On mobile so can’t be more specific)

~ sjorge 

> On 1 May 2018, at 12:43, Robert Fisher  wrote:
> 
> I build pkgin (pkgsrc?) packages of certain tools, customized to my own 
> needs. To get them on my hosts I stick them in Manta, and config-management 
> downloads them and installs them from the local filesystem. This has always 
> seemed crude and clumsy, but works.
> 
> Now I'm looking at deploying my own code via pkgin packages, but I can't see 
> an efficient way to do it. My stick-it-in-Manta approach can't cut it with 
> frequently rebuilt packages: I need a proper repo. If I used, say, ubuntu, my 
> CI pipeline would drop the package in Artifactory or Gemfury or whatever, and 
> it would be pulled down from there by the proper packaging tools on the next 
> config-management run. 
> 
> How would I (could I, even?) implement a similar approach with pkgin on 
> SmartOS? I haven't been able to find any documentation on running additional 
> private repos, which is starting to make me wonder if it's even possible.
> 
> Before I start re-inventing wheels, is there any accepted best-practice I 
> should begin with? 
> 
> 
> Rob
> smartos-discuss | Archives | Modify Your Subscription  



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] pkgsrc-2018Q1 breaks SaltStack

[Jorge Schrauwen]

Quick bit of follow up, using 2018.3 it works fine. (Aside from the 
jinja2 indent bug mentioned earlier)
So it probably got fixed upstream. (pip install works, or you can grab 
my package from https://pkg.blackdot.be/)


[cronos :: sjorge][~]
[.]$ pfexec salt -l warning isotope test.ping
isotope:
True

[cronos :: sjorge][~]
[!]$ salt-call --versions-report
Salt Version:
   Salt: 2018.3.0

Dependency Versions:
   cffi: 1.11.5
   cherrypy: 14.0.1
   dateutil: 2.7.2
  docker-py: Not Installed
  gitdb: 2.0.3
  gitpython: 2.1.9
  ioflo: Not Installed
 Jinja2: 2.10
libgit2: Not Installed
libnacl: 1.6.1
   M2Crypto: 0.29.0
   Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.5.6
   mysql-python: Not Installed
  pycparser: 2.18
   pycrypto: 2.6.1
   pycryptodome: Not Installed
 pygit2: Not Installed
 Python: 2.7.14 (default, Apr  7 2018, 14:51:22)
   python-gnupg: 0.4.2
 PyYAML: 3.12
  PyZMQ: 17.0.0
   RAET: Not Installed
  smmap: 0.9.0
timelib: 0.2.4
Tornado: 4.5.3
ZMQ: 4.2.3

System Versions:
   dist:
 locale: UTF-8
machine: i86pc
release: 5.11
 system: SunOS
version: Not Installed



On 2018-04-15 23:06, Paul Sture wrote:

# salt --version
salt 2017.7.4 (Nitrogen)
# salt orange test.ping
[WARNING ]
/opt/tools/lib/python2.7/site-packages/salt/utils/async.py:56:
DeprecationWarning: zmq.eventloop.ioloop is deprecated in pyzmq 17.
pyzmq now works with default tornado and asyncio eventloops.
  self.io_loop = LOOP_CLASS()

No minions matched the target. No command was sent, no jid was
assigned.
ERROR: No return received




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] pkgsrc-2018Q1 breaks SaltStack

[Jorge Schrauwen]

There is also a bug with the newer jinja2 in relation to salt:
https://github.com/saltstack/salt/issues/46594

jinja2 2.9.6 is the last know working one.
There is an upstream fix but there is no release yet with that one 
included.


Regards

Jorge

On 2018-04-15 23:06, Paul Sture wrote:

# salt --version
salt 2017.7.4 (Nitrogen)
# salt orange test.ping
[WARNING ]
/opt/tools/lib/python2.7/site-packages/salt/utils/async.py:56:
DeprecationWarning: zmq.eventloop.ioloop is deprecated in pyzmq 17.
pyzmq now works with default tornado and asyncio eventloops.
  self.io_loop = LOOP_CLASS()

No minions matched the target. No command was sent, no jid was
assigned.
ERROR: No return received




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] DHCPv6 Client Prefix Delegation

[Jorge Schrauwen]

Hi Bill, 

From experience, LX zones use the native dhcpclient and network
configuration tools from /native. 

Regards 

Jorge 

On 2018-04-06 16:02, H. William Welliver III wrote:

> Hi Jorge, 
> 
> Thanks for the info. I was able to include "addrconf" to the list of ips for 
> my nic and got a v6 address from my upstream provider (I'm using a SmartOS 
> zone as an IPv4 router for my enclave). If SmartOS supported PD, I could get 
> a network allocation and then be able to assign routable v6 addresses to all 
> of my clients. PD uses DHCP but it's not strictly about configuring a given 
> interface, so I can see the rationale why it isn't supported. 
> 
> Thinking out loud.. I wonder if LX zones use the illumos dhcpagent or the one 
> typically used by the LX distro in use? Perhaps some more research is in 
> order. 
> 
> Best, 
> 
> Bill 
> 
> On Apr 5, 2018, at 3:23 PM, Jorge Schrauwen <sjorge...@blackdot.be> wrote: 
> 
> Hi Bill, 
> 
> There is some IPv6 support but Prefix Delegation is not amoung it AFAIK. 
> 
> the basics are ```ipadm create-addr -T addrconf net0/v6auto``` to grab SLAAC 
> address, static works by ```ipadm create-addr -T static -a 
> my:ad:dr:es:he:re/64 net/v6static``` 
> 
> I think the -T addrconf will also grab a stateful address but I do not run 
> DHCPv6 in my network. 
> 
> Regards 
> 
> Jorge
> 
> On 2018-04-05 20:49, H. William Welliver III wrote: 
> Hi all,
> 
> I've got a project coming up and have been getting (back) up to speed with 
> IPv6... My understanding is that the SmartOS/Illumos DHCP client does not 
> support Prefix Delegation. Can anyone confirm that, or have I missed some 
> nugget buried deep in the documentation?
> 
> Thanks in advance!
> 
> Bill

 SMARTOS-DISCUSS | Archives [1] | Modify [2] Your Subscription
 [3]

 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2]
https://www.listbox.com/member/?;
[3] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] add device to OS/LX zone

[Jorge Schrauwen]

In your example you called newfs, which creates a new UFS file system.

I think if you don't create a filesystem on it and use it as a raw block
device it should just work.
This is what qemu does when running inside a KVM branded zone. 

Regards 

Jorge 

On 2018-02-27 14:05, Fred Liu wrote:

> Actually，we need access the real hardware not the file system. There is some 
> database software which claims having performance optimization on real 
> hardware. I notice that we can tune zfs rec block size in vm, maybe that is 
> another idea. Anyone tuned? 
> 
> Thanks! 
> 
> Fred 
> 
> On Tue, Feb 27, 2018 at 8:45 PM +0800, "Jorge Schrauwen" 
> <sjorge...@blackdot.be> wrote:
> 
>> Hi,
>> 
>> You probably want to set fs_allowed so it includes the filesystem you 
>> are trying to create on it.
>> 
>> (from man vmadm)
>> fs_allowed:
>> 
>> This option allows you to specify filesystem types this zone 
>> is allowed
>> to mount.  For example on a zone for building SmartOS you 
>> probably want
>> to set this to: "ufs,pcfs,tmpfs".  To unset this property, 
>> set the
>> value to the empty string.
>> 
>> type: string (comma separated list of filesystem types)
>> vmtype: OS
>> listable: no
>> create: yes
>> update: yes (requires zone reboot to take effect)
>> 
>> Regards
>> 
>> Jorge
>> 
>> On 2018-02-27 13:41, Fred Liu wrote:
>>> Hi,
>>> 
>>> For I have no spare hardware(disk), I have tried adding zvol to OS/LX
>>> zone. But it looks likes not working as the document.
>>> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
>>> match=/dev/zvol/rdsk/zones/device
>>> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
>>> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
>>> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit
>>> 
>>> [root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
>>> [Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
>>> Last login: Tue Feb 27 20:25:02 on pts/6
>>> __.   .
>>> _|  |_  | .-. .  . .-. :--. |-
>>> |__| ;|   ||  |(.-' |  | |
>>> |__|   `--'  `-' `;-| `-' '  ' `-'
>>> /  ; Instance (base-multiarch-lts 15.4.0)
>>> `-'  https://docs.joyent.com/images/smartos/base
>>> 
>>> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
>>> /dev/zvol/rdsk/zones/device
>>> crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
>>>  [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
>>> /dev/zvol/rdsk/zones/device
>>>  newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
>>> y
>>> can't check mount point; can't stat
>>> 
>>> Will the real hardware be different?
>>> 
>>> I also tried adding zvol to zones on solaris11.2. It works well.
>>> device:
>>> match not specified
>>> storage.template:
>>> dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
>>> storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
>>> 0
>>> bootpri: 0
>>> device:
>>> match not specified
>>> storage: dev:/dev/zvol/dsk/tank/device
>>> 2
>>> bootpri: 2
>>> capped-memory:
>>> physical: 2G
>>> keysource:
>>> raw redacted
>>> zonecfg:kz01>
>>> 
>>> root@kz01:~# format
>>> Searching for disks...done
>>> 
>>> AVAILABLE DISK SELECTIONS:
>>>   . c1d0
>>> /kz-devices@ff/disk@0
>>> c1d2
>>> /kz-devices@ff/disk@2
>>> Specify disk (enter its number): ^C
>>> root@kz01:~# zpool create test1 c1d2
>>> root@kz01:~# zpool list
>>> NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
>>> rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
>>> test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
>>> root@kz01:~#
>>> 
>>> Thinking little bit more, for we already can add zvol to kvm zone, it
>>> should not be very hard to realize in OS/LX zone.
>>> 
>>> Thanks.
>>> 
>>> Fred
>>> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] add device to OS/LX zone

[Jorge Schrauwen]

Hi,

You probably want to set fs_allowed so it includes the filesystem you 
are trying to create on it.


(from man vmadm)
   fs_allowed:

   This option allows you to specify filesystem types this zone 
is allowed
   to mount.  For example on a zone for building SmartOS you 
probably want
   to set this to: "ufs,pcfs,tmpfs".  To unset this property, 
set the

   value to the empty string.

   type: string (comma separated list of filesystem types)
   vmtype: OS
   listable: no
   create: yes
   update: yes (requires zone reboot to take effect)

Regards

Jorge


On 2018-02-27 13:41, Fred Liu wrote:

Hi,

For I have no spare hardware(disk), I have tried adding zvol to OS/LX
zone. But it looks likes not working as the document.
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
match=/dev/zvol/rdsk/zones/device
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit

[root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
[Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
Last login: Tue Feb 27 20:25:02 on pts/6
   __.   .
 _|  |_  | .-. .  . .-. :--. |-
|__| ;|   ||  |(.-' |  | |
  |__|   `--'  `-' `;-| `-' '  ' `-'
   /  ; Instance (base-multiarch-lts 15.4.0)
   `-'  https://docs.joyent.com/images/smartos/base

[root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
/dev/zvol/rdsk/zones/device
crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
 [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
/dev/zvol/rdsk/zones/device
 newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
y
can't check mount point; can't stat

Will the real hardware be different?

I also tried adding zvol to zones on solaris11.2. It works well.
device:
  match not specified
  storage.template:
dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
  storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
  0
  bootpri: 0
device:
  match not specified
  storage: dev:/dev/zvol/dsk/tank/device
  2
  bootpri: 2
capped-memory:
  physical: 2G
keysource:
  raw redacted
zonecfg:kz01>

root@kz01:~# format
Searching for disks...done

AVAILABLE DISK SELECTIONS:
. c1d0 
  /kz-devices@ff/disk@0
  c1d2 
  /kz-devices@ff/disk@2
Specify disk (enter its number): ^C
root@kz01:~# zpool create test1 c1d2
root@kz01:~# zpool list
NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
root@kz01:~#

Thinking little bit more, for we already can add zvol to kvm zone, it
should not be very hard to realize in OS/LX zone.

Thanks.

Fred




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KPTI testing help wanted (PCID edition)

[Jorge Schrauwen]

Just got it booted on on my dual Xeon Ivy Bridge.
Probably won't get to put a whole lot of load on it though.

---
~ sjorge

On 2018-02-23 08:08, Jussi Sallinen wrote:

On 23 Feb 2018, at 4.17, Alex Wilson  wrote:


Hi all,

Same deal as before, I would like to solicit testers for a DEBUG image
of KPTI with PCID support this time. I am particularly interested in
anyone who has a Nehalem or Westmere era Xeon to try this one out, as
well as anyone who can put significant load on it. Quite a few of the
bugs we've found so far have only been visible when all the CPUs were
kept busy at once. :)

Thanks again!

https://us-east.manta.joyent.com/arekinath/public/kpti/20180221T003551Z/platform-20180221T003551Z.tgz
https://us-east.manta.joyent.com/arekinath/public/kpti/20180221T003551Z/platform-20180221T003551Z.iso
https://us-east.manta.joyent.com/arekinath/public/kpti/20180221T003551Z/platform-20180221T003551Z.usb.bz2


I’ll be able to run tests on X5500 system (Fire X4170) during the
weekend, if I’m not mistaking it’s Nehalem based.

-Jussi




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KPTI testing help wanted

[Jorge Schrauwen]

For those only on the mailing list. I am now running the KPTI build without 
issue.

1. Initial problems were due to how I boot SmartOS which has a tweaked grub.
2. Second issue with because my zones/dump was size just large enough for a 
non-debug build. After resizing it to accommodate the size of a debug kernel 
everything booted smoothly. (dumpadm -e is your friend)

~ sjorge 

> On 1 Feb 2018, at 18:20, Jorge Schrauwen <sjorge...@blackdot.be> wrote:
> 
> Progress... but not in the good direction.
> I got it to boot to the point were it starts to load smf services.
> system/filesystem/joyent seems to repeatedly fail. Nothing ends up in the 
> logs in /var/svc/log...
> 
> I rebooted to the current PI and it came right up.
> I will check for cores in a bit.
> 
> Regards
> 
> Jorge
> 
> 
> 
>> On 2018-01-31 03:40, Alex Wilson wrote:
>>> On 29/01/18 23:52, Alex Wilson wrote:
>>> These images have held up to our initial testing (they can run e.g. the
>>> dtest suite, stand up a CoaL or simple Manta, basic LX functionality
>>> seems to work), so please try whatever unusual and interesting workloads
>>> you can find on them.
>> I would also like to note for anyone using these that the ISO image has
>> its default console device set to serial ttyb (COM-2). You can change
>> this in GRUB by using "c" and "variable os_console vga" (for example,
>> to
>> change to the vga glass console).
>> If you get a screen of dots from GRUB and then silence (no "SunOS
>> Release 5.11 Version joyent_20180130T004501Z 64-bit" banner), then
>> double-check the console device that was set, you might be watching the
>> wrong one.
>> Thanks again!
> 
> 
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KPTI testing help wanted

[Jorge Schrauwen]

Hi Alex,

Finally got a bit further :|
https://i.imgur.com/hRmgnTn.jpg

So to be able to quickly switch back I updated menu list like this:
https://gist.github.com/sjorge/c7cc93cc7e100e9997fa7d50df4cd117

Using the bits from nopkti/ boots fine (20180118T013028Z), using the 
kpti/ directory gives the result from the screen shot above.


I might poke it some more on a later timeframe.

Regards

Jorge


On 2018-01-31 11:39, Jorge Schrauwen wrote:

Not much success with the new image, remote so can't do more
troubleshooting now.
Also why I am not on IRC, as the box is now dead in the water again.

Regards

Jorge


On 2018-01-31 03:40, Alex Wilson wrote:

On 29/01/18 23:52, Alex Wilson wrote:


These images have held up to our initial testing (they can run e.g. 
the

dtest suite, stand up a CoaL or simple Manta, basic LX functionality
seems to work), so please try whatever unusual and interesting 
workloads

you can find on them.



I would also like to note for anyone using these that the ISO image 
has

its default console device set to serial ttyb (COM-2). You can change
 this in GRUB by using "c" and "variable os_console vga" (for example,
to
change to the vga glass console).

If you get a screen of dots from GRUB and then silence (no "SunOS
Release 5.11 Version joyent_20180130T004501Z 64-bit" banner), then
double-check the console device that was set, you might be watching 
the

wrong one.

Thanks again!







---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KPTI testing help wanted

[Jorge Schrauwen]

Not much success with the new image, remote so can't do more 
troubleshooting now.

Also why I am not on IRC, as the box is now dead in the water again.

Regards

Jorge


On 2018-01-31 03:40, Alex Wilson wrote:

On 29/01/18 23:52, Alex Wilson wrote:


These images have held up to our initial testing (they can run e.g. 
the

dtest suite, stand up a CoaL or simple Manta, basic LX functionality
seems to work), so please try whatever unusual and interesting 
workloads

you can find on them.



I would also like to note for anyone using these that the ISO image has
its default console device set to serial ttyb (COM-2). You can change
 this in GRUB by using "c" and "variable os_console vga" (for example,
to
change to the vga glass console).

If you get a screen of dots from GRUB and then silence (no "SunOS
Release 5.11 Version joyent_20180130T004501Z 64-bit" banner), then
double-check the console device that was set, you might be watching the
wrong one.

Thanks again!




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KPTI testing help wanted

[Jorge Schrauwen]

Hi Alex,

Not of too a super good start for me :(
I swap in the PI you linked below but the box did not come back.

I did have a serial console open (remotely from work) and the only 
output is:

"Copyright (c) 2"

Nothing else, check the actualy vga console once I get home in like 6 
hours from now.
I'll probaly revert back to the PI I had before this though. It does not 
seem to dump core or reboot. It just seems stuck.


Regards

Jorge


On 2018-01-30 08:52, Alex Wilson wrote:

Hi all,

We're at the stage with the illumos/SmartOS KPTI (Meltdown mitigation)
work now that we would like to solicit help with testing from the
 community. So for those keen to help out with some testing, you can
find
links to a platform image with KPTI (and full DEBUG assertions) below.

This is plain KPTI with no PCID support yet.

These images have held up to our initial testing (they can run e.g. the
dtest suite, stand up a CoaL or simple Manta, basic LX functionality
 seems to work), so please try whatever unusual and interesting
workloads
you can find on them.

Of special interest to us is anybody who has a machine that takes MCEs
(machine check exceptions) a lot (e.g. because of a bad ECC DIMM that's
reporting errors), workloads making extensive use of/causing floating
point exceptions, and workloads that make use of LDTs (if we have any?
anyone?).

When you find issues, please reply to this mailinglist thread here on
smartos-discuss@ so I can keep track of them easily :)

Also please note that these are from a DEBUG build, so it's probably a
bad idea to compare performance unless you're doing it very carefully
and your baseline is another DEBUG build pre-KPTI (i.e. *not* a regular
production SmartOS image). These will be quite a bit slower than a
regular non-DEBUG image.

https://us-east.manta.joyent.com/arekinath/public/kpti/20180130T004501Z/platform-20180130T004501Z.iso
https://us-east.manta.joyent.com/arekinath/public/kpti/20180130T004501Z/platform-20180130T004501Z.tgz
https://us-east.manta.joyent.com/arekinath/public/kpti/20180130T004501Z/platform-20180130T004501Z.usb.bz2

We're not soliciting code review just yet, because we know we still
need
to clean some stuff up. But we want to find bugs. :) If it's
particularly useful to be able to see the code for the testing you want
to do, it's at
https://github.com/rmustacc/illumos-gate/tree/kpti-rebase

Thanks!

-  Alex
(on behalf of Robert and John and everyone else who's been helping out)




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] logadm messages for unknown zone-uuids

[Jorge Schrauwen]

I think I have seen this after it was fixed too.
logadm -r /zones/9f3484d5-2807-42c2-8204-eb04fe87d0e4/root/tmp/vm.log

Will make it go away for that particular file.

---
~ sjorge

On 2018-01-26 10:56, David Brooke wrote:

Hi,

On Fri, Jan 26, 2018 at 10:15:11AM +0100, qutic development wrote:


cron is sending me logadm messages for unknown zone-uuids every hour:

logadm: Warning: 
/zones/9f3484d5-2807-42c2-8204-eb04fe87d0e4/root/tmp/vm.log: No such 
file or directory

...


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

Apparently fixed now but there are a couple of workarounds in that
issue
log to help with cleaning up from older releases.

David




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Building a 32-bit kernel

[Jorge Schrauwen]

If you want the more traditional Solaris-like experience,
OmniOSce and OpenIndiana should both still work fine on 32-bit x86 
CPU's.


They ship both 32 and 64-bit binaries of everything. Admittedly I have 
not

tried this myself so your luck may vary.

Regards

Jorge

On 2018-01-22 13:00, Jonathan Perkin wrote:

* On 2018-01-22 at 11:52 GMT, a b wrote:


Apologies if this has been asked before,  in  which  case  I
will  be  grateful  to be pointed to the documentation to go
read.

I have a perfectly good, last generation Pentium 4 server at
3.2  GHz  which  currently runs Solaris 10 GA (01/2006). I'd
like to migrate away from Solaris 10 and run SDC on it.

Solaris and by extension illumos used to  have  full  32-bit
kernel  support,  which  if  I understood correctly has pur-
posely been ripped out.

I'd hate to waste a good server just because it has a 32-bit
processor. Is there a way to restore that and build a 32-bit
kernel so I can run SmartOS and SDC? What steps do I need to
take?


It's just software, so there's always a way, but SmartOS has never
supported 32-bit so you will need to do a huge amount of engineering
work by yourself to achieve this.  It's not simply a case of reverting
some patches and booting a custom build.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] pkgsrc local cache

[Jorge Schrauwen]

I have this blog post saved: 
http://www.daveeddy.com/2015/07/19/smartos-pkgsrc-caching-proxy/

I haven't done it my self but it's on my todo list.

Would be nice if there was something on images.joyent.com though, but I 
haven't found one yet.


Regards

Jorge

On 2018-01-20 18:34, Jesus Cea wrote:

I wonder if there is out there a pkgsrc cache that I could run in a
zone
and cache pkgsrc metadata and packages to serve to other
zones/machines.

I would like to be able to:

1.  Reduce the load on joyent infra.
 Faster install speed and no impact when reprovisioning machines when
packages already present in the pkgsrc cache.
 Being able to use pkgsrc even on machines/zones with no trivial
Internet access.

If not, is there any interest in such a project?.




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Remove ZIL from zones pool?

[Jorge Schrauwen]

The package exists in OmniOS, so I guess it did compile at somepoint.

~ sjorge 

> On 19 Jan 2018, at 12:28, Paul Sture  wrote:
> 
>> On 19 Jan 2018, at 12:10, Jonathan Perkin wrote:
>> 
>> GNU parted is pretty small so it could be argued it wouldn't have much
>> of an impact, but the principles remain the same.  This is why we
>> prefer to add software to the GZ tools set, available here:
>> 
>>  https://pkgsrc.joyent.com/install-on-illumos/#tools-install
>> 
>> which isn't bound by the same restrictions.
>> 
> 
> On that subject, are there any notes anywhere about adding packages found
> in the full 64-bit pkgsrc kit to the GZ tools?  I am not asking for additions
> to the official GZ tools package here; I am quite happy to have a way of
> adding extras after the standard GZ tools package has been installed.
> 
> Background to this: before it got trimmed down, the GZ tools package contained
> tree and Mercurial (plus a pile of other stuff).  I find tree an excellent 
> tool
> when exploring a new file system, and I was using Mercurial to manage various
> scripts which logically belong in the GZ alone.  Other folks would no doubt
> like to add their own bits and pieces...
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Automatically start znapzend on reboot

[Jorge Schrauwen]

I usually import the manifest manually and enable the requiems services. After 
everything is running properly I use svccfg export to drop a enabled copy into 
/opt/custom/smf.

~ sjorge 

> On 16 Jan 2018, at 20:17, Sven Kirmess  wrote:
> 
> The znapzend package installs a manifest under 
> /opt/tools/lib/svc/manifest/znapzend.xml, which is not imported on system 
> boot. What's the correct way to automatically start znapzend on reboot?
> 
>  - Copy the manifest to /opt/custom/smf/?
>  - Symlink the manifest to /opt/custom/smf/?
>  - Create a manifest in /opt/custom/smf/ that imports the manifest from 
> /opt/tools/lib/svc/manifest/?
> 
> # pkg_info -L znapzend
> Information for znapzend-0.15.3:
> 
> Files:
> /opt/tools/bin/znapzend
> /opt/tools/bin/znapzendzetup
> /opt/tools/bin/znapzendztatz
> /opt/tools/lib/ZnapZend.pm
> /opt/tools/lib/ZnapZend/Config.pm
> /opt/tools/lib/ZnapZend/Time.pm
> /opt/tools/lib/ZnapZend/ZFS.pm
> /opt/tools/man/man1/znapzend.1.gz
> /opt/tools/man/man1/znapzendzetup.1.gz
> /opt/tools/man/man1/znapzendztatz.1.gz
> /opt/tools/lib/svc/manifest/znapzend.xml
> 
> smartos-discuss | Archives  | Modify Your Subscription 




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] exploring various NAT stuff for possible use in SmartOS

[Jorge Schrauwen]

Hi Lonnie, 

I wrote the page on docu.blackdot.be, you can just run the ipf and ipnat
inside a 'router' zone.
That zone can then also run dnsmasq or simular to hand out the DHCP
leases and do DNS forwarding. 

You can then still add all other zones and one interface in the 'router'
zone to and etherstub. The other zone will then just get there address
from the 'router' zone if you configure them like mentioned in Brians
message. 

Regards 

Jorge

On 2017-11-03 14:56, Lonnie Cumberland wrote:

> Greetings All, 
> 
> Since my recent entry into the world of Illumos and in particular, SmartOS 
> which I REALLY think is awesome by the way, I an playing around with 
> different zone implementations and running a few VMs which led to a question. 
> 
> I am wondering if an internal NAT can be setup to provide to provide DHCP, 
> DNS, etc.. to dynamic zone VMs and wanted to ask the community what thoughts 
> and experiences you have on this? 
> 
> I started looking at pfsense and VyOS as possible off-the-shelf solutions and 
> am exploring this possibility. 
> 
> On a side note, the test bed network is a cable modem NAT for a local LAN of 
> which I have some physical machines. Once of them is for playing around with 
> SmartOS which I would like to setup a NAT zone to handle the other zones when 
> created. 
> 
> I did also run across these posts that may be of interest to you: 
> 
> https://wiki.smartos.org/display/DOC/NAT+using+Etherstubs 
> 
> https://docu.blackdot.be/snipets/solaris/smartos-nat   (This one if really 
> interesting) 
> 
> https://gist.github.com/baetheus/5e1e5ab1eb68fae3490d 
> 
> https://timboudreau.com/blog/smartos/read 
> 
> http://www.scalingbits.com/book/export/html/479 
> 
> Anyway, thought that I would share these links and perhaps hear back from 
> what others are doing in SmartOS. 
> 
> Thanks and have a great day, 
> Lonnie 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Can a delegated dataset be removed from a zone

[Jorge Schrauwen]

Hi Kevin, 

You should be able to remove it using zonecfg -z uuid 

Be sure the zone is not running when you do this, I'm not near a
computer at the moment so I can't give a proper example. 

But man zonecfg should get you there. 

Regards 

Jorge

On 2017-11-01 13:38, Kevr wrote:

> Hi 
> 
> Can anybody please give an example of how to remove a delegated dataset from 
> a zone? 
> 
> Thanks in advance for any help. 
> 
> Kevin Ratcliffe 
> 
> Sent from ProtonMail [1] 
> 
> SMARTOS-DISCUSS | Archives [2] [3] | Modify [4] Your Subscription
> [5]
 

Links:
--
[1] https://protonmail.ch
[2] https://www.listbox.com/member/archive/184463/=now
[3] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[4]
https://www.listbox.com/member/?;
[5] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Add tags to nic

[Jorge Schrauwen]

Not near a box right now to look up the correct command, but check out" 
nictagadm


---
~ sjorge

On 2017-10-09 19:07, Matthias Teege wrote:

Hi,

I'm using SmartOS in an VM for testing.  During the setup SmartOS
configured a nic with the tag "admin".  I've added another NIC to the
VM which I would use for SmartOS zones.  How do I assign a "tag" to
the new interfaces?

 # dladm show-phys -m
 LINK SLOT ADDRESSINUSE CLIENT
 vioif0   primary  54:52:a:fe:0:c yes  vioif0
 vioif1   primary  54:52:a:2:a:e  yes  vioif1

How can I list the "tags" of a nic? Dladm shows no vnics at all.

 # dladm show-vnic
 #

Thanks
Matthias




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Newbie to SmartOS

[Jorge Schrauwen]

Don't let the 64G number scare you, 

Depending on your performance needs it works fine with less, I had it
running slowish on 16G and pretty alright on 24G in a test setup. 

Regards 

Jorge

On 2017-08-04 20:40, Michael Cooper wrote:

> Yes I know, I already found that out you have to go to joyent triton to get 
> open source version however it requires 64 gb of RAM I have 4 servers with 
> only 32 gb of RAM so it's out for now 
> 
> On Aug 4, 2017 2:37 PM,  wrote:
> 
>> something tells me that triton.org [1] isn't where we should be looking ...
>> 
>> - On Aug 4, 2017, at 1:22 PM, Toens Bueker 
>> toens.bue...@lists0903.nurfuerspam.neuroserve.de wrote:
>> 
>>> Michael Cooper  wrote:
>>> 
 Very New to SmartOS so far I really like it very much. I
 do have a few questions though. I installed this on a usb and fired
 up a Dell server every is fine with that. How do I add another node
 to this? I believe the First Node is configured as the head node
 correct?
>>> 
>>> It seems, that you're looking for Triton (http://www.triton.org/)
>>> which is basically an "application" on top of smartos
>>> (https://github.com/joyent/smartos-live [2]), providing services for
>>> setting up a public or private cloud. There is a separate mailinglist
>>> for that sdc-disc...@lists.smartos.org
>>> (https://www.listbox.com/member/archive/247449/sort/time_rev/ [3]).
>>> 
>>> Smartos is the "hypervisor" used by Triton. If you want to get Triton
>>> up and running, you should probably start reading here:
>>> https://docs.joyent.com/private-cloud/install/download [4]
>>> 
>>> If you want to try out Smartos without Triton, you should probably
>>> start reading here:
>>> https://wiki.smartos.org/display/DOC/Download+SmartOS [5].
>>> 
>>> Kind regards,
>>> Toens
>>> --
>>> There is no safe distance.
>>> 
>> 
> 
> SMARTOS-DISCUSS | Archives [6] [9] | Modify [10] Your Subscription
> [11]
 

Links:
--
[1] http://triton.org
[2] https://github.com/joyent/smartos-live
[3] https://www.listbox.com/member/archive/247449/sort/time_rev/
[4] https://docs.joyent.com/private-cloud/install/download
[5] https://wiki.smartos.org/display/DOC/Download+SmartOS
[6] https://www.listbox.com/member/archive/184463/=now
[7] https://www.listbox.com/member/archive/rss/184463/29197591-a2127e31
[8] https://www.listbox.com/member/?;
[9] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[10]
https://www.listbox.com/member/?;
[11] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] [FLAG DAY] sdc-docker, sdc-imgapi, cn-agent for Triton docker images changes

[Jorge Schrauwen]

Cool, thanks for confirming.
I'm not using any docker containers due to the lack of v2 stuff.

If there is no change there, I shouldn't wast time on giving it another 
go.


Regards

Jorge


On 2017-07-24 23:19, Todd Whiteman wrote:

Hey Jorge,

Vanilla SmartOS users should not be affected - SmartOS images and
zones are unchanged.

For those using docker images on SmartOS without sdc-docker (i.e.
importing docker images directly via imgadm), imgadm has not changed,
so it will continue to only support registry v1 images, c.f.:
https://github.com/joyent/smartos-live/issues/644

I have not done any work on imgadm to support registry v2, but the
underlying libraries (node-imgmanifest and
node-docker-registry-client) do support registry v2, if anyone's
wanting to take a shot at it :)

Cheers,
Todd

On 2017-07-24 1:21 PM, Jorge Schrauwen wrote:

Hi Todd,

How does this effect us vanilla SmartOS users?
Does this mean we can or must now also use v2 repositories with 
imgadm?


Regards

Jorge



On 2017-07-24 21:24, Todd Whiteman wrote:

Hello All,

If your not running Triton docker services, then you can ignore the
rest of this email.

For those using Triton docker, we have upgraded our support for 
docker

images to support the latest docker registry v2 formats, and we've
removed support for docker registry v1.

In order to have a functioning docker service, on your next update,
you must upgrade these three components together:
  docker
  imgapi
  cn-agent

Here is the relevant RFD and ticket, for those that are curious:
https://github.com/joyent/rfd/blob/master/rfd/0057/README.md
https://smartos.org/bugview/DOCKER-929

Cheers,
Todd







---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] [FLAG DAY] sdc-docker, sdc-imgapi, cn-agent for Triton docker images changes

[Jorge Schrauwen]

Hi Todd,

How does this effect us vanilla SmartOS users?
Does this mean we can or must now also use v2 repositories with imgadm?

Regards

Jorge



On 2017-07-24 21:24, Todd Whiteman wrote:

Hello All,

If your not running Triton docker services, then you can ignore the
rest of this email.

For those using Triton docker, we have upgraded our support for docker
images to support the latest docker registry v2 formats, and we've
removed support for docker registry v1.

In order to have a functioning docker service, on your next update,
you must upgrade these three components together:
  docker
  imgapi
  cn-agent

Here is the relevant RFD and ticket, for those that are curious:
https://github.com/joyent/rfd/blob/master/rfd/0057/README.md
https://smartos.org/bugview/DOCKER-929

Cheers,
Todd




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Checking in on Ryzen

[Jorge Schrauwen]

Hi Robert,

Out of interest, by 'SmartOS runs well' do you mean all of SmartOS or 
everything except QEMU/KVM?


Regards

Jorge



On 2017-07-13 06:42, Robert Mustacchi wrote:

On 7/12/17 20:28 , Patrick O'Sullivan via smartos-discuss wrote:

I had seen some earlier issues with running SmartOS on AMD Ryzen. Has
anyone gotten to what one might call success, or do others perhaps 
have

plans for the server platform (Epyc)?


Hi Patrick,

Working on making sure that SmartOS runs well on the epyc platform is
definitely something that we care about and is something we're working
on in the background.

Robert




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] ANNOUNCEMENT OmniOS Community Edition - OmniOSce r151022h

[Jorge Schrauwen]

Congrats guys! May many releases follow!



On 2017-07-12 17:32, Tobias Oetiker wrote:

# OmniOS Community Edition

On April 21st 2017, OmniTI announced that they would suspend active
development of OmniOS and support contracts would not be renewed.

While this announcement left many users stunned, others focused more
on the fact that OmniTI in their announcement also expressed the hope
that "the community" would take up further development of the OS. 14
weeks later, OmniOS Community Edition is a reality.

Andy Fiddaman (www.citrus-it.net), Tobias Oetiker (www.oetiker.ch) and
Dominik Hassler have spent some quality time setting up the systems
and procedures allowing us to take over maintenance and development of
OmniOS. In this endeavour we were supported by many. Special thanks to
Stefan Husch (www.qutic.com), Peter Tribble (www.petertribble.co.uk),
Dan McDonald and Theo Schlossnagle (www.circonus.com).

We have forked the OmniOS repos and pulled in bugfixes and security
fixes that have been published since the release of OmniOS r151022.
After setting up our own package repository and updating the build
infrastructure, we are finally ready to go public. We are following
the established OmniOS release naming scheme by releasing


## OmniOSce r151022h, 12th July 2017

The new release contains the following fixes:

- expat updated to version 2.2.1 (fixes CVE-2017-9233)
- openssl updated to version 1.0.2l
- curl updated to version 7.54.1
- bind updated to version 9.10.5-P3
- p7zip updated to fix CVE-2016-9296
- web/ca-bundle updated to include OmniOSce Certificate Authority 
certificate


`uname -a` shows omnios-r151022-f9693432c2 (no change in this release)

Our work does not stop here though. First we are committed to quickly
releasing updates for r151022 as the need arises. We are also working
towards releasing r151024 on schedule. To that end, we have already
updated the bloody environment with all the latest goodies from
upstream illumos and joyent-lx repositories.

OmniOS community edition hosts its sources on
https://github.com/omniosorg/ and if you want to get in touch, you can
find us on https://gitter.im/omniosorg/Lobby


## Release Schedule

The intention is for new stable releases to continue to come out every
26 weeks. Interim, "weekly" updates to stable follow a fixed schedule
denoted by letters, one per week. Weekly releases are made as needed,
so there may not be a release each week. The first release of a new
stable version is synonymous with weekly release "a", though the
letter is not used.

During the intervals between stable releases, Bloody moves forward
rapidly, picking up changes from upstream illumos-gate and
illumos-joyent as well as updating various userland packages. In
general, upstream merges will be performed on a Thursday/Friday each
week and weekly releases will be published on a Monday.

Bloody releases will be published on an ad-hoc basis but may be as
frequent as every week.

Security fixes are excluded from the schedule and handled with
priority as they occur.


## How to Upgrade

All OmniOS packages are signed and the pkg installer is configured to
only allow trusted sources for the core packages. In order to upgrade
to the new OmniOS community edition, you have to let your box know
that the updates will be coming from a new trusted source. This means
you will have to import our CA certificate into your system.

1. Get a copy of the new certificate

```
# /usr/bin/wget -P /etc/ssl/pkg \
https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem
```

2. Check the certificate fingerprint

```
# /usr/bin/openssl x509 -fingerprint \
-in /etc/ssl/pkg/omniosce-ca.cert.pem -noout
```

`8D:CD:F9:D0:76:CD:AF:C1:62:AF:89:51:AF:8A:0E:35:24:4C:66:6D`


3. Change the publisher to our new repo

```
# /usr/bin/pkg set-publisher -P \
   -G https://pkg.omniti.com/omnios/r151022/ \
   -g https://pkg.omniosce.org/r151022/core/ omnios
```

4. For each native zone (if you have any), run

```
# /usr/bin/pkg -R  set-publisher -P \
   -G https://pkg.omniti.com/omnios/r151022/ \
   -g https://pkg.omniosce.org/r151022/core/ omnios
```

(get a list of all your zones by running `zoneadm list -cv` for the
``, add `/root` to the PATH given in the list.)


5. Install the new ca-bundle containing our new CA

```
# /usr/bin/pkg update -rv web/ca-bundle
```

6. Remove the CA file imported by hand

```
# rm /etc/ssl/pkg/omniosce-ca.cert.pem
```

7. Finally update as usual

```
# /usr/bin/pkg update -rv
```


## About OmniOS Community Edition Association

OmniOS Community Edition Association (OmniOSce) is a Swiss
association, dedicated to the continued support and release of OmniOS
for the benefit of all parties involved. The board of OmniOSce
controls access to the OmniOS CA. Current board members are: Tobias
Oetiker (President), Andy Fiddaman (Development), Dominik Hassler
(Treasurer).


## About Citrus-IT

Citrus IT is a UK company that provides a managed email service
platform to companies around 

Re: [smartos-discuss] DNS server in zone

[Jorge Schrauwen]

For every IP you want to listen on add a --listen-address flag to the
command line or if you have a config, add it there. 

You can have multiple of those. 

Regards 

Jorge

On 2017-05-30 16:00, the outsider wrote:

> And how do i do that ? 
> 
> Problem is that helpfiles and most forums show different ways to "bind" and I 
> am lost 
> 
> VAN: Jorge Schrauwen [mailto:sjorge...@blackdot.be] 
> VERZONDEN: dinsdag 30 mei 2017 15:37
> AAN: smartos-discuss@lists.smartos.org
> CC: the outsider <openindi...@out-side.nl>
> ONDERWERP: Re: [smartos-discuss] DNS server in zone 
> 
> Have you tried listening on the IP instead of using the default 
> bind-interface thing? 
> 
> I had issues with dnsmasq that.
> 
> Regards 
> 
> Jorge 
> 
> On 2017-05-30 14:31, the outsider wrote:
> 
>> I try to get DNSMASQ running inside a plain SmartOS zone with 3 nics. 
>> 
>> Each nic is connected to a switchport and each switchport has its own VLAN 
>> defined. 
>> 
>> There is no VLAN config on SmartOS , nor on the zone itself. 
>> 
>> These nics are defined as follows: 
>> 
>> [ 
>> 
>> { 
>> 
>> "interface": "net0", 
>> 
>> "mac": "92:dd:b6:c5:20:60", 
>> 
>> "nic_tag": "admin", 
>> 
>> "gateway": "192.168.120.1", 
>> 
>> "gateways": [ 
>> 
>> "192.168.120.1" 
>> 
>> ], 
>> 
>> "netmask": "255.255.255.0", 
>> 
>> "ip": "192.168.120.2", 
>> 
>> "ips": [ 
>> 
>> "192.168.120.2/24" 
>> 
>> ], 
>> 
>> "dhcp_server": "1", 
>> 
>> "allow_dhcp_spoofing": true, 
>> 
>> "allow_ip_spoofing": true, 
>> 
>> "primary": true 
>> 
>> }, 
>> 
>> { 
>> 
>> "interface": "net1", 
>> 
>> "mac": "92:dd:b6:c5:20:61", 
>> 
>> "nic_tag": "nicp4r", 
>> 
>> "netmask": "255.255.255.0", 
>> 
>> "ip": "192.168.140.2", 
>> 
>> "ips": [ 
>> 
>> "192.168.140.2/24" 
>> 
>> ], 
>> 
>> "dhcp_server": "1", 
>> 
>> "allow_dhcp_spoofing": true, 
>> 
>> "allow_ip_spoofing": true 
>> 
>> }, 
>> 
>> { 
>> 
>> "interface": "net2", 
>> 
>> "mac": "92:dd:b6:c5:20:62", 
>> 
>> "nic_tag": "demo", 
>> 
>> "netmask": "255.255.255.0", 
>> 
>> "ip": "192.168.141.2", 
>> 
>> "ips": [ 
>> 
>> "192.168.141.2/24" 
>> 
>> ], 
>> 
>> "dhcp_server": "1", 
>> 
>> "allow_dhcp_spoofing": true, 
>> 
>> "allow_ip_spoofing": true 
>> 
>> } 
>> 
>> ] 
>> 
>> It all works from time to time, but it lags and stalls a lot. 
>> 
>> So I have 3 subnets: 
>> 
>> Net0 -> 192.168.120.x 
>> 
>> Net1 -> 192.168.140.x 
>> 
>> Net2 -> 192.168.141.x 
>> 
>> Sometimes it all works great but after a few hours people start complaining 
>> about not getting an IP-address. 
>> 
>> Has anyone experience with this setup ?
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Docker support in smartos

[Jorge Schrauwen]

Lastest I am aware of is that only the v1 repositories work with vanilla
smartos. 

I think most interesting things have now moved to v2 repositories.
Triton does handle does with a helper service IIRC. But I don't use
docker my self since the only think I'd use is not in a v1 repo. 

Hopefully someone with more experience will be along shortly. 

Regards 

Jorge

On 2017-05-17 11:23, Tiraen wrote:

> Very good question 
> 
> would also like to clarify docker status 
> 
> 2017-05-17 12:19 GMT+03:00 Paolo Marcheschi :
> 
>> Hi
>> How is the situation with docker support ?
>> Is it still broken ?
>> 
>> Thank you
>> 
>> Paolo
> 
> -- 
> 
> With best regards,
> 
> Vyacheslav Yakushev,
> 
> Unix system administrator
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Saltstack disappeared from pkgin for GZ

[Jorge Schrauwen]

Pretty much that, I have a full pkgbuild zone.
With a small overlay repository 
(https://github.com/sjorge/pkgsrc-blackdot which has a few tweaks to the 
salt package)


To be fair a few of those changes should probably get upstreamed.

@jperkin, do you accept a PR against joyent pkgsrc git repo?

I just upload the small selection I build as the other stuff should 
already be available from the main repository.




On 2017-04-25 21:15, Jonathan Perkin wrote:

* On 2017-04-25 at 19:12 BST, Filip Chabik wrote:

On Sun, Apr 16, 2017 at 4:53 PM, Jorge Schrauwen 
<sjorge...@blackdot.be> wrote:

> This may not be workable for you but...
> I have a separate salt (targetting the latest salt release) repo that I use
> and track the current LTS release for x64_86 both base64 and tools variants
> here:
> https://pkg.blackdot.be/

Some time ago I raised topic about contributing packages directly to
SmartOS[1]. I prefer this way over heading to your own/separate
repository, though I do understand that sometimes it's simply not
applicable (for example some custom nginx module needs that are not
necessarily needed for majority of use cases etc.). Either way --
would you mind sharing you workflow for building and properly signing
packages? The GPG part was mostly difficult for me to get right and
have packages properly signed.


The instructions here should work:

  https://github.com/joyent/pkgsrc/wiki/pkgdev:signing

If not let me know.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Saltstack disappeared from pkgin for GZ

[Jorge Schrauwen]

*Jorge, jikes autocorrect is a *bleep*

On 2017-04-16 16:53, Jorge Schrauwen wrote:

This may not be workable for you but...
I have a separate salt (targetting the latest salt release) repo that
I use and track the current LTS release for x64_86 both base64 and
tools variants here:
https://pkg.blackdot.be/

I have had report that using the latest LTS repo with newer tools
release also works as it just adds a package or two. YMMV.

Regards

Hirge



On 2017-04-16 16:17, Paul Sture wrote:

I have just upgrade one of my Global Zones to 2017Q1 and see that Salt
is missing.

It was in 2016Q3 and 2016Q4

Compare the following for confirmation:

https://pkgsrc.joyent.com/packages/SmartOS/2016Q3/tools/All/ contains
salt-2016.3.3.tgz

https://pkgsrc.joyent.com/packages/SmartOS/2016Q4/tools/All/ contains
salt-2016.3.3.tgz

https://pkgsrc.joyent.com/packages/SmartOS/2017Q1/tools/All/ - no salt
package

Intentional or oversight?

This is a shame because I had simplified my GZ installation by using
pkgin -y in salt
by removing the need to use the bootstrap from the Saltstack site.

Yes, I am aware of Jorge Schrauwen's bootstrap solution at
https://gist.github.com/sjorge/6f0b61d825907fb828890e0c504a2870 but
thought the solution
I was working towards as a simplification.

What does the panel think?




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Saltstack disappeared from pkgin for GZ

[Jorge Schrauwen]

This may not be workable for you but...
I have a separate salt (targetting the latest salt release) repo that I 
use and track the current LTS release for x64_86 both base64 and tools 
variants here:

https://pkg.blackdot.be/

I have had report that using the latest LTS repo with newer tools 
release also works as it just adds a package or two. YMMV.


Regards

Hirge



On 2017-04-16 16:17, Paul Sture wrote:

I have just upgrade one of my Global Zones to 2017Q1 and see that Salt
is missing.

It was in 2016Q3 and 2016Q4

Compare the following for confirmation:

https://pkgsrc.joyent.com/packages/SmartOS/2016Q3/tools/All/ contains
salt-2016.3.3.tgz

https://pkgsrc.joyent.com/packages/SmartOS/2016Q4/tools/All/ contains
salt-2016.3.3.tgz

https://pkgsrc.joyent.com/packages/SmartOS/2017Q1/tools/All/ - no salt
package

Intentional or oversight?

This is a shame because I had simplified my GZ installation by using
pkgin -y in salt
by removing the need to use the bootstrap from the Saltstack site.

Yes, I am aware of Jorge Schrauwen's bootstrap solution at
https://gist.github.com/sjorge/6f0b61d825907fb828890e0c504a2870 but
thought the solution
I was working towards as a simplification.

What does the panel think?




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] sysinfo script modification question

[Jorge Schrauwen]

In my case it is always the first onboard (as in soldered onto the 
mainboard) nic.


---
~ sjorge

On 2017-04-04 13:39, Paul Sture wrote:

On 4 Apr 2017, at 8:37, Dale Ghent wrote:


I have SMCI servers that have mangled or all-zero UUIDs as well.

By "mangled", SMCI has made the extraordinarily poor choice on several 
of their X10 platforms to set the first 4 fields to 0 and the last 48 
bits to the MAC address of one of the on-board ethernet PHYs, in an 
apparent "good enough" approach to UUID generation at the factory:




This sets off an alarm bell - what happens if the NIC supplying the
MAC gets replaced?




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] sysinfo script modification question

[Jorge Schrauwen]

The ones currently still running SmartOS:
- A1SAi-2550F (X10 IIRC) -> gives all 0
- X9DRi-LN4F+ (X9) -> seems to be the mac, never noticed before

[root@core ~]# smbios | grep -i uuid
  UUID: ----002590f15506
[root@core ~]# dladm show-phys -m
LINK SLOT ADDRESSINUSE CLIENT
igb0 primary  a0:36:9f:6e:ba:6a  yes  igb0
igb1 primary  0:25:90:f1:55:6yes  trunk0-igb1
igb2 primary  0:25:90:f1:55:6yes  trunk0-igb2
igb3 primary  0:25:90:f1:55:6yes  trunk0-igb3
igb4 primary  0:25:90:f1:55:6yes  trunk0-igb4


---
~ sjorge

On 2017-04-04 08:37, Dale Ghent wrote:

I have SMCI servers that have mangled or all-zero UUIDs as well.

By "mangled", SMCI has made the extraordinarily poor choice on several
of their X10 platforms to set the first 4 fields to 0 and the last 48
bits to the MAC address of one of the on-board ethernet PHYs, in an
apparent "good enough" approach to UUID generation at the factory:

[daleg@xenon]~$ smbios | grep -i uuid
  UUID: ----0cc47a09b5f2
[daleg@xenon]~$ dladm show-phys -m
LINK SLOT ADDRESSINUSE CLIENT
igb1 primary  c:c4:7a:9:b5:f3no   --
igb0 primary  c:c4:7a:9:b5:f2yes  igb0
igb3 primary  c:c4:7a:9:b5:f5no   --
igb2 primary  c:c4:7a:9:b5:f4no   --

[daleg@devohat]~$ smbios | grep -i uuid
  UUID: ----0cc47a7b58d8
[daleg@devohat]~$ dladm show-phys -m
LINK SLOT ADDRESSINUSE CLIENT
igb0 primary  c:c4:7a:7b:58:d8   yes  igb0
igb1 primary  c:c4:7a:7b:58:d9   no   --
ixgbe0   primary  c:c4:7a:7b:5c:be   yes  ixgbe0
ixgbe1   primary  c:c4:7a:7b:5c:bf   yes  ixgbe1

How widespread this practice is throughout their product line? I'm not
sure. It might work from a practical standpoint insofar as it's a UUID
that can be used to identify a particular piece of iron, but it does
seem extraordinarily sloppy to not bother with filling out the first
80 bits which comprise the first 4 fields, thus reducing a 128bit UUID
to a 48bit one. It also means that these really aren't UUIDs in
spirit, because one could predict the UUID of a given box based only
on observed or even guessed MAC addresses.

/dale


On Apr 4, 2017, at 2:01 AM, Jorge Schrauwen <jo...@blackdot.be> wrote:

It's usually a bit and miss to be honest. I only have one of the 
machines I run smartos on report a UUID that is not all 0.
Most of them are SuperMicro too, I guess it is more of a OEM BIOS 
verder specific thing, I think they were all AMI.





On 2017-04-03 23:42, Robert Mustacchi wrote:

On 4/3/17 0:22 , 강경원 wrote:

Hello.
We are testing SDC with same SMBIOS uuid servers.
We recommend that you talk to your hardware vendor and have them 
provide

tooling to fix the server's UUID. If they have the same UUID, they've
not properly implemented the SMBIOS spec (though it's far from the 
first

time we've heard of this).
So we tried to modify images's sysinfo script to test and after 
modifing the

sysinfo, the fake uuid can be created successfully and can be setup.
But when we try to reboot the node, below error message is shown and 
rebooting

is not working.
The only thing that we can do is ipmi power reset.
How can we avoid the errors?
 svc.startd: Killing user processes.
WARNING: Error writing ufs log state
WARNING: ufs log for /usr changed state to Error
WARNING: Please umount(1M) /usr and run fsck(1M)

Given what little information we have to work on, I'd suggest you
review
your procedure for building and modifying the live image for how you
updated sysinfo to your custom version. Without knowing what you've
done
or not done or how you've done it, it's hard to suggest actionable
steps
to take.
Robert









---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] sysinfo script modification question

[Jorge Schrauwen]

It's usually a bit and miss to be honest. I only have one of the 
machines I run smartos on report a UUID that is not all 0.
Most of them are SuperMicro too, I guess it is more of a OEM BIOS verder 
specific thing, I think they were all AMI.





On 2017-04-03 23:42, Robert Mustacchi wrote:

On 4/3/17 0:22 , 강경원 wrote:

Hello.

We are testing SDC with same SMBIOS uuid servers.


We recommend that you talk to your hardware vendor and have them 
provide

tooling to fix the server's UUID. If they have the same UUID, they've
not properly implemented the SMBIOS spec (though it's far from the 
first

time we've heard of this).

So we tried to modify images's sysinfo script to test and after 
modifing the

sysinfo, the fake uuid can be created successfully and can be setup.

But when we try to reboot the node, below error message is shown and 
rebooting

is not working.

The only thing that we can do is ipmi power reset.

How can we avoid the errors?

  svc.startd: Killing user processes.

WARNING: Error writing ufs log state
WARNING: ufs log for /usr changed state to Error
WARNING: Please umount(1M) /usr and run fsck(1M)


Given what little information we have to work on, I'd suggest you
review
your procedure for building and modifying the live image for how you
updated sysinfo to your custom version. Without knowing what you've
done
or not done or how you've done it, it's hard to suggest actionable
steps
to take.

Robert




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Available images status and upkeep

[Jorge Schrauwen]

I mostly deploy base64 images and have a bootstrap script that setup 
salstack.

https://gist.github.com/sjorge/6f0b61d825907fb828890e0c504a2870

It works on a compute node, base64 image (not tested others) and 
ubuntu/centos LX images if they are new enough.


As long as the minion is know on my salt master a few minutes after 
creation I end up with the server setup how I wanted.


I have also played around with having this work masterless and that also 
works with a few tweaks.
So I can just make it fetch a small tarball with states and assemble 
itself from that.


Regards

Jorge

On 2017-03-09 23:38, Jonathan Perkin wrote:

* On 2017-03-09 at 19:19 GMT, Will Beazley wrote:


Might it make sense to have some middle ground (maybe super-sparse)
image and then have blessed "recipes" by some means (not implying
Chef) and after install get them to their pre-install state?


This is something I have planned, and have rough notes for, mainly
from my own setups of e.g. mail or www or SMB servers.  The aim is to
consolidate them into a bunch of HOWTOs on the pkgsrc wiki, with
simple steps to take you from a base or minimal image to a working
production server.

If anyone has written up their own setups then please send them to me
and I'll collate and publish them.

Another thing worth mentioning is that there are third-party image
server such as https://datasets.at/ and it'd be great to see community
supported images that are regularly updated, especially for esoteric
use cases.

Cheers,





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Reboot GZ

[Jorge Schrauwen]

I already have apmd running, my openbsd kvm still ignores it. That might
be because it has 2 vvpu's though.
So if you are running OpenBSD somewhere... check if it works properly to
make sure :) 

Regards 

Jorge

On 2017-01-31 19:17, Tamás Gérczei wrote:

> @Jorge: it does, provided apmd is running... 
> 
> tgerczei@router (~) $ grep apm /etc/rc.conf.local
> apmd_flags=""   # we need ACPI triggers handled for shutdown
> 
> Yours,
> Tamás
> 
> On 2017-01-31 16:23, Jorge Schrauwen wrote: 
> 
> I usually used: 
> 
> shutdown -g0 -i6 -y 
> 
> If you replace -i6 with -i5 it will do a graceful shutdown. 
> 
> Do note for KVM, that the gues OS needs to properly handle ACPI_SHUTDOWN 
> call, OpenBSD for example does not! 
> 
> Regards 
> 
> Jorge 
> 
> On 2017-01-31 16:20, Gjermund Gusland Thorsen wrote: Did you try: reboot? 
> 
> G 
> 
> On 31 Jan, 2017, at 16:17, John Barfield <john.barfi...@bissinc.com> wrote: 
> 
> Greetings, 
> 
> I've read somewhere in IRC about the correct 'init' command that will 
> gracefully shutdown all KVM's & Zones in the GZ without simply killing them 
> and now I can't seem to find it. 
> 
> Could someone please post it here? I need to upgrade platform images over the 
> next few days and don't want the Windows/Linux VM's to be killed by the 
> reboot process. 
> 
> Thanks! 
> 
> JOHN BARFIELD 
> ENGINEERING AND STUFF 
> 
> M: +1 (214) 425-0783  O: +1 (214) 506-8354  
> john.barfi...@bissinc.com 
> 
>  
> 4925 Greenville Ave, Ste 900 
> Dallas, TX 75206 
> 
> For Support Requests: 
> http://support.bissinc.com [1] or supp...@bissinc.com 
> 
> http://www.listbox.com

 SMARTOS-DISCUSS | Archives [2] [3] | Modify [4] Your 
Subscription
 [5]

 

Links:
--
[1] http://support.bissinc.com/
[2] https://www.listbox.com/member/archive/184463/=now
[3] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[4]
https://www.listbox.com/member/?;
[5] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Reboot GZ

[Jorge Schrauwen]

I usually used: 

shutdown -g0 -i6 -y 

If you replace -i6 with -i5 it will do a graceful shutdown. 

Do note for KVM, that the gues OS needs to properly handle ACPI_SHUTDOWN
call, OpenBSD for example does not! 

Regards 

Jorge 

On 2017-01-31 16:20, Gjermund Gusland Thorsen wrote:

> Did you try: reboot? 
> 
> G 
> 
> On 31 Jan, 2017, at 16:17, John Barfield  wrote: 
> 
>> Greetings, 
>> 
>> I've read somewhere in IRC about the correct 'init' command that will 
>> gracefully shutdown all KVM's & Zones in the GZ without simply killing them 
>> and now I can't seem to find it. 
>> 
>> Could someone please post it here? I need to upgrade platform images over 
>> the next few days and don't want the Windows/Linux VM's to be killed by the 
>> reboot process. 
>> 
>> Thanks! 
>> 
>> JOHN BARFIELD 
>> ENGINEERING AND STUFF 
>> 
>> M: +1 (214) 425-0783  O: +1 (214) 506-8354  
>> john.barfi...@bissinc.com 
>> 
>>  
>> 4925 Greenville Ave, Ste 900 
>> Dallas, TX 75206 
>> 
>> For Support Requests: 
>> http://support.bissinc.com [1] or supp...@bissinc.com
> 
 

Links:
--
[1] http://support.bissinc.com/



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] WARNING: 2016Q4 / 16.4.0 upgrade failures

[Jorge Schrauwen]

Thanks for the heads up, my stuff auto upgrade every friday at 19.00.
I just did an upgrade of openssl only everywhere to avoid breakage!


On 2017-01-27 15:42, Jonathan Perkin wrote:

To those of you running 16.4.0 images, there is an issue introduced
with the recent OpenSSL 1.0.2k update where a 'pkgin upgrade' will
render the pkg_install tools unusable, due to removing the previous
openssl package prior to installing the update.

This is completely my fault as I forgot to merge in a patch which
ensures that pkg_install statically links against openssl.

In the short term:

 - If you wish to upgrade your 16.4.0 image, perform:

$ pkg_add -U openssl

   first.  This will upgrade openssl in place, and then the remaining
   upgrades can be handled normally via pkgin.

 - If you have already broken a system with 'pkgin upgrade', things
   are a little more complicated.  For now probably the simplest fix,
   if very ugly, is (for x86_64):

$ cp /lib/64/libsunw_crypto.so.1.0.0 libcrypto.so.1.0.0
$ cp /lib/64/libsunw_ssl.so.1.0.0 libssl.so.1.0.0
$ LD_LIBRARY_PATH=. pkg_add
http://pkgsrc.joyent.com/packages/SmartOS/2016Q4/x86_64/All/openssl-1.0.2k.tgz
$ rm -f libcrypto.so.1.0.0 libssl.so.1.0.0

   If using i386/multiarch remove the '/64' path and change the URL
   accordingly.

Longer term I will put out 16.4.1 images which correctly build the
pkg_install package statically linked against OpenSSL, and add QA to
our build process to ensure we can't ship broken packages again.

Sorry for the mess,

---
~ sjorge



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Wrong disksize calculation

[Jorge Schrauwen]

I vaguely remember having this when the blocksize did not match 4k from 
a HDD pool to 16k for SSD pool.


Regards

Jorge



On 2016-11-29 10:26, Gjermund Gusland Thorsen wrote:

Did you stop the vm first?

vmadm stop 557ba0c0-b09c-678f-b1bc-a6bf2cc7b439; vmadm send
557ba0c0-b09c-678f-b1bc-a6bf2cc7b439 | ssh r...@192.168.xx.xx vmadm
receive

G

On 29 Nov, 2016, at 10:08, Kilian Ries  wrote:


Hello,

yesterday i encountered the following problem:

I wanted to move a KVM from one host to another via "vmadm send" 
command, but that ended up in the following error:


###
vmadm send 557ba0c0-b09c-678f-b1bc-a6bf2cc7b439 | ssh 
r...@192.168.xx.xx vmadm receive

Invalid value(s) for: disks.*.size
This socket is closed.
###


Reading the vmadm manual i figured out that

 • ​disks.*.size MUST be an integer
 • if you have a ZVOL, disks.*.size is depending on the size from the 
ZVOL and cannot be updated via vmadm


So i think SmartOS does somewhere calculate wrong disksizes, because 
there should always be an integer but that isn't the case in reallity, 
for example:


-> first, output of vmadm get UUID
-> second, output of zfs get all zones/UUID-disk0

###

Example 1:

vmadm get UUID​

  "disks": [
{
  ...
  "size": 117187.5,
  ...
}
  ]


volsize  114G



Example 2:

  "disks": [
{
  ...
  "size": 29296,875
  ...
}
  ]


volsize   28,6G

###


Why does SmartOS calculate wrong numbers here? These should all be 
integers ...


Thanks
Greets
Kilian


smartos-discuss | Archives  | Modify Your Subscription






---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] How to install SmartOS when memory is bigger than hard disk?

[Jorge Schrauwen]

IIRC there is no OOM killer in illumos,

There is a indepth chapter in Solaris Internals that went a bit over my 
head, but this page is a nice quick reference.
But if I remember correctly no new process will be able to be created if 
there is no available memory.


There was also something about locked memory that escapes me at the 
moment.


Regards

Jorge



On 2016-11-27 06:27, Jeffrey 'jf' Lim wrote:
On Fri, Nov 25, 2016 at 5:05 PM, Si-Qi Liu  
wrote:

Hi,


BTW, for a machine with 256G memory, is there necessary to create a 
swap zone? If so, how big should it be?




For some time now, my opinion has been to not use any swap at all for
any of my systems. Maybe I'm extreme, but when my systems fail, I want
them to fail categorically so that I know that something is wrong (I'm
assuming that there's something similar to the OOM killer on Linux)
instead of "not fail but grind along slowly". Am I wrong to think this
way?

-jf




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

It gets even weirder!

This is with the UPS attached

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product 
String
2   ehci0 pci8086,7270  2.0  .   No Product 
String
3   hubd1 hub   2.0  8087.07db   No Product 
String
4   hubd2 hub   2.0  0557.7000   No Product 
String
5   usb_mid 2 device1.1  0557.2419   No Product 
String

6   ugen0 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4

Now also note that the USB3 key with the smartos-live image is not 
detected!
It only seems to be detected if I plug it in AFTER the host has booted 
but not if it is present at boot. (As grub did load the kernel + 
boot_archive from it)


Here I switched back to everything behind the hub on a USB2 port. But I 
remembered to unplug and replug the USB3 key on the USB3 port it was not 
detecting... and poof it appeared!


INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product 
String
2   ehci0 pci8086,7270  2.0  .   No Product 
String
3   hubd1 hub   2.0  8087.07db   No Product 
String
4   hubd2 hub   2.0  0557.7000   No Product 
String
5   usb_mid 2 device1.1  0557.2419   No Product 
String

6   hubd3 hub   2.0  1a40.0101   USB 2.0 Hub
7   hubd4 hub   1.1  058f.9254   Generic USB Hub
8   usb_mid 3 device2.0  046d.c52b   USB Receiver
9   usb_mid 4 device1.1  10d5.55a2   2Port 
KVMSwitcher

a   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
b   scsa2usb0 storage   3.0  0781.5583   Ultra Fit

Notice aboce the Ultra Fit was not detected, I just unplugged and 
replugged it into the same port :/


I'm going back to the working setup now but I can play some more this 
weekend.

Perhaps you have some specific things you want me to try by then.

Regards

Jorge



On 2016-11-21 18:20, Jorge Schrauwen wrote:

Here is the data with the USB1 hub connected to a USB2 port:
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product 
String
2   ehci0 pci8086,7270  2.0  .   No Product 
String
3   hubd0 hub   1.1  058f.9254   Generic USB 
Hub
4   hubd1 hub   2.0  8087.07db   No Product 
String

5   usb_mid 0 device2.0  046d.c52b   USB Receiver
6   hubd2 hub   2.0  0557.7000   No Product 
String
7   usb_mid 1 device1.1  10d5.55a2   2Port 
KVMSwitcher
8   usb_mid 2 device1.1  0557.2419   No Product 
String


The 2nd dump is definitely something that did not happen before
because I joggled the USB ports a lot before I got the USB2 hub.

Regards

Jorge

On 2016-11-21 18:12, Jorge Schrauwen wrote:

Well now,

I just plugged the UPS into the USB2 port after unplugging the hub...
and the thing panics again!
So it was probably not the USB1 Hub on the KVM.

I'll get you the dump from earlier and the new one later tonight, will
grab dinner now.
I can do some more testing but probably not until the weekend.

Regards

Jorge


On 2016-11-21 16:46, Robert Mustacchi wrote:

On 11/21/16 7:05 , Jorge Schrauwen wrote:

USB3 Key: works fine if plugged in USB3 port!

I moved to back to the USB2 port and I plugged in the 2 devices that
were in the hub into the 2 USB3 ports but the box creating a dump 
now :s


Do you want me to send you the dump?


Yes, please that'd be very useful.

Also the output from the kernel there is also quite useful. The being
unable to get the devices to transition is quite useful in 
understanding

what happened, though there are some confusing messages. I'm a bit
surprised that we saw the slot disabling fail -- another thing to 
look into.


Thanks,
Robert


On 2016-11-21 15:57, Jorge Schrauwen wrote:

https://gist.github.com/sjorge/b7fb9113468ae538c84dd8df3b6dc92e

I noticed on the console that it complains about not being able to
bring online some of the USB stuff.
I also included the dmesg snippet from the time.

It did seem to detect the USB key so I will see if I can get that 
to

work and leave the kb in the hub connecto to usb2

On 2016-11-20 20:04, Robert Mustacchi wrote:

On 11/20/16 1:29 , Jorge Schrauwen wrote:


On 2016-11-19 17:11, Robert Mustacchi wrote:

On 11/19/16 5:14 , Jorge Schrauwen wrote:

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is 
working.

I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

Here is the data with the USB1 hub connected to a USB2 port:
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product 
String
2   ehci0 pci8086,7270  2.0  .   No Product 
String

3   hubd0 hub   1.1  058f.9254   Generic USB Hub
4   hubd1 hub   2.0  8087.07db   No Product 
String

5   usb_mid 0 device2.0  046d.c52b   USB Receiver
6   hubd2 hub   2.0  0557.7000   No Product 
String
7   usb_mid 1 device1.1  10d5.55a2   2Port 
KVMSwitcher
8   usb_mid 2 device1.1  0557.2419   No Product 
String


The 2nd dump is definitely something that did not happen before because 
I joggled the USB ports a lot before I got the USB2 hub.


Regards

Jorge

On 2016-11-21 18:12, Jorge Schrauwen wrote:

Well now,

I just plugged the UPS into the USB2 port after unplugging the hub...
and the thing panics again!
So it was probably not the USB1 Hub on the KVM.

I'll get you the dump from earlier and the new one later tonight, will
grab dinner now.
I can do some more testing but probably not until the weekend.

Regards

Jorge


On 2016-11-21 16:46, Robert Mustacchi wrote:

On 11/21/16 7:05 , Jorge Schrauwen wrote:

USB3 Key: works fine if plugged in USB3 port!

I moved to back to the USB2 port and I plugged in the 2 devices that
were in the hub into the 2 USB3 ports but the box creating a dump now 
:s


Do you want me to send you the dump?


Yes, please that'd be very useful.

Also the output from the kernel there is also quite useful. The being
unable to get the devices to transition is quite useful in 
understanding

what happened, though there are some confusing messages. I'm a bit
surprised that we saw the slot disabling fail -- another thing to look 
into.


Thanks,
Robert


On 2016-11-21 15:57, Jorge Schrauwen wrote:

https://gist.github.com/sjorge/b7fb9113468ae538c84dd8df3b6dc92e

I noticed on the console that it complains about not being able to
bring online some of the USB stuff.
I also included the dmesg snippet from the time.

It did seem to detect the USB key so I will see if I can get that to
work and leave the kb in the hub connecto to usb2

On 2016-11-20 20:04, Robert Mustacchi wrote:

On 11/20/16 1:29 , Jorge Schrauwen wrote:


On 2016-11-19 17:11, Robert Mustacchi wrote:

On 11/19/16 5:14 , Jorge Schrauwen wrote:

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is 
working.

I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No 
Product

String
2   ehci0 pci8086,7270  2.0  .   No 
Product

String
3   hubd0 hub   2.0  8087.07db   No 
Product

String
4   hubd2 hub   2.0  0557.7000   No 
Product

String
5   usb_mid 2 device1.1  0557.2419   No 
Product

String
6   hubd1 hub   2.0  1a40.0101   USB 2.0 
Hub
7   scsa2usb0 storage   2.1  0781.5583   Ultra 
Fit

8   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
9   hubd4 hub   1.1  058f.9254   Generic
USB Hub
a   usb_mid 3 device2.0  046d.c52b   USB 
Receiver

b   usb_mid 4 device1.1  10d5.55a2   2Port
KVMSwitcher
[root@mantle ~]# prtconf -dD | grep -i xhci
pci15d9,813 (pciex1912,14) [Renesas Technology Corp.
uPD720201 USB 3.0 Host Controller], instance #0 (driver name: 
xhci)


Hmm, one of the Renesas controllers, not one we've seen yet. Also
one of
the ones more often reported to be troublesome.

If you have the time, can you please plug things back into USB 3
ports,
reboot, and then run the following:

/usr/lib/xhci/xhci_portsc -v

Along with the mdb -ke '::prtusb'. Could you also check if 
there's

anything got logged about that?


I added everything to a gist for easier reading:
https://gist.github.com/sjorge/47cb7f5e14b335c3c3c382dd3daf4e4f

This is with the boot USB plugged into the first USB3 port (it 
always

works at boot, even before the xhci work)
The small USB2 hub with my keyboard (KVM) and UPS plugged in
attached to
the second USB3 port.


Thanks for the additional information. It looks like one of your 
ports

 is stuck trying to transition in the device state machine.
Unfortunately
it's a bit hard to get a mapping between the virtual ports on the
controller and the physical ports on the machine.

I'm not entirely sure why it would be stuck in that state, from the
spec
it makes it sound like it's supposed to transition that way on its 
own

without any intervention from the host.

It does look like we detected one of the devices, but for some 
reason
that fact didn't make it to the kernel

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

Well now,

I just plugged the UPS into the USB2 port after unplugging the hub... 
and the thing panics again!

So it was probably not the USB1 Hub on the KVM.

I'll get you the dump from earlier and the new one later tonight, will 
grab dinner now.

I can do some more testing but probably not until the weekend.

Regards

Jorge


On 2016-11-21 16:46, Robert Mustacchi wrote:

On 11/21/16 7:05 , Jorge Schrauwen wrote:

USB3 Key: works fine if plugged in USB3 port!

I moved to back to the USB2 port and I plugged in the 2 devices that
were in the hub into the 2 USB3 ports but the box creating a dump now 
:s


Do you want me to send you the dump?


Yes, please that'd be very useful.

Also the output from the kernel there is also quite useful. The being
unable to get the devices to transition is quite useful in 
understanding

what happened, though there are some confusing messages. I'm a bit
surprised that we saw the slot disabling fail -- another thing to look 
into.


Thanks,
Robert


On 2016-11-21 15:57, Jorge Schrauwen wrote:

https://gist.github.com/sjorge/b7fb9113468ae538c84dd8df3b6dc92e

I noticed on the console that it complains about not being able to
bring online some of the USB stuff.
I also included the dmesg snippet from the time.

It did seem to detect the USB key so I will see if I can get that to
work and leave the kb in the hub connecto to usb2

On 2016-11-20 20:04, Robert Mustacchi wrote:

On 11/20/16 1:29 , Jorge Schrauwen wrote:


On 2016-11-19 17:11, Robert Mustacchi wrote:

On 11/19/16 5:14 , Jorge Schrauwen wrote:

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is 
working.

I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No 
Product

String
2   ehci0 pci8086,7270  2.0  .   No 
Product

String
3   hubd0 hub   2.0  8087.07db   No 
Product

String
4   hubd2 hub   2.0  0557.7000   No 
Product

String
5   usb_mid 2 device1.1  0557.2419   No 
Product

String
6   hubd1 hub   2.0  1a40.0101   USB 2.0 
Hub
7   scsa2usb0 storage   2.1  0781.5583   Ultra 
Fit

8   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
9   hubd4 hub   1.1  058f.9254   Generic
USB Hub
a   usb_mid 3 device2.0  046d.c52b   USB 
Receiver

b   usb_mid 4 device1.1  10d5.55a2   2Port
KVMSwitcher
[root@mantle ~]# prtconf -dD | grep -i xhci
pci15d9,813 (pciex1912,14) [Renesas Technology Corp.
uPD720201 USB 3.0 Host Controller], instance #0 (driver name: 
xhci)


Hmm, one of the Renesas controllers, not one we've seen yet. Also
one of
the ones more often reported to be troublesome.

If you have the time, can you please plug things back into USB 3
ports,
reboot, and then run the following:

/usr/lib/xhci/xhci_portsc -v

Along with the mdb -ke '::prtusb'. Could you also check if there's
anything got logged about that?


I added everything to a gist for easier reading:
https://gist.github.com/sjorge/47cb7f5e14b335c3c3c382dd3daf4e4f

This is with the boot USB plugged into the first USB3 port (it 
always

works at boot, even before the xhci work)
The small USB2 hub with my keyboard (KVM) and UPS plugged in
attached to
the second USB3 port.


Thanks for the additional information. It looks like one of your 
ports

 is stuck trying to transition in the device state machine.
Unfortunately
it's a bit hard to get a mapping between the virtual ports on the
controller and the physical ports on the machine.

I'm not entirely sure why it would be stuck in that state, from the
spec
it makes it sound like it's supposed to transition that way on its 
own

without any intervention from the host.

It does look like we detected one of the devices, but for some 
reason
that fact didn't make it to the kernel per se. Would it be possible 
for

you to run cfgadm -al in both cases?

Sorry I don't have a more immediate answer for what's happening 
here.

 I'm not sure yet what's different about your setup from others --
though
more likely than not there's some driver bug at the root of it all.

Robert










---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

USB3 Key: works fine if plugged in USB3 port!

I moved to back to the USB2 port and I plugged in the 2 devices that 
were in the hub into the 2 USB3 ports but the box creating a dump now :s


Do you want me to send you the dump?

Regards

Jorge

On 2016-11-21 15:57, Jorge Schrauwen wrote:

https://gist.github.com/sjorge/b7fb9113468ae538c84dd8df3b6dc92e

I noticed on the console that it complains about not being able to
bring online some of the USB stuff.
I also included the dmesg snippet from the time.

It did seem to detect the USB key so I will see if I can get that to
work and leave the kb in the hub connecto to usb2

On 2016-11-20 20:04, Robert Mustacchi wrote:

On 11/20/16 1:29 , Jorge Schrauwen wrote:


On 2016-11-19 17:11, Robert Mustacchi wrote:

On 11/19/16 5:14 , Jorge Schrauwen wrote:

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is working.
I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product
String
2   ehci0 pci8086,7270  2.0  .   No Product
String
3   hubd0 hub   2.0  8087.07db   No Product
String
4   hubd2 hub   2.0  0557.7000   No Product
String
5   usb_mid 2 device1.1  0557.2419   No Product
String
6   hubd1 hub   2.0  1a40.0101   USB 2.0 
Hub

7   scsa2usb0 storage   2.1  0781.5583   Ultra Fit
8   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
9   hubd4 hub   1.1  058f.9254   Generic 
USB Hub
a   usb_mid 3 device2.0  046d.c52b   USB 
Receiver

b   usb_mid 4 device1.1  10d5.55a2   2Port
KVMSwitcher
[root@mantle ~]# prtconf -dD | grep -i xhci
pci15d9,813 (pciex1912,14) [Renesas Technology Corp.
uPD720201 USB 3.0 Host Controller], instance #0 (driver name: xhci)


Hmm, one of the Renesas controllers, not one we've seen yet. Also 
one of

the ones more often reported to be troublesome.

If you have the time, can you please plug things back into USB 3 
ports,

reboot, and then run the following:

/usr/lib/xhci/xhci_portsc -v

Along with the mdb -ke '::prtusb'. Could you also check if there's
anything got logged about that?


I added everything to a gist for easier reading:
https://gist.github.com/sjorge/47cb7f5e14b335c3c3c382dd3daf4e4f

This is with the boot USB plugged into the first USB3 port (it always
works at boot, even before the xhci work)
The small USB2 hub with my keyboard (KVM) and UPS plugged in attached 
to

the second USB3 port.


Thanks for the additional information. It looks like one of your ports
 is stuck trying to transition in the device state machine.
Unfortunately
it's a bit hard to get a mapping between the virtual ports on the
controller and the physical ports on the machine.

I'm not entirely sure why it would be stuck in that state, from the
spec
it makes it sound like it's supposed to transition that way on its own
without any intervention from the host.

It does look like we detected one of the devices, but for some reason
that fact didn't make it to the kernel per se. Would it be possible 
for

you to run cfgadm -al in both cases?

Sorry I don't have a more immediate answer for what's happening here.
 I'm not sure yet what's different about your setup from others --
though
more likely than not there's some driver bug at the root of it all.

Robert







---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

https://gist.github.com/sjorge/b7fb9113468ae538c84dd8df3b6dc92e

I noticed on the console that it complains about not being able to bring 
online some of the USB stuff.

I also included the dmesg snippet from the time.

It did seem to detect the USB key so I will see if I can get that to 
work and leave the kb in the hub connecto to usb2


On 2016-11-20 20:04, Robert Mustacchi wrote:

On 11/20/16 1:29 , Jorge Schrauwen wrote:


On 2016-11-19 17:11, Robert Mustacchi wrote:

On 11/19/16 5:14 , Jorge Schrauwen wrote:

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is working.
I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product
String
2   ehci0 pci8086,7270  2.0  .   No Product
String
3   hubd0 hub   2.0  8087.07db   No Product
String
4   hubd2 hub   2.0  0557.7000   No Product
String
5   usb_mid 2 device1.1  0557.2419   No Product
String
6   hubd1 hub   2.0  1a40.0101   USB 2.0 Hub
7   scsa2usb0 storage   2.1  0781.5583   Ultra Fit
8   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
9   hubd4 hub   1.1  058f.9254   Generic USB 
Hub
a   usb_mid 3 device2.0  046d.c52b   USB 
Receiver

b   usb_mid 4 device1.1  10d5.55a2   2Port
KVMSwitcher
[root@mantle ~]# prtconf -dD | grep -i xhci
pci15d9,813 (pciex1912,14) [Renesas Technology Corp.
uPD720201 USB 3.0 Host Controller], instance #0 (driver name: xhci)


Hmm, one of the Renesas controllers, not one we've seen yet. Also one 
of

the ones more often reported to be troublesome.

If you have the time, can you please plug things back into USB 3 
ports,

reboot, and then run the following:

/usr/lib/xhci/xhci_portsc -v

Along with the mdb -ke '::prtusb'. Could you also check if there's
anything got logged about that?


I added everything to a gist for easier reading:
https://gist.github.com/sjorge/47cb7f5e14b335c3c3c382dd3daf4e4f

This is with the boot USB plugged into the first USB3 port (it always
works at boot, even before the xhci work)
The small USB2 hub with my keyboard (KVM) and UPS plugged in attached 
to

the second USB3 port.


Thanks for the additional information. It looks like one of your ports
 is stuck trying to transition in the device state machine.
Unfortunately
it's a bit hard to get a mapping between the virtual ports on the
controller and the physical ports on the machine.

I'm not entirely sure why it would be stuck in that state, from the
spec
it makes it sound like it's supposed to transition that way on its own
without any intervention from the host.

It does look like we detected one of the devices, but for some reason
that fact didn't make it to the kernel per se. Would it be possible for
you to run cfgadm -al in both cases?

Sorry I don't have a more immediate answer for what's happening here.
 I'm not sure yet what's different about your setup from others --
though
more likely than not there's some driver bug at the root of it all.

Robert




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB 3 / xHCI beta testing

[Jorge Schrauwen]

I just upgrade one of my compute nodes.
No crashes yet, but nothing plugged into the USB3 ports is working.
I tried a USB-keyboard and a USB3 Drive.

[root@mantle ~]# mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODE  GEN  VID.PID PRODUCT
1   xhci0 pci15d9,813   3.0  .   No Product 
String
2   ehci0 pci8086,7270  2.0  .   No Product 
String
3   hubd0 hub   2.0  8087.07db   No Product 
String
4   hubd2 hub   2.0  0557.7000   No Product 
String
5   usb_mid 2 device1.1  0557.2419   No Product 
String

6   hubd1 hub   2.0  1a40.0101   USB 2.0 Hub
7   scsa2usb0 storage   2.1  0781.5583   Ultra Fit
8   ugen1 input 2.0  051d.0002
Back-UPS RS 900G FW:879.L4 .I USB FW:L4
9   hubd4 hub   1.1  058f.9254   Generic USB Hub
a   usb_mid 3 device2.0  046d.c52b   USB Receiver
b   usb_mid 4 device1.1  10d5.55a2   2Port 
KVMSwitcher

[root@mantle ~]# prtconf -dD | grep -i xhci
pci15d9,813 (pciex1912,14) [Renesas Technology Corp. 
uPD720201 USB 3.0 Host Controller], instance #0 (driver name: xhci)



I plugged everything back into the USB2 ports before leaving, so the 
output above is with the keyboard and usb key plugged into the USB2 
ports via a hub.


Regards

Jorge


On 2016-11-18 22:26, Robert Mustacchi wrote:

Hi,

We are about to wrap the initial set of USB 3.x support. If you have
 some additional cycles to perform some testing of this (regardless of
if
your system has USB 3 or not), we'd appreciate it.

If you do test it, and things are working, it'd help me if you could
share the output of the following two commands for my notes:

mdb -ke '::prtusb'
prtconf -dD | grep -i xhci

SmartOS builds:

https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.tgz
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.iso
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.usb.bz2

SmartOS debug builds:

https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.tgz
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.iso
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.usb.bz2

Thanks,
Robert




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] About install pkgin in global zone

[Jorge Schrauwen]

Any reason to not add a [ -d /opt/tools ] && export ... to the bashrc 
that ships in smartos-live?
It should not break anything but it should pick up the tools if present. 
/opt/local for example is already auto-added if it exists.


Regards

Jorge


On 2016-11-16 23:13, Jonathan Perkin wrote:

* On 2016-11-16 at 19:48 GMT, Tiraen wrote:


[root@ds821695 /opt]# gpg --recv-keys 0xDE817B8E
gpg: no keyserver known (use option --keyserver)
gpg: keyserver receive failed: bad URI


Yeh I should probably add a note about that too - the gpg shipped in
SmartOS is utterly broken, and we should probably stop doing so.  The
instructions are primarily written for other illumos distributions
where the gpg command should work.

If you want to verify the signature you'll need to do it from within
an image using gpg from pkgsrc.

Cheers,





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] About boot order vms

[Jorge Schrauwen]

There is no way to set a boot order. 

However you can get creative with a custom smf service to do this for
you. 

Regards 

Jorge

On 2016-11-14 22:17, Tiraen wrote:

> Good day, the question of such a plan:
> 
> I now reread the whole man page vmadm and found no opportunity to set the 
> boot priority VMS after restart host.
> 
> It really is not provided, or I'm not there watching?
> -- 
> 
> With best regards,
> 
> Vyacheslav Yakushev,
> 
> Unix system administrator
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Preferred admin pattern: GZ or "admin" zone?

[Jorge Schrauwen]

delegate_dataset will create a dataset zones/UUID/data that can be
managed inside the zone. (snapshots, sub datasets) 

you can cheat and use zonecfg to for example delegate an entire zpool to
a zone. (which has a lot of painful caviats -- mainly if you delete your
zone the datasets goes with it) 

doing that also removes it from the global zone, so if you try and
delegate zones dataset everything is going to break TM. 

Send from my phone 

Jorge

On 2016-10-24 21:23, Gjermund Gusland Thorsen wrote:

> Delegate zone is for when you want to keep application on a separate zpool 
> than the data, no? 
> 
> G 
> 
> On 24 Oct, 2016, at 21:07, Jorge Schrauwen <sjorge...@blackdot.be> wrote: 
> 
> Instructions for that are here: https://pkgsrc.joyent.com/install-on-illumos/ 
> 
> And yeah, delegating zones is not going to go very well. 
> 
> Regards 
> 
> Jorge
> 
> On 2016-10-24 21:07, Daniel Carosone wrote: 
> 
> You don't want to delegate /zones :-) 
> 
> You might get away with a lofs mount for some jobs, but that won't let you 
> manage zfs, snapshots, etc. 
> 
> There's now a special tools set of pkgsrc specifically for the GZ.
> 
> On 25 Oct 2016 6:03 am, "Matthew Parsons" <matt...@aspergerexperts.com> wrote:
> 
> What's the accepted/preferred method for one-off admin customizations - do we 
> manually install pkgsrc in the global zone (seems ugly and a bit less 
> secure), or create a "let me do stuff" base image and delegate the /zones 
> pool to it? 
> 
> (For starters I just want to install tmux and a few utilities that need 
> access to the full filesystem...)
 
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] X11 over VNC

[Jorge Schrauwen]

There is a vnc_password property that can be fed to vmadm during create,
does that not work?

Regards 

Jorge 

On 2016-10-23 01:48, Gjermund Gusland Thorsen wrote:

> Is there a way to set vnc_password in the zone file? 
> 
> G 
> 
> On 19 Sep, 2016, at 10:21, Peter Kelm  wrote: 
> 
> For the KVM VM in question: 
> vmadm update  vnc_password= 
> 
> Then launch the „Screen Sharing" app (e.g. by entering „screen" in Spotlight) 
> and enter the hostname or ip address of the SmartOS host (not the KVM zone) 
> followed by the port: :. You will be prompted for the 
> password set via vmadm (above) and VNC will connect. 
> 
> Alternatively you can also press Command-K in the Finder to bring up the 
> „Connect to Server" dialog, Enter „vnc://:" under 
> „Server address" and press „Connect" and OS X will launch „Screen Sharing" 
> and establish the VNC connection. As above you will be prompted for the 
> password. 
> 
> Am 19.09.2016 um 09:23 schrieb Gjermund Gusland Thorsen 
> : 
> 
> How does that work? 
> 
> On 19 Sep, 2016, at 9:14, Peter Kelm  wrote: 
> 
> No need for a third party VNC client on OS X/OSX/macOS - the builtin „Screen 
> Sharing" applications does the job nicely. To make it work you need to set a 
> „vnc_password" through vmadm, though. 
> 
> Peter 
> 
> P.S. And yes, I did use Chicken myself before… 
> 
> Am 19.09.2016 um 01:23 schrieb Gjermund Gusland Thorsen 
> : 
> 
> For example on Mac the only VNC client that actually manages to login to the 
> KVM using VNC is Chicken 2.2b2 to my knowledge. 
> 
> G
> 
> On 18 Sep, 2016, at 22:26, G B via smartos-discuss 
>  wrote: 
> 
> Yes, I'm using the internal vnc in kvm.
> 
> On Sunday, September 18, 2016 12:16 PM, Gjermund ॐ Gusland Thorsen 
>  wrote:
> 
> Are you using the internal VNC in the KVM? I believe certain VNC clients are 
> incompatible. 
> Sent from cyberspace 
> 
> On 18 Sep 2016, at 16:20, G B via smartos-discuss 
>  wrote:
> 
> I'm running SmartOS 20160818T234814Z and using freebsd-10 20160415 in a KVM.  
> I've installed a number of window managers but the mouse never works.  Has 
> anyone been able to use a window manager like WindowMaker, wmii, twm, etc., 
> over Xming? 
> 
> I tried generating an xorg.conf which typically isn't needed, but it doesn't 
> work.  Here are the contents. 
> Section "ServerLayout"
> Identifier "X.org [1] Configured"
> Screen  0  "Screen0" 0 0
> InputDevice"Mouse0" "CorePointer"
> InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
> 
> Section "Files"
> ModulePath   "/usr/local/lib/xorg/modules"
> FontPath "/usr/local/share/fonts/misc/"
> FontPath "/usr/local/share/fonts/TTF/"
> FontPath "/usr/local/share/fonts/OTF/"
> FontPath "/usr/local/share/fonts/Type1/"
> FontPath "/usr/local/share/fonts/100dpi/"
> FontPath "/usr/local/share/fonts/75dpi/"
> EndSection
> 
> Section "Module"
> Load  "glx"
> EndSection
> 
> Section "InputDevice"
> Identifier  "Keyboard0"
> Driver  "kbd"
> EndSection
> 
> Section "InputDevice"
> Identifier  "Mouse0"
> Driver  "mouse"
> Option"Protocol" "auto"
> Option"Device" "/dev/sysmouse"
> Option"ZAxisMapping" "4 5 6 7"
> EndSection
> 
> Section "Monitor"
> Identifier   "Monitor0"
> VendorName   "Monitor Vendor"
> ModelName"Monitor Model"
> EndSection
> 
> Section "Device"
> ### Available Driver options are:-
> ### Values: : integer, : float, : "True"/"False",
> ### : "String", : " Hz/kHz/MHz",
> ### : "%"
> ### [arg]: arg optional
> #Option "ShadowFB"   # []
> #Option "DefaultRefresh" # []
> #Option "ModeSetClearScreen" # []
> Identifier  "Card0"
> Driver  "vesa"
> BusID   "PCI:0:2:0"
> EndSection
> 
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor"Monitor0"
> SubSection "Display"
> Viewport   0 0
> Depth 1
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 4
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 8
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 15
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 16
> EndSubSection
> SubSection "Display"
> Viewport   0 0
> Depth 24
> EndSubSection
> EndSection
 
 http://www.listbox.com [2]
 
 http://www.listbox.com [2]
 
 Links:
 --
 [1]  http://x.org/
  http://www.listbox.com/



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] SmartOS won't install on Dell PowerEdge T130 -- Possibly USB keyboard issue?

[Jorge Schrauwen]

OK the answer is no, it does not compile on illumos/SmartOS.

But I have a hack here 
https://github.com/jclulow/vmware-sercons/issues/2
Works great with OpenBSD and FreeBSD vm.console sockets. Socat does not 
fair so well.



On 2016-10-09 13:30, Jorge Schrauwen wrote:

Hey Joshua,

Does this only compile on OSX?
I wanted to try it on a SmartOS node to see if it fixes the funky
kvm+serial issues I sometimes see with OpenBSD.
But it fails to compile with "sercons.c:194:4: error: 'struct
sockaddr_un' has no member named 'sun_len'"

Regards

Jorge


On 2016-10-09 06:15, Joshua M. Clulow wrote:
On 8 October 2016 at 21:00, Casey Bisson <casey.bis...@joyent.com> 
wrote:

Just to confirm, you’ve set your console to VGA in the grub menu?

This is from the CoaL install docs in 
https://github.com/joyent/triton, but

it applies any time you’re using a local console:

Press 'c' to go to the command line for GRUB.
grub> variable os_console vga


That applies to the _Triton_ (formerly SDC) install media.  The
standalone SmartOS image, which I believe Nick is using, defaults to
the VGA console.

Robert is hard at work on a driver for the XHCI controller (USB 3).
Hopefully we'll have something ready for serious testing soon.  Once
there's a platform image available for testing, this mailing list will
the be the first to know!

By default, the OS will redirect the console to ttyb which is fine 
for
production but needs to be changed for CoaL. While in the command 
line:


Though somewhat off-topic, if you're using COAL via VGA (i.e. without
the serial console) you're missing out!  There are several tools that
allow you to attach to the VMware Fusion serial port that COAL
includes by default; e.g.,

https://github.com/jclulow/vmware-sercons



Cheers.






---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] SmartOS won't install on Dell PowerEdge T130 -- Possibly USB keyboard issue?

[Jorge Schrauwen]

Hey Joshua,

Does this only compile on OSX?
I wanted to try it on a SmartOS node to see if it fixes the funky 
kvm+serial issues I sometimes see with OpenBSD.
But it fails to compile with "sercons.c:194:4: error: 'struct 
sockaddr_un' has no member named 'sun_len'"


Regards

Jorge


On 2016-10-09 06:15, Joshua M. Clulow wrote:
On 8 October 2016 at 21:00, Casey Bisson  
wrote:

Just to confirm, you’ve set your console to VGA in the grub menu?

This is from the CoaL install docs in 
https://github.com/joyent/triton, but

it applies any time you’re using a local console:

Press 'c' to go to the command line for GRUB.
grub> variable os_console vga


That applies to the _Triton_ (formerly SDC) install media.  The
standalone SmartOS image, which I believe Nick is using, defaults to
the VGA console.

Robert is hard at work on a driver for the XHCI controller (USB 3).
Hopefully we'll have something ready for serious testing soon.  Once
there's a platform image available for testing, this mailing list will
the be the first to know!


By default, the OS will redirect the console to ttyb which is fine for
production but needs to be changed for CoaL. While in the command 
line:


Though somewhat off-topic, if you're using COAL via VGA (i.e. without
the serial console) you're missing out!  There are several tools that
allow you to attach to the VMware Fusion serial port that COAL
includes by default; e.g.,

https://github.com/jclulow/vmware-sercons



Cheers.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Trouble starting a KVM

[Jorge Schrauwen]

Hi,

Do you have qemu_opts set? I see two -smp flags

The later one also seems wrong:
-smp cpus=2,cores=8,threads=2
probably needs to be
-smp sockets=2,cores=8,threads=2

Regards

Jorge

On 2016-10-07 20:21, Ian Collins wrote:

On 10/ 8/16 05:28 AM, Robert Mustacchi wrote:

On 10/7/16 1:35 , Ian Collins wrote:

On 10/ 7/16 04:32 PM, Robert Mustacchi wrote:

On 10/6/16 16:26 , Ian Collins wrote:

Hello,

I'm having trouble starting a KVM (which had been shut down 
cleanly).

It times out waiting for zone to transition to running. I can't see
anything obvious in the zone log except for:

+ setup_cpu_baseline
+ nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
+ prctl -P -n zone.cpu-baseline -i zone
f3384dd7-5697-63cb-b194-d53911b0bfb8
prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable 
process

found in task, project, or zone.
+ curr_base=''

Which doesn't look good.  Any ideas for further debugging?


You'll want to go take a look at the log files in
/zones//root/tmp/vm.log. At least, I think that's pretty close 
to

the path you want, which will be the QEMU log.

Alas all the logs in there are empty...

ls -l /zones/f3384dd7-5697-63cb-b194-d53911b0bfb8/root/tmp
total 20
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.console
-rw-r--r--   1 root root   0 Oct  6 23:17 vm.log
-rw-r--r--   1 root root   0 Oct  6 21:38 vm.log.0
-rw-r--r--   1 root root   0 Oct  6 21:32 vm.log.1
-rw-r--r--   1 root root   0 Oct  6 20:00 vm.log.2
-rw-r--r--   1 root root   0 Oct  6 19:56 vm.log.3
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.4
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.5
-rw-r--r--   1 root root   0 Aug 21 03:00 vm.log.6
-rw-r--r--   1 root root   0 Aug 17 06:07 vm.log.7
-rw-r--r--   1 root root   0 Aug 16 08:13 vm.log.8
-rw-r--r--   1 root root   0 Aug 15 20:00 vm.log.9
-rw-r--r--   1 root staff 72 Oct  6 23:17 vm.metadata
-rw---   1 root root   6 Aug 21 03:49 vm.pid
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.qmp
-rw-r--r--   1 root root1281 Oct  6 23:17 vm.startvm.log
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.ttyb
srwxr-xr-x   1 root root   0 Aug 21 03:50 vm.vnc


What's in the vm.startvm.log file?

The launch command:

+ [[ -x /startvm.zone ]]
+ exec /smartdc/bin/qemu-exec /smartdc/bin/qemu-system-x86_64 -m 16384
-name f3384dd7-5697-63cb-b194-d53911b0bfb8 -uuid
f3384dd7-5697-63cb-b194-d53911b0bfb8
-cpu host -smp 2 -drive
file=/dev/zvol/rdsk/zones/f3384dd7-5697-63cb-b194-d53911b0bfb8-disk0,if=virtio,index=0,media=disk
-drive file=/dev/zvol/rdsk/zones/f3
384dd7-5697-63cb-b194-d53911b0bfb8-disk1,if=virtio,index=1,media=disk
-boot order=cd -device
virtio-net-pci,mac=90:b8:d0:14:d6:21,tx=timer,x-txtimer=20,x
-txburst=128,vlan=0 -net
vnic,name=net0,vlan=0,ifname=net0,ip=192.168.42.223,netmask=255.255.255.0,gateway_ip=192.168.42.3,hostname=f3384dd7-5697-63cb-b194-d
53911b0bfb8,dns_ip0=216.146.36.113,dns_ip1=216.146.35.113 -smbios
'type=1,manufacturer=Joyent,product=SmartDC
HVM,version=7.20161004T154212Z,serial=f3384dd7-
5697-63cb-b194-d53911b0bfb8,uuid=f3384dd7-5697-63cb-b194-d53911b0bfb8,sku=001,family=Virtual
Machine' -pidfile /tmp/vm.pid -vga std -chardev socket,id=qmp,pa
th=/tmp/vm.qmp,server,nowait -qmp chardev:qmp -chardev
socket,id=serial0,path=/tmp/vm.console,server,nowait -serial
chardev:serial0 -chardev socket,id=serial
1,path=/tmp/vm.ttyb,server,nowait -serial chardev:serial1 -vnc
unix:/tmp/vm.vnc -parallel none -usb -usbdevice tablet -k en-us -smp
cpus=2,cores=8,threads=2



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Windows KVM with many cores showing high load average

[Jorge Schrauwen]

On 2016-10-06 00:48, Ian Collins wrote:

On 10/ 6/16 10:03 AM, Matthew Parsons wrote:
Have you installed the VirtIO drivers in windows? (And what version?) 
For testing I'd try disabling/removing the guest NICs and just see if 
interrupts die down.


Which version is often an issue!  There are so many out there and some
work with one version of windows and not another!  The ISO I use is
named "me-ws2012std-20130712.iso" and I've been using it for a couple
of years so its origins are lost in the mists of time.


This which version works/is best used to come up a lot.
A while ago most seem to be in agreement which was the best set. I 
managed to find it and also host it on my package repository site to not 
have it go lost:


http://pkg.blackdot.be/extras/virtio-win-0.1-49.iso

Not sure this is the same version as you mention but I had decent 
results on windows 7 and 2008 R2 (didn't have access to newer stuff)


Also (again for testing) perhaps reduce cores to the amount on a 
physical CPU socket and assign/restrict to avoid crossing NUMA 
boundries.


The problem only becomes an issue when the core number gets high, as I
said in my original post the load average almost quadruples when going
from 16 to 32 cores.

(I trust that whatever workload you're running benefits from that many 
cores, but typically I'd keep 2 or so for the 
hypervisor/management/other.)


The workload is compiling a large C and C++ code base, so the more
cores the better.

Experimenting on a smaller machine shows the build times to cores
ratios reflect those on bare metal, that is if I give the VM the full
system picture (using qemu_extra_opts) build times are about 25%
faster than giving it the number of physical cores (using vcpus).  For
example to get optimum performance on a single quad core, use "vcpus":
1, "qemu_extra_opts": "-smp cpus=1,cores=4,threads=2".

Cheers,



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] inet6 default gateway in non-global zones

[Jorge Schrauwen]

This doesn't work in an lx zone however, unless you add some glue to 
reload the rules at boot.


---
~ sjorge

On 2016-10-05 17:54, Dan McDonald wrote:
On Oct 5, 2016, at 11:06 AM, Juraj Lutter  
wrote:


Hi,

just a quick question: Can one specify inet6 default route for 
joyent-branded zones? From what I understand, net-physical relies on 
NDP (which might not always be available.)


Is there any other systematic way?


The route(1M) command works for IPv6, and does have its "-p" option
(persistent storage).  Since native zones have actual backing store on
/etc/inet, it's a perfectly acceptable way of adding a persistent IPv6
route if the vmadm-style configuration doesn't do it.  For example:

route -p add -inet6 default fe80::dead:beef:feed:face

Hope this helps,
Dan




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] GZ and /zones/swap

[Jorge Schrauwen]

Same for KVM zones, due to the kernel wanting to have every bit of
memory allocated also backed by swap.
It will also reserve resize the same amount as the ram parameter (with a
bit of overhead actually)

On 2016-10-03 09:22, Len Weincier wrote:

> Hi 
> 
> Thanks for the responses. Of course the LX machines will need the zones/swap 
> which I did not realize. 
> 
> cheers 
> Len 
> 
> On Sun, 2 Oct 2016 at 23:42 Nigel W  wrote: 
> 
>> On Sep 29, 2016 2:03 PM, "Len Weincier"  wrote:
>>> 
>>> Hi
>> Hi 
>> 
>>> 
>>> We have some new hosts with 1.5T memory and this causes a zones/swap of 
>>> 1.5T to be created. 
>>> Is this necessary in the GZ ? Each VM gets its own swap so just not sure 
>>> what would be running in the GZ that would end u using that swap ?
>>> 
>> 
>> Yes, it could be a good idea depending on your use case. 
>> 
>> If you are using LX or joyent zones, they are assigned out of the GZ's 
>> resources and the since the illumos kernel does not over commit memory, all 
>> memory allocated by a process must be backed in the GZ in either RAM or 
>> swap, so having 0.5x to 1x "max_physical_mem" in "swap". 
>> 
>> KVM zones are a bit different because they will have their own swap as part 
>> of the allocated zvol using whatever mechanism the guest OS uses.  However, 
>> even heavy KVM zone hosts benefit from a lot of swap because they need to 
>> allocate all of the guests memory up front so having a large swap helps deal 
>> the memory fragmentation as the host gets to capacity. 
>> 
>> Of couse because the swap is just a zvol, you can reduce the swap dataset if 
>> you like using using the normal zvol commands: 
>> 
>> zfs set volsize= zones/swap 
>> 
>> I don't recall if shrinking zones/swap needs to be done while the host is in 
>> noimport mode though.
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] how to block init 6 on global zone

[Jorge Schrauwen]

Something like this would be really nice to have upstream,

[ -d /usbkey/root ] &&  mount -O -F lofs /usbkey/root /root

Or whatever in the local-fs service? Is it worth opening a issue for 
this, or a PR even?


Regards

Jorge

On 2016-09-29 14:41, Jonathan Perkin wrote:

* On 2016-09-29 at 13:29 BST, Rob Seastrom wrote:

Of course, now you have a problem:  since you put the alias in 
~root/.bashrc, it will be gone after you reboot, because the SmartOS 
global zone is volatile (filesystem is run from ram).  So what you 
need is an SMF service to copy files out of persistent (zpool) storage 
into /root at boot time.  The details on how to do that are here:  
https://wiki.smartos.org/display/DOC/Administering+the+Global+Zone 
(search for "Creating Persistent Services Using SMF").


Back when I was a novice at using SMF I decided that the most low-drag 
way to handle this general case was to have a sparse-populated file 
hierarchy to tar | tar over a running memory filesystem.  Although 
crude and a bit inelegant, it's served me well for almost four years.  
I used the xml in the wiki (linked above) as a template and had it 
call /opt/custom/tar-root.sh which contains this:


A simpler way to do this is to fetch jclulow's "rc.local" SMF:

  https://gist.github.com/jclulow/2606370

and then add:

  mount -O -F lofs /opt/custom/root /root

or similar to your postboot script.  You then have a persistent root
home directory.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Any SaltStack users around?

[Jorge Schrauwen]

I've done a lot of development on Salt 2016.3.x, I've had the timeouts 
sinds day 1 (was using -devel before 2016.3 got tagged)


I run my entire stack on SmartOS but I had to bump the master's timeout 
up to 120 for me to not have any minions not returning. My longest 
state.apply run is also around 100 seconds.


I have not ran 2015.x versions so cannot comment on those.

Regards

Jorge



On 2016-09-07 21:05, Filip Chabik wrote:

Hi guys,

happy to see some other SaltStack + SmartOS users out there. Recently
salt became a bit more unstable for me and I was hoping to dig a bit
deeper and check whether the issue is on my side, my salt-master side
or in the compatibility of salt-minion and SmartOS zone. Here's the
deal:

1. I'm using 15.4.1 LTS on all of my zones.
2. Not long ago I decided to "bump up" my SaltStack minions to version 
2016.3.1.

a) In order to achieve both points mentioned above, I had to use
some "creativity" when it comes to SaltStack installation.
b) I have a deploy script that I run after every
provisioning/reprovisioning of the zone which is also handling Salt
installation, like this:

# Installing Salt dependencies:
pkgin -y in zeromq py27-m2crypto py27-crypto py27-msgpack
py27-yaml py27-jinja2 py27-zmq py27-requests py27-pip py27-tornado
py27-six

# This one ought to be installed via pip for some reason I
can't recall now:
pip install futures

# The de facto installation:
curl -L https://bootstrap.saltstack.com -o install_salt.sh
sudo sh install_salt.sh -A ${master_ip} -i
"${1:-${minion_name}}" -P git v2016.3.1

3. This is generally working fine -- while I'm running silly stuff
like test.version, test.ping or cmd.run  all is good.
But whenever I hit some more demanding stuff, like state.highstate
that's going through couple of formulas, I very often get information
in red saying: "didn't get response from the minion" (or something
along these lines).

My question is -- are you guys also experiencing such behavior? I have
some formulas that are supposed to run bash script in order to get
some stuff done on the zone, but they rarely succeed when triggered
through Salt. Sometimes they are succeeding, but I still get the same
"didn't get response from the minion" on the master.

Guess I will need to dig a bit deeper into debugging this, but I was
hoping that maybe some of you already experienced such behavior and
have some tips & tricks to share (like for example: "dude, don't
upgrade to anything above 2015.8.x on LTS zones...").

All the best
--
Filip



On Sat, Aug 22, 2015 at 11:38 AM, Jorge Schrauwen 
<sjorge...@blackdot.be> wrote:
I've decided the old smartos_vmadm (virt) module to smartos_legacy and 
added

a deprecation message.

A new smartos_vmadm will be implemented, leaving the old behavior 
unchanged

for now.

Regards

Jorge



On 2015-08-20 08:53, Jasper Siepkes wrote:


Hi Jorge,

I'm a SaltStack user on SDC / SmartOS! I've also made a modest
contribution to
the pkgsrc SaltStack package by contributing an SMF manifests for it. 
My

idea is
to provision SDC Base64 images with Saltstack. That way I can also 
easily

upgrade to newer base64 images.

I'm not (yet) really into the internals of SaltStack so I can't 
really say

anything about the refactoring your proposing.

Thanks for all your work on SaltStack so far! I'm also on #smartos 
BTW as

KermitTheFragger (yeah cheesy, I know ;-).

Kind regards,

Jasper


Op 20 augustus 2015 om 8:22 schreef Jorge Schrauwen
<sjorge...@blackdot.be>:

Hey All,

Anyone around here use SaltStack on SmartOS?
 I've been fixing up the 2015.8 release to work again. All that is 
left

is the smartos_vmadm module which needs a lot of love.

I'm a bit worried about breaking things as the changes I want to do 
are

rather big: https://github.com/saltstack/salt/issues/26507

So if you use SaltStack, speak up before I start tackling this :)

Regards

Jorge

















---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] windows server / sybase ads

[Jorge Schrauwen]

Hey Robert,

That's awesome to hear! Does that also include UAS 
(https://en.wikipedia.org/wiki/USB_Attached_SCSI)
I have a USB3 to msata adaptor that supports and and boy is it fast when 
the hosts supports UAS, I got about 10MB/s less than having it on the 
msata slot on the board it self!


---
~ sjorge

On 2016-07-04 20:41, Robert Mustacchi wrote:

On 7/1/16 22:12 , Garrett D'Amore wrote:
its probably past time that i invest effort in the usb3 stack.  sadly 
my current employer has not expressed any interest in that effort. 
anyone want to help subsidize the effort ?


For what it's worth, we're already working on an xhci driver at Joyent.
It's something I'm working on as we know there's a lot of need for this
around the community.

Robert

On Jul 1, 2016, at 8:09 PM, Dave Finster  
wrote:


You might find that your better off investing in standard spinning 
SAS disks but a very good SLOG like the HGST SSD800MH.B, which cost 
around $800 AUD. The reason being that in a well built SmartOS box, 
you’ll have ZFS ARC occupying RAM from which a good portion of your 
database reads should be sourced from and when sync writes do need to 
be done, the SLOG will help make them more performant. ARC makes read 
performance exceptional for a cache hit. As for zpool layout, for 
database workloads your better off with a multi-way mirror (i.e. a 
pool full of mirror vdevs) as when there is an ARC miss it should be 
performant (at least won’t incur parity penalties in RAIDZ).


The only things to watch out for if your acquiring new hardware is 
NIC, HBA and USB compatibility. The best NICs you can have for 
SmartOS are Intel based ones (be they integrated onto the motherboard 
or as an add-in card), I’ve not had any issues at all with LSI (now 
Avago) HBA cards whereas on-board SATA/SAS can be hit and miss unless 
they are also LSI based (but can be painful to reflesh if needed). 
The USB compatibility aspect is becoming more important as Illumos 
doesn’t yet have an appropriate driver which can cause boot issues 
and rules out keyboard interactions - some boards have the ability to 
emulate USB2, but some work and some don’t.



On 2 Jul 2016, at 8:45 AM, de...@hyltown.com wrote:

the vendor stated this:

"Believe me, my programmers all were extremely frustrated when Linux 
and Sybase ADS were unreliable."


i hope that was badly worded; though linux has never been the most 
reliable of the unix-like systems, i believe it's on a whole 
different level from any version of windows. i was once an MCSE but 
defected (back) to *nix because i wanted to get real work done 
instead of fighting the operating system and related products.


thanks for the suggestions thus far - all good stuff, and i really 
appreciate the insight and recommendations. i didn't realize joyent 
provided virtio drivers - i've been using the ones from fedora for 
several years on the windows terminal server (sitting on 
joyent_20140221T042147Z).


i have often wondered about running an all-ssd zones pool. the devs 
all poo-poo the use of consumer-grade disks, and sata in general. 
and they have made great cases for doing so. but for most of my 
uses, the price and potential performance looks extremely 
attractive. i don't usually have the ability to drop a couple of 
thousand dollars into a disk subsystem for these small 
installations. the customers typically already have enough hardware 
to run everything bare-metal, but i've tried hard to virtualize 
everything for the many benefits provided by doing so (plus of 
course the ones specific to using smartos/zfs).


- On Jul 1, 2016, at 3:23 PM, Humberto Ramirez 
 wrote:
Ideally it should sit on a SmartOS zone but... I understand he wants 
to run the database on top of NTFS...(Vendor requirement) however 
Sybase ADS its also available for linux.



On Jul 1, 2016 2:56 PM, "Joerg Sonnenberger"  wrote:
On Fri, Jul 01, 2016 at 11:15:21AM -0400, Humberto Ramirez wrote:
- Set "compression": "lz4" "block_size": 131072   (This one 
can

only be set at creation)


I would be careful with setting compression, since it can easily be 
a

waste of time, depending on the database.

Joerg


http://www.listbox.com


smartos-discuss | Archives  | Modify Your Subscription









---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Docker on SmartOS (without Triton) / Triton on a single node

[Jorge Schrauwen]

Hi Paul, 

Have a look here:
https://blog.jasper.la/docker-on-smartos-the-harder-way/ 

It seems possible, I haven't tried it myself though. 

Regards 

Jorge

On 2016-06-24 12:20, Paul Dunkler wrote:

> Hi there,
> 
> just read some stuff about the new Triton.
> That really sounds like a nice solution you folks are coming up with!
> Will definitely give it a try.
> 
> We are currently working with original SmartOS-Installations for some 
> customers.
> Mainly doing native + LX-Branded Zones which really works well. Especially 
> the LX-Part advanced heavily in the last time. Good to have that!
> 
> Now i'm somewhat curious if it is possible to run docker containers on a 
> plain SmartOS-System as well -
> or if it is possible to have a single node Triton installation. We really 
> would like to use Docker on our SmartOS.
> 
> Best regards,
> 
> --
> Paul Dunkler
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] OpenBSD and qemu graceful shutdown - WAS: USB pass through to zone needed

[Jorge Schrauwen]

Thank you for confirming it was indeed still working.
I spend most of my evening tracking down the problem.

The problem was that I had cpu_type set to "kvm64,+aes" when I changed 
it a while ago from "qemu64" to expose the AES feature (as the box does 
lots of TLS/SSL) I switched to kvm64.


That broke the acpi shutdown. If you look at "qemu-system-x86_64 -cpu 
?dump" there is only a very small difference. popcnt sse4a abm svm 
lahf_lm are missing with kvm64 but present in qemu64.


Switching to "qemu64,+aes" made OpenBSD respond to the acpi shutdown 
command again!
I did some more tinkering and finally settled on "qemu64,+x2apic,+aes", 
the x2apic seems to lower qemu's CPU usage from a constant 4% or up to 
around 2% or up!


Regarding to qemu_opts property in vmadm... you might want to add "-vga 
none" (I have "-parallel none -k en-us -vga none -nographic").


vmadm won't allow you to set the vga to anything other than 
std,vmware,qxl and circus. But the last -vga encouters wins. This does 
not only disable the vnc console it actually removed the pci bus device.


There is now no mention at all of wsdisplay in dmesg.

Also posting to the list again, as this might be useful for someone down 
the road.


Regards

Jorge

On 2016-06-07 19:33, Tamas Gerczei wrote:

Curious - it still works on my 5.9, I've just tested. Admittedly I'm
overriding the default value of "qemu_opts" with "-parallel none -k
en-us -nographic" though.

Jorge Schrauwen wrote:
I already have that enabled as it use to work fine (around 5.6ish I 
think).


$ rcctl get apmd
apmd_class=daemon
apmd_flags=
apmd_timeout=30
apmd_user=root

But currently on 5.9 it is ignore the acpi shutdown command.
Not the biggest of deals though as I usually just stop the vm before
updating my SmartOS pi.


On 2016-06-06 22:29, Tamas Gerczei wrote:

Slightly off-topic, but a direct response regarding ACPI vs OpenBSD:
this is only true if you don't run apmd. (Which is supplied, so 
adding

'apmd_flags=""' to '/etc/rc.conf.local' and then starting it via
'/etc/rc.d/apmd start' will do.)

Jorge Schrauwen wrote:
I generally use 'shutdown -g0 -i5 -y' for poweroff en 'shutdown -f0 
-i6

-y' for reboots and it stops the zones.

KVM zones get a ACPI shutdown signel, from my experience windows 
does

the right thing, linux too if acpi stuff is installed. OpenBSD just
ignores it unfortunately.

---
~ sjorge

On 2016-06-06 19:53, Paul Sture wrote:

On 6 Jun 2016, at 19:40, Gareth Howell wrote:


I’m monitoring this with interest.

If I issue a shutdown to the global zone on the server, will the
zones have had the chance to do a  graceful shutdown before the
global zone shuts down?



I do regular shutdowns from the global zone and in my experience
'poweroff' waits until all the zones have done a graceful shutdown.

In the last year I've had a couple of instances where a zone hasn't
closed in response to a 'poweroff' and either hung or provoked a
timeout error. Sorry I didn't research the reasons for the timeout 
- I
managed to ssh into the offending zone and do a poweroff inside 
that,

then reissued the GZ poweroff.










---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Community interest in illumos PF port?

[Jorge Schrauwen]

Hello,

We promised to send a reply once we gathered some data, so here it is.

From what alanc told us Oracle spent well over 2 engineer years working 
on their port. This would

require high amount of money for a successfull crowdsourcing campaign.

27 people including us (Adam and Jorge) responded that we would like to 
see pf ported to illumos.
However, all of us were individuals without a backing company to back 
with some serious amount of funds.


Based on this fact, we conclude that the crowd-sourcing campaign would 
likely fail.


Regards

Adam and Jorge




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB pass through to zone needed

[Jorge Schrauwen]

I already have that enabled as it use to work fine (around 5.6ish I 
think).


$ rcctl get apmd
apmd_class=daemon
apmd_flags=
apmd_timeout=30
apmd_user=root

But currently on 5.9 it is ignore the acpi shutdown command.
Not the biggest of deals though as I usually just stop the vm before 
updating my SmartOS pi.



On 2016-06-06 22:29, Tamas Gerczei wrote:

Slightly off-topic, but a direct response regarding ACPI vs OpenBSD:
this is only true if you don't run apmd. (Which is supplied, so adding
'apmd_flags=""' to '/etc/rc.conf.local' and then starting it via
'/etc/rc.d/apmd start' will do.)

Jorge Schrauwen wrote:
I generally use 'shutdown -g0 -i5 -y' for poweroff en 'shutdown -f0 
-i6

-y' for reboots and it stops the zones.

KVM zones get a ACPI shutdown signel, from my experience windows does
the right thing, linux too if acpi stuff is installed. OpenBSD just
ignores it unfortunately.

---
~ sjorge

On 2016-06-06 19:53, Paul Sture wrote:

On 6 Jun 2016, at 19:40, Gareth Howell wrote:


I’m monitoring this with interest.

If I issue a shutdown to the global zone on the server, will the
zones have had the chance to do a  graceful shutdown before the
global zone shuts down?



I do regular shutdowns from the global zone and in my experience
'poweroff' waits until all the zones have done a graceful shutdown.

In the last year I've had a couple of instances where a zone hasn't
closed in response to a 'poweroff' and either hung or provoked a
timeout error. Sorry I didn't research the reasons for the timeout - 
I

managed to ssh into the offending zone and do a poweroff inside that,
then reissued the GZ poweroff.










---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB pass through to zone needed

[Jorge Schrauwen]

I generally use 'shutdown -g0 -i5 -y' for poweroff en 'shutdown -f0 -i6 
-y' for reboots and it stops the zones.


KVM zones get a ACPI shutdown signel, from my experience windows does 
the right thing, linux too if acpi stuff is installed. OpenBSD just 
ignores it unfortunately.


---
~ sjorge

On 2016-06-06 19:53, Paul Sture wrote:

On 6 Jun 2016, at 19:40, Gareth Howell wrote:


I’m monitoring this with interest.

If I issue a shutdown to the global zone on the server, will the zones 
have had the chance to do a  graceful shutdown before the global zone 
shuts down?




I do regular shutdowns from the global zone and in my experience
'poweroff' waits until all the zones have done a graceful shutdown.

In the last year I've had a couple of instances where a zone hasn't
closed in response to a 'poweroff' and either hung or provoked a
timeout error. Sorry I didn't research the reasons for the timeout - I
managed to ssh into the offending zone and do a poweroff inside that,
then reissued the GZ poweroff.




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB pass through to zone needed

[Jorge Schrauwen]

I'll try to write something up tomorrow,
I managed to strip out a lot of unneeded stuff and ended up just shy of 
10mb.


Everything seems to be working, I'll also write a manifest for it so it 
can be started.


I'll probably roll with this, I don't like having a lot in the gz but 
~10mb is acceptable.
I just have all the node run a local copy and talk to a master to deal 
with the shutdown stuff.


Regards

Jorge

On 2016-06-05 21:11, Jorge Schrauwen wrote:

I was experimenting a bit today.

pkg_add -p /opt/apcupsd apcupsd-*.tgz
followed by patchelf to fix the paths seems to result in a ~65MB dir
that can be dropped into the gz.

I only give it a quick spin and got no segfaults so it looks promising.

Regards

Jorge

On 2016-06-04 14:42, Jorge Schrauwen wrote:

You can pass through the device to a native zone if you like.
You need to manual edit the zone using zonecfg and use the 'add 
device' command.


Due to SmartOS running from ramdisk the usb device order was not
stable for me causing some problems. (APC SmartUPS)

I abandoned that approach and switched to a RPi which failed last year
and I haven't setup a replacement yet. I was thinking about using
socat to forward it from the GZ to a zone over the network.

Socat is available I just need to write a proper smf for this.
Alternatively I'm looking into a smf that will reconfigure the zone
automaticall on boot to have the correct usb device. Not sure which
methode would be easier.

Regards

Jorge

On 2016-06-04 05:40, John Croix wrote:
I'm currently sitting in the dark in my house without power, 
pondering

the need for an automatic means to shutdown my SmartOS server. When
power went off, I raced upstairs to manually shut it down prior to
draining the UPS, and I'd like to avoid a repeat scenario.

It seems like the best way to do this might be to have a dedicated LX
zone that runs the APC UPS daemon software. I can use it to touch a
file when required, and, in the global zone, monitor the file system
for the presence of that file. When the file appears, a power off
command is issued. I just need to be able to have the local zone
access the UPS via USB connection. Access to the LX file system from
the global zone for monitoring is obviously not an issue.

In short, I need to find out how to do the following:
   Determine which device in the global zone the UPS is attached to 
via

USB cable
   Pass the device down to a local zone (I assume via some zonecfg
commands)
  Determine which device to point the daemon to in the local zone
Can anybody provide some info concerning the above issues?

Thanks in advance,
John

Sent from my iPad










---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] USB pass through to zone needed

[Jorge Schrauwen]

I was experimenting a bit today.

pkg_add -p /opt/apcupsd apcupsd-*.tgz
followed by patchelf to fix the paths seems to result in a ~65MB dir 
that can be dropped into the gz.


I only give it a quick spin and got no segfaults so it looks promising.

Regards

Jorge

On 2016-06-04 14:42, Jorge Schrauwen wrote:

You can pass through the device to a native zone if you like.
You need to manual edit the zone using zonecfg and use the 'add device' 
command.


Due to SmartOS running from ramdisk the usb device order was not
stable for me causing some problems. (APC SmartUPS)

I abandoned that approach and switched to a RPi which failed last year
and I haven't setup a replacement yet. I was thinking about using
socat to forward it from the GZ to a zone over the network.

Socat is available I just need to write a proper smf for this.
Alternatively I'm looking into a smf that will reconfigure the zone
automaticall on boot to have the correct usb device. Not sure which
methode would be easier.

Regards

Jorge

On 2016-06-04 05:40, John Croix wrote:

I'm currently sitting in the dark in my house without power, pondering
the need for an automatic means to shutdown my SmartOS server. When
power went off, I raced upstairs to manually shut it down prior to
draining the UPS, and I'd like to avoid a repeat scenario.

It seems like the best way to do this might be to have a dedicated LX
zone that runs the APC UPS daemon software. I can use it to touch a
file when required, and, in the global zone, monitor the file system
for the presence of that file. When the file appears, a power off
command is issued. I just need to be able to have the local zone
access the UPS via USB connection. Access to the LX file system from
the global zone for monitoring is obviously not an issue.

In short, I need to find out how to do the following:
   Determine which device in the global zone the UPS is attached to 
via

USB cable
   Pass the device down to a local zone (I assume via some zonecfg
commands)
  Determine which device to point the daemon to in the local zone
Can anybody provide some info concerning the above issues?

Thanks in advance,
John

Sent from my iPad







---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] nmap in LX Zone

[Jorge Schrauwen]

I can reproduce this under ubuntu:
https://github.com/joyent/illumos-joyent/issues/117



On 2016-06-01 20:51, Robert Mustacchi wrote:

On 5/30/16 6:53 , Kilian Ries wrote:

Hi,


is there any chance to get nmap running inside a lx-centos7 zone? 
Already tried it with privileged / unprivileged flag, getting the 
following errors:



###

nmap x.x.x.x 22


Starting Nmap 6.40 ( http://nmap.org ) at 2016-05-30 13:46 UTC

dnet: Failed to open device eth0

QUITTING!

###


###

nmap --unprivileged x.x.x.x 22


Starting Nmap 6.40 ( http://nmap.org ) at 2016-05-30 13:46 UTC

Problem binding to interface , errno: 92

socket_bindtodevice: Protocol not available

###



The next step i'll try is to build a statically-linked binary under 
smartos and try to use it via /native in the lx-zone, but isn't there 
an easier solution?


Could you perhaps strace that so we can see how it's trying to pen the
devices in those cases and what errors it's getting?

Thanks,
Robert




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Problem with dnsmasq on smartos zone

[Jorge Schrauwen]

do you have the following property set? 

   nics.*.dhcp_server:

   With this property set to true, this VM will be able to
operate as a
   DHCP server on this interface.  Without this, some of the
packets
   required of a DHCP server will not get through.

   type: boolean
   vmtype: OS,KVM
   listable: yes (see above)
   create: yes
   update: yes
   default: false 

Regards 

Jorge

On 2016-05-27 13:39, Gareth Howell wrote:

> Hi 
> I'm in the process of moving my raspberry pi based dnsmasq server to a 
> smartos zone called ns2. It's the only thing running in the zone. 
> 
> I moved the config files over and changed the paths. The server starts up OK 
> and responds to DHCPDISCOVER requests with a DHCPOFFER, but the client never 
> sees the offer. 
> 
> I've dumped the output from dnsmasq here http://pastebin.com/Zm7YH5n8 
> I was running wireshark on the client and it never saw the unicast traffic 
> coming back from the server. Could this be an adapter configuration issue? 
> 
> -- 
> 
> Regards
> 
> Gareth 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KVM with lofs mount

[Jorge Schrauwen]

I've been running Plex in LX branded zones for... euhm pretty close
after the first datasets went up. 

I never want to go back to KVM for Plex, aside form a few hickups every
now and then it has been a breeze.

---
~ sjorge 

On 2016-05-19 16:48, Rickie via smartos-discuss wrote:

> Thanks.  My other option was to use samba.   I've got a zone running samba 
> that exports the zfs filesystem.
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] KVM with lofs mount

[Jorge Schrauwen]

Make sure you are on the latest platform image though. 

There was a small bug in the images from end of march to mid aprilish. 

Regards 

Jorge

On 2016-05-19 15:07, Rickie via smartos-discuss wrote:

> Glad to hear that Plex works in an lx-zone.  That's exactly what I wanted to 
> run.  
> 
> Thanks
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Community interest in illumos PF port?

[Jorge Schrauwen]

On 2016-05-12 23:39, Joshua M. Clulow wrote:

On 12 May 2016 at 14:32, Adam Števko  wrote:
Well, I suppose the smaller the divergence, the better it would be. 
But

that’s the theory.


In some senses that's true.  As I was working on it, though, it became
obvious that there are a number of things that will just be different:
e.g., we have rather different data structures (list_t, avl_t), our
packet filter hooks are a bit different, we're already an SMP capable
kernel, we have zones (and each zone needs its own idea of what is,
today, a single-instance firewall), we generally want to have prefixed
structures and typedef types.

In the end, it might be possible to do a port that did _not_ use as
many of our native facilities, but then it would be less easy to debug
and less of a first class citizen.  Part of this work is not just
doing a port, but deciding on the legacy you'll be creating: who will
look after it over time, and how.

Also, at the time I had not had opportunity to evaluate "npf" from
NetBSD.  Perhaps it'd be a better fit?  I'm not sure.


npf is also pretty nice, I was looking at this a while back.
The fact that SMP was not an afterthought for npf was nice,
also there seems to be some extension like support (IIRC) which may make
plugging in zones, ... easier.


Who would be funded via the Kickstarter to actually do the work?
The person is not yet known. We just want to know how many potential 
backers

could we get and if it’s even possible to fund the port.


I think if you're looking to fund work, you should probably first
figure out who you would be funding.


Well that as our problem, both me and xenol were toying with the idea 
but well
neither of us has heaps of cash to spare. So we decided to start by 
poking the
community to get a feel if there is any interest in this. If it is just 
us, no

point and trying to figure out a kickstarter or similar idea.

Alanc (on IRC) said it was multiple engineers for a year+ when they did 
it.
That would put the required funding target very high, probably not 
something

that just a few community people chipping in can gather :(


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Support for unattended installation/recovery

[Jorge Schrauwen]

I glanced over the patch and it looks sane to me.
Also being able to kick off a sshd server after booting via pxe does 
indeed seem like a very nice feature to have!




On 2016-05-05 23:03, Joerg Sonnenberger wrote:

Hello,
I recently faced the problem of trying to install SmartOS on a Skylake
system. This means no keyboard on the remote console due to missing 
USB3

support. While hacking something together, I realized that the idea is
useful enough for remote emergency maintainance as well, i.e. when a
machine in the office has issues like a broken firewall config and all
the technical assistanec you have at hand boils down to "Select the
second item on the GRUB boot prompt". The patch adds a boot command 
line

option "run_sshd=true". If it is set, the following happens:
- all interfaces are configured automatically with DHCP
- ssh-keygen creates a set of SSH keys, the fingerprints are shown on
  the console
- the root password is replaced with root_shadow (if present)
- sshd is started

The final three steps are skipped if sshd is already running. This is
useful for installation as it allows just starting the script again 
from

ssh. It is easier than using the answer file when dealing with a fresh
installation on a new server, as you often won't know the correct
answers in advance.

I have not added anything advanced like providing authorized_keys via
separate file, the primary goal for me is to have something at hand 
that

works out of the box without customizing the ISO image. It is certainly
possible to extend this somewhat as a second step, if deemed useful.

Joerg



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] CentOS 7 lx-dataset images & Systemd

[Jorge Schrauwen]

For those wondering, this also works for the new Ubuntu 16.04 LTS 
dataset released last week.

However the 'dbus' package needs to be installed first.


On 2016-03-10 21:47, Jorge Schrauwen wrote:

Hey All,

I've been playing around with SaltStack 2016.3 on the CentOS 7
lx-dataset images.
As I made some changes to that version I wanted to test. Stuff like
setting timezone, hostname,... is broken.

This is due to the lack of a lot of cgroups suppport, but there is a
'easy' workaround.

---
  ## disable some functions because lx-brand (TODO: remove once 
implemented)

  for svc in systemd-timedated systemd-hostnamed; do
override_dir=/etc/systemd/system/${svc}.service.d
override_svc=${override_dir}/override.conf
mkdir -p ${override_dir}

echo "[Service]" > ${override_svc}
echo "PrivateTmp=no" >> ${override_svc}
echo "PrivateDevices=no" >> ${override_svc}
echo "PrivateNetwork=no" >> ${override_svc}
echo "ProtectSystem=no" >> ${override_svc}
echo "ProtectHome=no" >> ${override_svc}

systemctl daemon-reload
systemctl restart ${svc}
done
---

This created 2 override files for systemd-hostnamed and
systemd-timedated, it forces off some of the 'protections' that depend
on the not support cgroups bits.

These changes are persistent even if the package updates the .service
file. (yay!)

After placing the 2 override files and reloading + restarting the
service the following 2 tools work again. hostnamectl and timedatectl.

Hopefully this is useful for some of you, it would also be nice to
have this in the images that get pulled down.

Regards

Jorge




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] FreeBSD in KVM

[Jorge Schrauwen]

Hi,

The mouse on SmartOS is always in tablet (-usb -usbdevice tablet) mode 
as this generally works better with VNC as this accepts absolute x,y 
instead of relative.


It might be that FreeBSD is expecting a PS2 emulated mouse by default. 
(/dev/sysmouse) seems to hint at that. Seems like a few people are 
having the same problem: https://forums.freebsd.org/threads/33609/


The solution always seems to be the same, remove those options and use 
the normal PS2 emulated mouse.


I'm not sure you can do this easily via SmartOS, append options is easy 
but removing, I found nothing on that front.


Regards

Jorge


On 2016-04-22 05:20, G B via smartos-discuss wrote:

I've tried both moused="YES" and moused="NO" in /etc/rc.conf and the 
mouse pointer just sits in the middle of the screen.


The xorg.conf was generated with Xorg -configure

On Thursday, April 21, 2016 9:35 PM, Chuck Barker 
 wrote:


You've probably already visited the FreeBSD handbook for 
troubleshooting tips.

https://www.freebsd.org/doc/handbook/x11-understanding.html
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html

If the mouse worked when at the command line, but not since X11 was 
installed, then check the /etc/rc.conf file.

Verify a line entry exists that reads;
moused_enable="NO"

What commands were used to generate the xorg.conf?
These commands?

Xorg -configure
Xorg -config /root/xorg.conf.new

On Thu, Apr 21, 2016 at 7:10 PM, G B via smartos-discuss 
 wrote:


I'm using FreeBSD 9.3-RELEASE-33 built from .iso in KVM on SmartOS 
3/31 image.  Everything works fine and X11 is installed and starts a 
window manager, except the mouse doesn't work.  I've tried generating 
an xorg.conf with:


Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5 6 7"

Under "Section "ServerLayout""
InputDevice "Mouse0" "CorePointer"

I've tried WindowMaker, XFCE, and dwm.  Just an arrow in the center of 
the window that won't move.  Any suggestions to get the mouse working?


--

Press On.

SMARTOS-DISCUSS | Archives | Modify Your Subscription



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] FreeBSD KVM image

[Jorge Schrauwen]

+1 for this, todays release of 5.9 would mark a nice occasion to do it
too ;)

On 2016-03-29 23:09, G B via smartos-discuss wrote:

> Has Joyent considered creating an OpenBSD image in addtion to FreeBSD?
> 
> On Tuesday, March 29, 2016 10:10 AM, G B via smartos-discuss 
>  wrote:
> 
> Robert, my apologies for my poor communication.  The FreeBSD image does have 
> that added, I wanted to know how to add it for the OpenBSD install I'm going 
> to do.  The question for OpenBSD was previously answered by Antoine and 
> Jorge. 
> 
> Thanks to all! 
> 
> On Tuesday, March 29, 2016 9:38 AM, Robert Mustacchi  wrote:
> 
> On 3/29/16 3:43 , G B via smartos-discuss wrote:
>> Last week I installed the FreeBSD 10.2 image for KVM provided by Joyent.  
>> What I really like is being able to do 'vmadm console UUID' and not have to 
>> use VNC.  Maybe I've done something wrong in the past, but I don't recall 
>> being able to do that.  
> 
> I think this was something that we were trying to make sure we got added
> to all the images at some point, but may have missed the FBSD one.
> 
> Christopher, can you make sure a bug is opened on that if it isn't already?
> 
> Thanks,
> Robert
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Net access on vm

[Jorge Schrauwen]

Hi, 

Lots of people seem to have issues following that guide but in the end
it was always the same problem. 

If you change the subnet, make sure to update the addresses in the nat
and firewall roles AND in the 'setup gw0' section.

On 2016-03-29 07:59, Rupinder Singh Chugh wrote:

> any one can provide us step by step  
> we are still not able to resolve it, we had follow this 
> https://docu.blackdot.be/snipets/solaris/smartos-nat [1] 
> 
> Regards 
> RUPINDER SINGH 
> On 16 March 2016 at 15:24, Rupinder Singh Chugh <rschug...@gmail.com> wrote:
> 
> we are looking basically NAT  
> so vms can be access via firewall outside publicly with static ip 
> 
> Regards 
> RUPINDER SINGH 
> 
> On 15 March 2016 at 23:52, Cody Mello <mel...@joyent.com> wrote:
> 
> Hi Rupinder,
> 
> Could you provide details about the network you're trying to get set up on? 
> The configuration of the network affects how you'll want to configure your 
> host.
> 
> - Cody
> 
> On Mon, Mar 14, 2016 at 9:45 PM, Rupinder Singh Chugh <rschug...@gmail.com> 
> wrote:
> 
> We had followed same link and do setup same already , but still issue is 
> there 
> 
> Regards 
> RUPINDER SINGH 
> 
> On 15 March 2016 at 01:13, Jorge Schrauwen <sjorge...@blackdot.be> wrote:
> 
> This was recently verified to still be working: 
> https://docu.blackdot.be/snipets/solaris/smartos-nat 
> 
> Just make sure to update the nat-rules, gz's vnic ip and address 
> concistantly. 
> 
> Regards 
> 
> Jorge
> 
> On 2016-03-14 17:30, Rupinder Singh Chugh wrote: 
> 
> We had smartos with single public ip 
> 
> We had created virtual nic with ip 10.0.0.1 on smartos and created a 
> Vm with ip 10.0.0.2 created and able to ping to nic ip 
> 
> But we are not able to access Internet 
> Can you provide us next additional steps to do on smartos so on all  my 
> Internet will be accessed

 SMARTOS-DISCUSS | Archives [2] [3] | Modify [4] Your 
Subscription
 [5]

 

Links:
--
[1] https://docu.blackdot.be/snipets/solaris/smartos-nat
[2] https://www.listbox.com/member/archive/184463/=now
[3] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[4]
https://www.listbox.com/member/?;
[5] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Jorge Schrauwen]

Hey Josh, 

I just remembered this https://github.com/joyent/smartos-live/issues/510

So only add_filesystems is implemented. 

Regards 

Jorge 

On 2016-03-14 17:22, Josh Wilsdon wrote:

>> I used vmadm, it works fine for adding but updating/remove is a bit flaky.
> 
> Hi Jorge, 
> 
> Could you be a bit more specific as to what problems you had with vmadm 
> update/remove? 
> 
> Thanks, 
> 
> Josh
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Jorge Schrauwen]

Only the _filesystem variants. 

If memory serves me right: adding them on creation -> OK 

Some of add_filesystems, remove_filesystems or update_filesystems was
broken... I think it was update and remove. I just stopped trying that
all together and recreaste the entire zone of I need to do a change. 

On 2016-03-14 17:22, Josh Wilsdon wrote:

>> I used vmadm, it works fine for adding but updating/remove is a bit flaky.
> 
> Hi Jorge, 
> 
> Could you be a bit more specific as to what problems you had with vmadm 
> update/remove? 
> 
> Thanks, 
> 
> Josh
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Net access on vm

[Jorge Schrauwen]

This was recently verified to still be working:
https://docu.blackdot.be/snipets/solaris/smartos-nat 

Just make sure to update the nat-rules, gz's vnic ip and address
concistantly. 

Regards 

Jorge 

On 2016-03-14 17:30, Rupinder Singh Chugh wrote:

> We had smartos with single public ip 
> 
> We had created virtual nic with ip 10.0.0.1 on smartos and created a 
> Vm with ip 10.0.0.2 created and able to ping to nic ip 
> 
> But we are not able to access Internet 
> Can you provide us next additional steps to do on smartos so on all  my 
> Internet will be accessed 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Jorge Schrauwen]

I used vmadm, it works fine for adding but updating/remove is a bit
flaky. 

On 2016-03-14 13:42, Fred Liu wrote:

> FROM: Jorge Schrauwen [mailto:sjorge...@blackdot.be] 
> SENT: 星期六, 三月 12, 2016 19:37
> TO: smartos-discuss@lists.smartos.org
> CC: 王靖
> SUBJECT: Re: [smartos-discuss] How to mount different zfs volumn to the same 
> lx branded zone 
> 
> Yes, it will work as long as the zone is on the same server as the data. 
> 
> type needs to be set to 'lofs', you probably also want 'options' set to [ 
> 'nodevice' ] 
> 
> [Fred]: Did you update these by vmadm or zonecfg?  In  my tests, it works in 
> zonecfg not vmadm. 
> 
> Thanks. 
> 
> Fred 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] pkgin upgrade openssl-1.0.2e to openssl-1.0.2g breaks python

[Jorge Schrauwen]

I hit the problem a while ago also, the python package got recompiled 
but it did not get a version bump so pkgin upgrade does not see it.


pkgin -Fy in python27

(the -Fy is imporant) will force reinstall python and fix the problem)

Regards

Jorge



On 2016-03-14 08:32, Eric wrote:

Only tested on python 2.7 so far

Upon upgrading openssl-1.0.2e to openssl-1.0.2g SSL related functions
in
python breaks

A solution is to remove python27-2.7.11 and re-install it

Removing python2.7 with 'pkgin remove python27-2.7.11' will also remove
nodejs-5.7.0, which will also need to be re-installed

Console logs attached

image: "96bcddda-beb7-11e5-af20-a3fb54c8ae29"




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Jorge Schrauwen]

Yes, it will work as long as the zone is on the same server as the data.


type needs to be set to 'lofs', you probably also want 'options' set to
[ 'nodevice' ] 

Regards 

Jorge

On 2016-03-12 12:08, 王靖 wrote:

> Thanks for your reply. 
> 
> Do you mean that I can solve this issue without using NFS/iSCSI/SMB? 
> In my case, there are one physical machine, 4 SSD,  1 SATA. I group SATA into 
> a pool naming sata_zpool and also group SSD to a pool naming zones. 
> 
> #zpool create sata_zpool c2t3d0 
> #zfs create -V 50G sata_zpool/test 
> 
> #zpool status 
> 
> pool: sata_zpool 
> state: ONLINE 
> scan: none requested 
> config: 
> 
> NAMESTATE READ WRITE CKSUM 
> sata_zpoolONLINE   0 0 0 
> c2t3d0ONLINE   0 0 0 
> 
> errors: No known data errors 
> 
> pool: zones 
> state: ONLINE 
> scan: none requested 
> config: 
> 
> NAMESTATE READ WRITE CKSUM 
> zones   ONLINE   0 0 0 
> raidz1-0  ONLINE   0 0 0 
> c0t0d0  ONLINE   0 0 0 
> c0t1d0  ONLINE   0 0 0 
> c0t2d0  ONLINE   0 0 0 
> c0t3d0  ONLINE   0 0 0 
> 
> errors: No known data errors 
> 
> Then I can write the json file like below 
> 
> test.json 
> { 
> "brand": "lx", 
> "image_uuid": "d5b3865c-0804-11e5-be21-dbc4ce844ddc", 
> "alias": "test", 
> "kernel_version": "2.6.32", 
> "hostname": "test", 
> "max_physical_memory": 1024, 
> "resolvers": [ 
> "114.114.114.114", 
> "8.8.8.8" 
> ], 
> "filesystem": [ 
> { 
> "type": "zfs", 
> "source":"/sata_zpool/test", 
> "target":"/test" 
> } 
> ], 
> "nics": [ 
> { 
> "nic_tag": "admin", 
> "ip": "10.20.2.49", 
> "netmask": "255.255.255.0", 
> "gateway": "10.20.2.1", 
> "primary": "1" 
> } 
> ] 
> }  
> 
> #vmadm create -f test.son 
> #zlogin UUD 
> #df -h 
> 
> Filesystem  Size  Used Avail Use% Mounted on 
> none 11G  562M   10G   6% / 
> 
> It seems that it does not work. Could you please help me? Thanks very much. 
> 
> On Mar 12, 2016, at 5:52 PM, Jorge Schrauwen <sjorge...@blackdot.be> wrote: 
> 
> If you just want the storage and not the zfs management layer... 
> 
> You can look in 'man vmadm' under the filesystems property. I use it and it 
> works great to expose my bulk data to multiple zones.
> 
> On 2016-03-12 10:49, Fred Liu wrote: 
> It seems hardware pass-through is not applicable in SmartOS from what I know. 
> But 
> there are some indirect methods(NFS/iSCSI) you can try for there is almost no 
> network 
> overhead in LX. 
> 
> Thanks.
> 
> 发送自 Outlook Mobile [1] 
> 
> On Sat, Mar 12, 2016 at 1:02 AM -0800, "Ian Collins" <i...@ianshome.com> 
> wrote:
> 
> On 03/12/16 21:49, 王靖 wrote:
>> Thanks for your reply. I try to install NOSQL database aerospike in a > lx 
>> branded zone. It seems that aerospike can put data in SSD and > SATA, so I 
>> want to have a lx branded zone that have SSD and SATA, in > this way I can 
>> store most of the data on SATA while use SSD as a > cache.
> 
> You will probably be much better of just using the SSD as a cache for the 
> zones pool.
> 
> SmartOS is designed to work with a single pool.  Unlike legacy file systems, 
> you generally don't have to mess about with drive configurations with ZFS.
> 
> -- 
> Ian.

 SMARTOS-DISCUSS | Archives [2] [3] | Modify [4] Your 
Subscription
 [5]

 

Links:
--
[1] https://aka.ms/sdimjr
[2] https://www.listbox.com/member/archive/184463/=now
[3] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[4]
https://www.listbox.com/member/?;
[5] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Jorge Schrauwen]

If you just want the storage and not the zfs management layer... 

You can look in 'man vmadm' under the filesystems property. I use it and
it works great to expose my bulk data to multiple zones.

On 2016-03-12 10:49, Fred Liu wrote:

> It seems hardware pass-through is not applicable in SmartOS from what I know. 
> But 
> there are some indirect methods(NFS/iSCSI) you can try for there is almost no 
> network 
> overhead in LX. 
> 
> Thanks.
> 
> 发送自 Outlook Mobile [1] 
> 
> On Sat, Mar 12, 2016 at 1:02 AM -0800, "Ian Collins"  
> wrote:
> 
> On 03/12/16 21:49, 王靖 wrote:
>> Thanks for your reply. I try to install NOSQL database aerospike in a > lx 
>> branded zone. It seems that aerospike can put data in SSD and > SATA, so I 
>> want to have a lx branded zone that have SSD and SATA, in > this way I can 
>> store most of the data on SATA while use SSD as a > cache.
> 
> You will probably be much better of just using the SSD as a cache for the 
> zones pool.
> 
> SmartOS is designed to work with a single pool.  Unlike legacy file systems, 
> you generally don't have to mess about with drive configurations with ZFS.
> 
> -- 
> Ian.
> 
> SMARTOS-DISCUSS | Archives [2] [3] | Modify [4] Your Subscription
> [5]
 

Links:
--
[1] https://aka.ms/sdimjr
[2] https://www.listbox.com/member/archive/184463/=now
[3] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[4]
https://www.listbox.com/member/?;
[5] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] CentOS 7 lx-dataset images & Systemd

[Jorge Schrauwen]

Hey All,

I've been playing around with SaltStack 2016.3 on the CentOS 7 
lx-dataset images.
As I made some changes to that version I wanted to test. Stuff like 
setting timezone, hostname,... is broken.


This is due to the lack of a lot of cgroups suppport, but there is a 
'easy' workaround.


---
  ## disable some functions because lx-brand (TODO: remove once 
implemented)

  for svc in systemd-timedated systemd-hostnamed; do
override_dir=/etc/systemd/system/${svc}.service.d
override_svc=${override_dir}/override.conf
mkdir -p ${override_dir}

echo "[Service]" > ${override_svc}
echo "PrivateTmp=no" >> ${override_svc}
echo "PrivateDevices=no" >> ${override_svc}
echo "PrivateNetwork=no" >> ${override_svc}
echo "ProtectSystem=no" >> ${override_svc}
echo "ProtectHome=no" >> ${override_svc}

systemctl daemon-reload
systemctl restart ${svc}
  done
---

This created 2 override files for systemd-hostnamed and 
systemd-timedated, it forces off some of the 'protections' that depend 
on the not support cgroups bits.


These changes are persistent even if the package updates the .service 
file. (yay!)


After placing the 2 override files and reloading + restarting the 
service the following 2 tools work again. hostnamectl and timedatectl.


Hopefully this is useful for some of you, it would also be nice to have 
this in the images that get pulled down.


Regards

Jorge


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Introducing io-lx -- an attempt to port LX Zones to OmniOS

[Jorge Schrauwen]

When I still had most of my zones on OmniOS and heard the LX news I was 
thinking about how that would work on non-smartos stuff given the lack 
of vmadm.


In my head I seemed to end up on traditional tools + a script that would 
use debbootstrap to setup debian/ubuntu zones on the spot, just point it 
to the dataset.


In theory that 'should' work. In practice? I have no idea. I have many 
ideas but all seem a bit painful. But feel free to pluk my brain about 
it on IRC if you want.


Regards

Jorge


On 2016-03-08 03:47, Dan McDonald wrote:

Hello!

700+ cherrypicked commits later, and at least I haven't obviously
regressed lipkg/ipkg zones.  :)

This github repo:

https://github.com/danmcd/io-lx-public/

is the beginning of my attempt to port LX zones over to OmniOS.  I
KNOW there's a lot more work to be done, but I wanted to make sure
this repo is viewable by the public so:

1. ) People know about it.

2. ) People who are interested in helping can do so.

3. ) People can laugh at all of the mismerges and other flub-ups I'm
sure I haven't caught yet.  :)

4. ) I will be context-switching to OmniOS r151018 ramp-up very soon,
and want to checkpoint state.

I've Bcc:ed the SmartOS (home of LX zones) and the illumos (where I
hope this work can be upstreamed at some point) lists.  Discussion on
io-lx (Illumos-OmniOS-LX) should take place either on github or on the
OmniOS mailing list.

So far:

-  I've sidepulled 700+ commits, ending with illumos-joyent's
8443e038ef8eb3ca6a95818d6e90b2a1eb4e9cb6.  There are some more
illumos-joyent commits I'll need to bring over, but my cherrypicking
script and setups are primed & tested, so I *should* be able to make
short work of it.

-  I've smoke-tested a global-only OmniOS boot, and a single-lipkg zone
OmniOS boot.  After some mismerge-related consternation, I booted the
lipkg zone as well.  A rudimentary ppriv(1) comparison between root
shells in global and lipkg zones was part of the smoke test.

-  Any files I didn't know where they went I put into the "brand/lx"
package.  The inotify feature, for example, is in there, and perhaps
it shouldn't be.

-  If you ONU to io-lx, note that to install brand/lx, you will need to
UNINSTALL the "illumos-gate" consolidation package first.  I don't
have changes in omnios-build or any of the other repos (like pkg5)
yet.  I hope to avoid outside-illumos changes until it's time to
figure out the admin model.

After I'm comfortable with no ipkg/lipkg regressions, I will need to
spend some design time figuring out how LX zones will look on OmniOS.
I will not be porting vmadm(1M) over from SmartOS, so I need to think
about how LX will fit in with traditional zone tools.  I may discover
other problems, but until I start the '018 process, and immediately
after '018 ships, I will need to ensure no ipkg/lipkg regressions
first and foremost.

It's not much, but it's a start.

Thanks for your time & patience,
Dan




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Delegated ZFS dataset access from the Gobal Zone

[Jorge Schrauwen]

I didn't catch that bit, yeah if you just want to 'access' it from the 
gz, doe what Ian said :)




On 2016-03-04 22:57, Ian Collins wrote:

On 03/04/16 18:05, Humberto Ramirez wrote:

Hi, Is it possible to access a delegated ZFS Dataset from the Global
Zone without having to detach change mount points etc?


If you just want to access the data, using
/zones/uuid/root/mount_point as suggested is fine.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] enable network/physical in noinstall/recovery?

[Jorge Schrauwen]

You can use ifconfig to bring it up manually. 

ifconfig e1000g0 inet auto-dhcp (from memory so it may be incorrect)

On 2016-02-19 11:30, Fred Liu wrote:

> Hi, 
> 
> "noinstall/recovery" is really helpful to fix/save zpools. But it is offline. 
> Is it hard to enable networking in it? Just like 
> "fail-safe-mode-with-network". 
> 
> Nobody wants to recover from remote backup but that is the ideal life. 
> 
> Thanks. 
> 
> Fred 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. Can it be enlarged?

[Jorge Schrauwen]

You can also just resize the fat partition after writing to the UBS
stick.

Jorge 

On 2016-02-16 12:58, Fred Liu wrote:

> It should be doable if we can hack in "gmake usb". 
> 
> FROM: Micky [mailto:mickylmar...@gmail.com] 
> SENT: 星期二, 二月 16, 2016 19:06
> TO: smartos-discuss@lists.smartos.org
> SUBJECT: Re: [smartos-discuss] the partition size is fixed 1.86G in USB 
> stick. Can it be enlarged? 
> 
> Likely no, cause it's a disk image. 
> 
> On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu  wrote:
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Question regarding package sizing

[Jorge Schrauwen]

Excellent explenation Nahum!



On 2016-02-15 15:39, Nahum Shalman wrote:

On 02/15/2016 01:30 AM, Benjamin Bergia wrote:

Hi,

I recently noticed that all the packages used by SDC zones are using 
some strange settings. All of them, even database ones, are using 1 
vCPU with a cap of 400. I can picture in my head the "meaning" of the 
CPU cap when the cap is lower than the sum of the CPU percentages. So 
something like 4 vCPU and a cap of 200 make sense to me.


Can somebody explain me what happens with a setting of let say 1 vCPU 
and a cap of 200 ?


In the SDC case what was the idea behind having this kind of settings 
? Does it give any performance/portability/else improvement ?


I am rethinking my packages and where I previously used settings like 
you would use on vSphere, I am no wondering if I am not doing it 
totally wrong.


There are 3 important concepts. vCPUs, cpu_shares, and cpu_cap. From
the vmadm man page (my further comments below that):

   vcpus:

   For KVM VMs this parameter defines the number of virtual
CPUs the guest
   will see. Generally recommended to be a multiple of 2.

   type: integer (number of CPUs)
   vmtype: KVM
   listable: yes
   create: KVM only
   update: KVM only (requires VM reboot to take effect)
   default: 1

   cpu_shares:

   Sets a limit on the number of fair share scheduler (FSS)
CPU shares for
   a VM. This value is relative to all other VMs on the
system, so a value
   only has meaning in relation to other VMs. If you have one 
VM with a
   a value 10 and another with a value of 50, the VM with 50 
will get 5x
   as much time from the scheduler as the one with 10 when 
there is

   contention.

   type: integer (number of shares)
   vmtype: OS,KVM
   listable: yes
   create: yes
   update: yes (live update)
   default: 100

   cpu_cap:

   Sets a limit on the amount of CPU time that can be used by a 
VM. The

   unit used is the percentage of a single CPU that can be
used by the VM.
   Eg. a value of 300 means up to 3 full CPUs.

   type: integer (percentage of single CPUs)
   vmtype: OS,KVM
   listable: yes
   create: yes
   update: yes (live update)


First, note that "vcpus" from a SmartOS perspective only applies to
KVM VMs. That setting determines how many processors the VM can see
and thus can use to schedule its processes. We'll come back to that.

Zones (both the kind containing the QEMU process for KVM VMs and
regular LX and joyent branded ones) can see all of the physical
processors and the OS can schedule processes on any of them.
If you imagine yourself as a multi-tenant cloud provider you'll
quickly realize that you need two things:
1. Fairness (preventing noisy neighbors) when the system is fully
loaded. This is what cpu_shares does. If you give every zone the
appropriate number of shares they will all get the proportional amount
of system CPU when the system is fully loaded.
2. Paying for what you get. On a system that is *not* fully loaded, in
theory a zone could use lots and lots of CPUs. Customers would be
incentivized  to create and destroy zones until they found one that
could use lots of free CPU. This is where CPU caps come in. They
ensure that on a system that is *not* fully loaded the zone can only
burst up to a reasonable amount relative to what the customer is
paying. This also helps manage expectations. Setting a CPU cap
reasonably close to the amount of CPU that the customer gets when the
system *is* fully loaded means that people are less likely to *think*
that they are suffering from noisy neighbors (when the delta of how
much CPU you get on a fully loaded vs fully unloaded system is small,
you see more consistent performance.)

I haven't looked at the details of the SDC packages, but I can
confidently say that "vcpu" in the context of a joyent branded zone is
an approximation of what to expect based on the shares and the cap (as
opposed to a KVM VM where that's literally the number that the VM will
see).

So if you have a SDC service zone with "1 vCPU and a cap of 200" then
it's getting shares such that when the system is fully loaded it
should get approximately 1 CPU's worth of CPU time from the scheduler,
but when the system is not fully loaded it should be able to get up to
2 CPUs worth of CPU time from the scheduler but no more. The
difference between those two is what the Joyent cloud advertises as
"bursting"

Coming back for one last moment to KVM VMs, remember that the QEMU
process is running in a zone that can have shares and caps.
Additionally, when the VM does I/O, QEMU threads need to be scheduled
to do some (overhead) work to make that happen.
So in theory you might need your shares and caps to be slightly more
than just what the number of vCPUs might otherwise suggest (e.g. for

Re: [smartos-discuss] Automatically mount a zfs filesystem to a zone

[Jorge Schrauwen]

Alternatively you could also add a filesystem to mount it at zone boot. 
It's in the vmadm man page. It works relatively well.




On 2016-02-02 03:37, Bryan Horstmann-Allen wrote:

+--
| On 2016-02-02 15:29:08, Ian Collins wrote:
|

The first question: Is there any option that can make the filesystem
automatically mount after the zone rebooting


Can't you use a delegated dataset?

The second question: Can I add the additional zfs filesystem to the 
vm by

some command like ‘vmadm update …'


No.


You could use a delegated dataset and a user-script passed to vmadm to 
populate
a basic hierarchy on creation. After that, you'd probably want some 
config mgmt

handling datasets.

Cheers.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] vmadm send with delegate_dataset

[Jorge Schrauwen]

From memory (I don't do it often)
vmadm send UUID | ssh host vmadm recv
... let it fail ...
zfs send -R zones/UUID/data | ssh host zfs recv
ssh host vmadm install UUID

From what I remember it fails on the (internal only) install step on the 
vmadm recv due to the dataset being missing, you should be able to kick 
it off there again once the dataset is there.



On 2016-01-29 07:50, Anil Jangity wrote:

I am having problems using vmadm send to a remote host when I have a 
zone configured with the 'delegate_dataset' flag. It looks like it 
doesn't transfer the delegated fs so it ends up throwing errors.


Is this something that will be supported in the future?
I have a few zones with this flag, what is a workaround for it?

I've tried to do zfs send, and then on the remote host, tried to setup 
the duplicate zone manually with vmadm, but can't seem to get that to 
work either:


host1# zfs send -Rp zones/9b92f6f8-7fec-442f-91f1-8387004a12ba@sending 
| ssh root@host2 zfs receive zones/9b92f6f8-7fec-442f-91f1-8387004a12ba

…
host2# vmadm create < vm2.json

This ends up failing because it tries to re-create the file system,
which already exists.

Thanks




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Update gone bad, the Aftermath

[Jorge Schrauwen]

I will try to answer what I can, most is just based on my personal 
experience:


Upgrading:
The script you linked is fine, I wrote something close to that a while 
ago. Aside from it taken 10-15min to write the new files on the USB I 
have had not issues with doing it that way.


There is a page on how to do an inplace upgrade manually:
https://wiki.smartos.org/display/DOC/Remotely+Upgrading+A+USB+Key+Based+Deployment

You can also just rotate USB keys, take the old one, flash the new dd 
images. Swap the keys.
If the new one doesn't work you have the old one as backup!, just repeat 
on the next upgrade.


As for the password, I think it is always root/root in noinstall mode. I 
think it used to (still does?) say so in the grub menu.


Zpool:
My zones pool is just a simple mirror setup, however I use 2 SSD's 
partitioned as ZIL (mirror of p1) and 2x cache on p2)


[root@core ~]# zpool status data
  pool: data
 state: ONLINE
  scan: scrub repaired 0 in 3h19m with 0 errors on Mon Jan 25 05:19:21 
2016

config:

NAME STATE READ WRITE CKSUM
data ONLINE   0 0 0
  mirror-0   ONLINE   0 0 0
c0t5000C50048DED002d0ONLINE   0 0 0
c0t5000C50048DF3BDFd0ONLINE   0 0 0
logs
  mirror-1   ONLINE   0 0 0
c0t5001B44CB2349D0Cd0p1  ONLINE   0 0 0
c0t5001B44A1692EB7Ad0p1  ONLINE   0 0 0
cache
  c0t5001B44CB2349D0Cd0p2ONLINE   0 0 0
  c0t5001B44A1692EB7Ad0p2ONLINE   0 0 0

I have not had issues with my 2nd pool being imported after a 
reboot/upgrade.
I did do all the paritioning of the SSD on SmartOS a long time ago, and 
I don't remember the exact commands.


Regards

Jorge

On 2016-01-28 09:35, the outsider wrote:


Dear all,

Many thanks to all that helped yesterday and tonight for restoring my 
server.


Everything works fine now, but I have some unanswered questions. Maybe 
someone can shed some light on this.


Since I ran into trouble after updating my USB drive with the latest 
SmartOS version some things are unclear at this moment.


Updating SmartOS

1.   What is the recommended update/upgrade strategy for SmartOS?

2.   Where is the right wiki for updating the SmartOS USB or 
SmartOS OS?


3.   I followed and used this 
https://github.com/calmh/smartos-platform-upgrade and it seemed to work 
ok. But is ok to use it?


ZPool:

1.   I created a log and cache on a SSD, but used partitions c2d0p2 
and c2d0p4 instead of slices. This seems to have caused the biggest 
error for my Zpool


2.   The SSD was still alive but Zpool could not find the 
partitions. The SSD is not attached to the RAID controller but (due to 
some physical mounting problems) connected to the onboard SATA 
controller. Can this have caused the error?


SmartOS

1.   The new SmartOS release I burned to USB was version 
20160121T174331Z


2.   During the "no install" procedure it asked for username and 
pass. The root/root was not correct. Thanks to someone on IRC I was 
guided to 
http://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos.html#20160121T174331Z


3.   The password for root mentioned on this page was not working. 
The OS kept complaining about something and it looked to me that the OS 
was trying to verify the password to a central system. But since the 
network drivers were not loaded this failed of course. Is this normal 
or did I do something wrong?


4.   My base version was 20151210T194528Z, and I could log in with 
root/root during the "noinstall". I didn't have to use the special 
password from the webpage?


SMARTOS-DISCUSS | Archives | Modify Your Subscription



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] HELP! Update gone bad?

[Jorge Schrauwen]

I had one missing after a reboot ones and did not lose data, it was a
clean reboot so I guess all data got flushed properly before shutdown.
It may just be OK.

---
~ sjorge 

On 2016-01-28 00:20, Eric wrote:

> It's good that they're just your cache and log devices, however I'm not too 
> sure about the log device, since it holds data that'll be flushed to disks. 
> I'm not sure what the extent of data corruption will occur with faulty log 
> devices in ZFS 
> 
> SMARTOS-DISCUSS | Archives [1] [2] | Modify [3] Your Subscription
> [4]
 

Links:
--
[1] https://www.listbox.com/member/archive/184463/=now
[2] https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7
[3]
https://www.listbox.com/member/?;
[4] http://www.listbox.com



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com