00:14:37 bahamat, Thanks for the answer, I think the problem is that, the vnc had issue with smartos, and all vnc viewer client are blank screen when connect to :< port for a VM> 00:29:49 tozhu: I can assure you that's not the case. 00:30:49 We use it all the time. Like, every day. If it was just flat broken, we'd for sure know about it and fix it because it's critical for us. 00:31:38 That's one reason this round of vm images took so long to put out, we wanted to make sure 100% that images could boot either KVM or bhyve, with either BIOS or UEFI so that vnc will for sure work. 00:31:54 The requirement for VNC is kvm with bios or bhyve with uefi. 00:43:59 bahamat, thank you, waiting for the new image 00:53:50 bahamat: VNC works after update the VM and set bootrom=uefi 02:24:08 I have other question regarding to smartos, I have 24*1.2T disk machine with 384G memory, ‘zpool iostat’ command says had 7T space, but for ‘zfs list’ command, it reports only had 110G space, what’s the issue? here is the details https://pastebin.com/zwQybdFT 02:27:56 sjorge: What C.M. do you use now? 03:07:16 tozhu: The zpool command will report to you allocated vs unallocated blocks. The zfs will take into account reserved space that is not yet written to. 03:07:58 so, actually I had 7T space on the machine? 03:08:55 tozhu: for example, if you have a 100T pool with a single two zfs datasets on it. Both have 25G written, so there's only 50G written on disk. But one of them has a reservation of 50G. The other one will see only 25G available. 03:09:29 Even though the first one has only written 25G, it has 50G guaranteed to it, which means the second one is not allowed to write to it ever for any reason. 03:09:42 So avail is free - reserved 03:09:55 got, Thank you very much, I’ll release some space, thanks again 03:11:07 When you have kvm or bhyve, they will always have a reservation. So the size of their disks is unavailable, even if they are not allocated (i.e., free). 03:11:46 If you remove the reservation on them then you'll see all of that free space become available. 03:12:29 However, you can cause severe damage to your guests if they try to perform a write to space they think they have, but isn't actually free. 03:13:18 A guest that fills up the virtual disk, the guest kernel will return out of space errors to the application. 03:14:57 Whelp, he quit. So I guess he won't find out that if you actually run out of free space because you removed the reservation then the vmm will start returning I/O errors to the guest kernel which causes data corruption for the guest. 06:21:41 bahamat, a big thanks 08:10:23 copec currently none 15:53:42 hi, I've just upgraded 1.17 bedrock (android minecraft) servers for kiddos to latest 1.20 and they're eating memory like crazy. 1.17 was fine with 512M limit, 1.20 allocated 775M in 2 hours of uptime. Anybody running this too? Any way to check if this a memory leak or normal behavior? 20:57:27 sjorge: My personal salt states have become my own documentation for how I set stuff up. I mostly start salt minions just to set stuff up, and call specific bootstrap states, but don't highstate across the board 20:57:48 I'm amazed how much I forget after setting up a bunch of stuff a few years ago 21:04:22 i used to do both standalone bootstrap runs and minion->master runs