03:15:19 <papertigers> How does one add multiple bugs to the same CR?
03:24:43 <rmustacc> papertigers: Just put one bug/line in the commit message.
03:27:18 <papertigers> rmustacc: thanks, wasn't sure if that was correct for how do commit messages in gate
03:29:47 <rmustacc> Once a cr's up we can always change it, so don't worry too much.
10:01:02 <sjorge> Hmm I winder if Ian on the list is also bitten by the same viona issue i always am, forgot where I got stuck with https://www.illumos.org/issues/15464 ... 
10:01:03 <fenix> → BUG 15464: Change the viona default to copy tx buffers instead of loaning them by default (New)
10:01:20 <sjorge> I wonder were my dev VM went too
13:18:46 <sjorge> I haven't found the VM but I did remember where I got stuck on, I was on sure how to deal with the logic in viona_tx_copy_needed() I could just add a new flag 'always copy' that defaults to try as propose in the original diff in https://www.illumos.org/issues/15271
13:18:47 <fenix> → FEATURE 15271: Want tunable to force viona to always copy tx buffers (New) | https://code.illumos.org/c/illumos-gate/+/2565
13:19:00 <sjorge> That also allows an easy out that would still do the proper thing on bnxe
13:19:07 <sjorge> But not  sure that would be good enough
13:19:35 <sjorge> As that was originally rejected in favor of just documenting how to set the other enum.
17:12:57 <gitomat> [illumos-gate] 15815 Errors in the urtw(4d) manual -- Peter Tribble <peter.tribble⊙gc>
19:32:20 <tsoome> dos bhyve have gdb stub?
19:32:43 <tsoome> does*
19:33:28 <tsoome> ah, ok -G.
19:53:45 <richlowe> papertigers: we can even leave comments on your commit message as part of code review, no need to worry about it in gerrit. :)
19:54:36 <papertigers> richlowe: thanks, that's how I got myself duplicate CRs.  Or I pushed to the wrong ref
19:54:57 <richlowe> the changeid needs to be constant, for updates.
19:57:03 <papertigers> yeah I should have the hook for it from previous gerrit usage.
19:57:44 <tsoome> hm: ERROR:root:Error b'bhyve: gdb address resolution: non-recoverable name resolution failure
19:57:55 <richlowe> I doubt it's tested much
19:58:04 <tsoome> seems so:(
19:58:05 <richlowe> though I desparately wish there was an mdb backend to talk to a gdb stub
19:58:13 <richlowe> which I bet would perk up the old timers.
19:58:34 <tsoome> there is very sketchy patch from jeffpc;)
19:59:33 <tsoome> never had time to get it to do useful work:D
20:00:42 <richlowe> I've used the qemu gdb stub quite a bit, but never with an accelerated backend like kvm.
20:01:12 <tsoome> yes, one in qemu is quite nice. 
20:01:30 <tsoome> one in vmware fusion is quite buggy
22:58:08 <tozhu> I would like to ask some question about oxide’s crucible project, is there anyone could answer?
23:46:02 <tozhu> I’m going to test crucible and use it as my backup / archive / database space cross physical node, but I don’t know how to use it;  I have 3 postgresql node(smartos vm), each postgresql node had it’s space for database, the same archive/backup space to store archive log and database backup; if then, how many downstairs/upstairs instance will be create?  how to link the space to database vm? best wishes