14:01:44 hello, what is the command to disable a zone (vm) from autobooting? 14:01:45 I currently have booted into single user mode to try to disable zones from booting on the next reboot 14:08:39 you can try to svcadm disable system/zones 14:09:14 see zones(7) 14:09:41 Yes, but that will stop all Vm's from booting. I want to set certain zones to autoboot=diabled 14:10:33 I am a bit rusty on my solaris skills ;-)  zonecfg -z UUID .... and then something more 14:12:24 ou. yes, in that case, in zonecfg enter info and then set autoboot to false;) 14:16:29 how do i get the current config a specific zone ? 14:56:09 Roelf09: zonecfg -z $zonename 14:56:21 starts the zone config editor. 14:56:55 "info" displays zone properties; "info autoboot" is the one you likely want to see 14:57:33 "set autoboot=false" will turn off auto-boot of the zone. 15:32:33 It seems that when you go to single user mode all vm's are already on autoboot=false. So it seems imposible to mark them that way for the multiboot ? 16:18:35 if they are marked autoboot=false then they shouldn't be brought up by svc:/system/zones .. but it's possible that something else could be starting them at boot time by invoking zoneadm -z $zone boot 16:20:37 see /lib/svc/method/svc-zones: " Boot the installed zones for which the "autoboot" zone property is 16:20:38 set and invoke the sysboot hook for all other installed zones. 16:58:19 Roelf09: You can look at the autoboot property for all zones with something like: zoneadm list -cin | xargs -t -I% zonecfg -z % info autoboot 17:46:57 zoneadm list -cin | xargs -t -I% zonecfg -z % info autoboot  gives an error on every line "% Bogus zone name" 17:59:14 hmz... whilst trying to figure out how to read the dump file I discovered that the server has been auto rebooted multiple times in last hours and was able to heal itself. 17:59:14 Everything is up and running again so it seems 18:05:53 zoneadm list -cin | xargs -t -I% zonecfg -z % info autoboot gives an error on every line "% Bogus zone name"  => turned out I typed an "l" (L)  instead of capital I (i) 19:19:47 sommerfeld: you had a prototype of a sqlite3 system once. Do you still? I know it has ABI issues, that isn't a problem for me 19:19:59 Trying to evaluate the merits of how to fix this 19:21:47 "prototype" somewhat overstates it. 19:23:34 API and binary on-disk format issues, too. 19:24:16 But what I have so far might be a useful first step 19:25:10 my first bit of evaluation was looking at taking sqlite 2 dumps and importing them into a sqlite3 database via the CLI. 19:25:40 second bit was building sqlite3 as part of illumos-gate 19:28:04 the second bit I can just take and use, if necessary, since arm has no abi. 19:28:13 it just puts us on the hook to fix it so we can integrate eventually 19:28:28 but there are many things on many such hooks 19:29:36 not least an entirely distinct libm, a libsqlite-sys.so.3 would not be out of place. 19:30:34 libsqlite3-sys is what I called it (I think it will need to coexist in-tree for a while..) 19:33:45 I'll push something to gerrit as a WIP and post a link here 19:35:34 thanks 19:36:18 https://code.illumos.org/c/illumos-gate/+/4254 https://code.illumos.org/c/illumos-gate/+/4255 https://code.illumos.org/c/illumos-gate/+/4256 19:36:19 → CODE REVIEW 4254: sqlite: hack up sqlite2 shell to dump tables in ways more compatible with sqlite3 (NEW) 19:36:19 → CODE REVIEW 4255: XXXXX add sqlite3 3.47.2 amalgamation to common sources (NEW) 19:36:19 → CODE REVIEW 4256: YYYYY build libsqlite3-sys (NEW) 19:37:56 i'd name the sqlite3 versions of the database *.db3 vs *.db for the sqlite2 19:38:58 several of them are ephemeral (like the idmap cache db) which makes the on-disk format conversion problem mostly go away. 19:42:09 my problem is that the bug I have is in the sqlite printf implementation (at least, the bug I'm chasing. I haven't checked if it fixes my symptoms). It is not 64bit safe 19:42:19 I am assuming sqlite3 no doubt is 19:42:53 it seems safer to me to try to use sqlite3 than to homebrew a fix -- even a little fix -- in here. 19:43:14 (it does `va_arg(ap,int)` when it means `va_arg(ap, unsigned int)`, at least) 19:44:01 and that does seem to be my larger issue. 19:44:15 but the risks of fix v. sqlite3 are I have to admit something I don't know right now. 19:44:38 jclulow asked how smf was working, and the answer is basically that SMF doesn't deal in integers with the 31 bit set. 19:45:01 and smb either does not, or doesn't work. it's untested to my knowledge 19:51:22 `realvalue` is also `LONGDOUBLE_TYPE` but va_arg'd a `double` 19:52:36 I'm guessing they mostly mis promote, rather than read the wrong amount and throw everything off. 21:19:55 richlowe: agreed on migrating to 3 vs trying to fix 2 21:20:51 (and idmap ephemeral id's all have bit 31 set..) 21:24:37 yes, indeed, this is my fix 21:25:11 so I know what's wrong, and it's perhaps more worrying about what else might be wrong. 21:25:50 probably danmcd gets to update to add sqlite3 to his list of 2038 blockers, since it intends on 64bit-izing things as the primary fix 21:26:11 which sqlite2 won't accept, apparently. 21:34:12 I think the way to go is to integrate libsqlite3-sys, then convert everything in illumos-gate but svc.configd, then get svc.configd 21:36:28 Yes. and for arm64-gate right now it would be all 3 and a most unfortunate flag-day 21:42:07 and there's a tension between just converting over to 3 as quickly as possible vs taking the time to tweak the schemas to use features now present in sqlite3 21:43:35 (one of the things my fiddling with dump/reload uncovered is that a lot of the content of the SMF database is long hex strings. would be half the size stored as BLOBs. 22:46:34 just pushed a predraft IPD for sqlite3 22:49:53 oooh 22:54:38 it's very predrafty 22:55:11 it looks very doable, though.