01:19:13 <jdt> Do snapshots with bhyve actually work? I enabled the ability on the headnode, and I can issue the "triton snapshot create" command on a new bhyve instance with "Flexible Disk" selected. But the job ultimately fails with: vmadm.create_snapshot error: vmadm exited with code: 1 signal: null
01:20:48 <jdt> I'd love to use LX containers more, but I just run into so many weird problems with them.
02:26:38 <nwilkens> @jdt yes, we have it working at mnx.  I'll have to dig up further details tomorrow, but if I recall, you'll need to have packages sized with a quota at around 2x the disk size to allow for snapshot space.
02:27:34 <bahamat> jdt: That should be fixed in release-20231116 and later.
02:28:21 <bahamat> jdt: Oh, also the guest needs to fstrim regularly.
02:33:00 <jdt> Okay, thanks. I did just update all of the zones and platform images to the latest this week. bahamat like a cron job to fstrim? And mwilkens, let me know what you find tomorrow - thanks!
02:33:29 <bahamat> jdt: Yeah. All of our current HVM images have fstrim cron'd by default.
02:33:38 <jdt> Okay, cool.
08:13:25 <symgryphon> I just installed smartos, but wheng I do imgadm avail it hangs forever.
15:29:51 <xmerlin> I just saw an old bug reappear, 'ttymon: set_termio_ get_ttymode failed: Timer expired' / 'ttymon: initial termio on (/dev/wscons) failed', when booting up a server to which I downgraded to 20231130T043122Z following the bug on the Mellanox CX4 cards.
15:30:25 <xmerlin> Any suggestions?
15:49:57 <danmcd> xmerlin: Off the top of my head, I say wait for tonight's release spin, only so future debugging can be up to date.  (Yes the CX-4 fix will be in there.)
15:50:31 <xmerlin> danmcd, thank you very much
15:51:02 <jbk> speaking of that, should I ping Alex to see if he wants to take a look at it?
15:51:23 <danmcd> Yeah, though he might have new-semester overhread.
15:55:09 <jbk> i'll shoot him an email since he's not on irc recently
22:30:43 <jdt> I did get a bhyve snapshot to work. But I'm a bit confused about bhyve flexible disks. I adjusted the quota to 20GB (it was at 10GB) and kept a flexible disk assigned at 10GB. The image disk seems to be 10GB as well. So I suspect that it's just the act of making the quota twice as big as the inherent instance drive that allows for snapshots - is that correct?
22:31:42 <jdt> Secondarily, the additional disk shows up as assigned in adminui, but is nowhere to be seen in the instance itself (i.e., there is no /dev/vdb and 'triton instance disk list' shows only the one 10GB drive). I'm not sure what to make of that.
22:32:27 <jdt> This is a debian-12 (20231127) instance fwiw.
23:33:38 <jdt> Hmm. Or maybe what I'm seeing in adminui is just the primary disk. Looking at the PCI_SLOT, that is what shows up in lspci. So I'm probably just misunderstanding the configuration. I thought "adding" a disk to the bhyve package would result in an additional disk, but it looks like it's just sizing the primary disk. I imagine adding a second one would show up as a separate drive.
23:54:36 <jdt> Yep, that seems to be it. "Quota" represents the space required for all disks. "Disks" represents all disks on the system, inclusive of the primary, system disk (that's where I erred - I thought the system disk was separate). "Quota" needs to be  about twice as large as the space allocated for all of the disks defined in "Disks".