09:10:00 <ik5pvx> per dire al comando che e` finita la lista di opzioni,  e quel che viene dopo sono arguments
09:10:07 <ik5pvx> ops, E_WIN
12:48:21 <antranigv> I'm trying to setup OmniOS on Digital Ocean, it works fine, I can login and all, but I'm not able to see the console. I'm not even sure if it's a VGA screen or a serial console.
13:08:47 <neirac> antranigv Petertribble has things hosted in DO, we could have some pointers
13:09:34 <neirac> antranigv ptribble
13:11:32 <antranigv> neirac another interesting thing is that I cannot reboot. it shuts down, but does not come up. Should I use `reboot` or `shutdown` with some flags?
13:11:50 <ptribble> I just ssh into anything on DO, so don't recall ever looking at the console
13:12:31 <andyf> There's an omnios mirror hosted on DO too. It's a VGA console
13:13:11 <andyf> and the hang on reboot/shutdown is likely https://www.illumos.org/issues/14526
13:13:12 <fenix> → BUG 14526: illumos guest hangs on reboot under QEMU 6.0.0 (New)
13:13:31 <andyf> We found that some of the VM types in DO work fine, but others hang like this.
13:20:32 <antranigv> andyf so I guess there's no way to bypass that right now. 
13:21:29 <andyf> Until it's fixed, wherever the problem lies, you have to stop the VM through DO's console, instead of rebooting from inside the guest. It is far from ideal.
13:21:47 <andyf> If it's stuck, sometimes you need to get support involved, or I think somebody once found that it did fix itself after a while
13:23:44 <andyf> and we need to work out what's going on - from what is in that issue it should be reproducible with QEMU 
13:35:27 <neirac> antranigv is your rge card still dead?
13:37:46 <tsoome> antranigv shutdown is wrapper script over setting init runlevels. reboot and poweroff commands are ok to use unless you want to have announces.
14:01:17 <antranigv> tsoome danke! learning new things every day :)
14:01:36 <antranigv> neirac going to the lab to check right now. btw I noticed that our "revisions" are not the same
14:02:03 <antranigv> andyf wish I had the knowledge to do that myself. but not really
14:11:51 <neirac> antranigv which revision is yours?
14:12:15 <antranigv> neirac 2
14:12:21 <antranigv> neirac yours says "c"
17:16:31 <neirac> antranigv try this rge driver, http://neirac.srht.site/resources/drvs/rge , you need to ipadm delete-if rge, then modunload -i (check rge id from modinfo), then copy to /kernel/drv/amd64/rge ; modload -p drv/rge , ipadm create-if rge0; ipadm create-addr -T dhcp rge0/v4 or static
18:24:39 <antranigv> hey neirac , I'm here now. I will load and try
18:41:25 <rmustacc> What's different?
18:48:31 <antranigv> neirac it didn't work. dladm keeps saying unknown and I still can't send/recieve packets
19:00:03 <neirac> any new messages in /var/adm/messages? should be debug messsages  there
19:01:43 <antranigv> neirac rge_dbg_enter(0): rge_attack
19:02:07 <antranigv> neirac Using FIXED interrupt type#012
19:02:07 <neirac> antranigv ok
19:02:16 <antranigv> rge0 registered
19:02:29 <antranigv> s/attack/attach
19:12:38 <antranigv> neirac I reset the BIOS, and now I see LINK at the other side
19:16:48 <antranigv> neirac IT'S ALIVE!
19:16:51 <antranigv> neirac what did you change?
19:19:54 <neirac>  antranigv when you say, I reset the BIOS you meant rebooted after copied the driver? 
19:20:01 <antranigv> neirac yes!
19:20:12 <neirac> Do some tests and let me know how it goes
19:21:12 <neirac> fill a bug in illumos issues with the info you have so, if this fix is really working, it could be submitted 
19:22:15 <rmustacc> Well, what did you change?
19:22:31 <neirac> interrupt handling
19:22:36 <rmustacc> Just disabling MSIs?
19:22:43 <neirac> yep
19:22:46 <rmustacc> Because that's not a general purpose option.
19:23:01 <rmustacc> So if that's broken, we need to understand why.
19:23:50 <neirac> yeah, so antranigv should use hte nic to see if all is working as expected then I think we could know if that fixed the problem
19:24:03 <rmustacc> Well, we don't know that the problem is so I don't think we can say it's fixed.
19:24:10 <neirac> I agree
19:24:22 <rmustacc> We've worked around and changed a bunch of things. But that driver is used for a lot of parts and I don't think we can accept a generic disable MSI fix.
19:24:36 <neirac> oh, is only for certain models
19:24:39 <rmustacc> Maybe an interim to make it more tunable to help here, but for example, the 2.5G adapters and related don't want that.
19:24:42 <neirac> where you disable MSI
19:24:56 <rmustacc> Is there a specific hardware erratum or quirk that led to that?
19:26:01 <antranigv> what do I restart to reload the routing table?
19:27:04 <neirac> rmustacc https://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/io/rge/rge_main.c?r=0dc2366f#1731
19:30:27 <antranigv> neirac should I restart the machine with the OLD module? maybe someone messed up the bios
19:32:25 <neirac> antranigv yes, do that so we are sure the driver change was the fix
19:34:14 <neirac> could be the bios change that made things work also
19:34:25 <neirac> so just to be sure, restart with the old module
19:37:24 <antranigv> rebooting
19:38:10 <neirac> ok, so this test is with the new BIOS settings and old rge module right?
19:38:59 <antranigv> yes.
19:39:19 <antranigv> works
19:39:36 <neirac> ok, so the bios was the fix, awesome!
19:39:52 <neirac> what was the bios change?
19:40:01 <antranigv> Load LAN ROM
19:40:05 <antranigv> I have no idea what it means
19:40:07 <antranigv> it was disabled
19:40:14 <antranigv> then I reset the BIOS settings
19:40:16 <antranigv> and it got enabled
19:40:23 <antranigv> I though hmm okay, good to know
19:40:25 <antranigv> and now it works
19:40:26 <antranigv> weird
19:40:54 <neirac> better document that somewhere if someone has the same problem at least could search on the illumos.issues page
19:41:49 <antranigv> btw I'm getting 300kbps connection from the pkg IPS mirror. is that normal? I get ~1Gbps with our Dutch datacenter
19:42:06 <antranigv> or rather, the origin, not the mirror
19:42:20 <antranigv> who's responsible for the mirrors? I might be able to sponsor a server in Armenia
19:43:28 <neirac> andyf could know,  https://omnios.org/info/ipsrepos
19:44:02 <andyf>  It's the omnios core team - we have a couple of mirrors in Western US at present, and the main server is on a fast connection in Switzerland.
19:44:16 <andyf> (At ETH Zurich)
19:44:44 <andyf> If you configure a mirror, IPS tries to work out where it's getting the fastest responses from and adapts.
19:49:55 <antranigv> andyf how big is the mirror? I have 1Gbps, I will be getting 10Gbps this year, and we have a lot of storage that we can allocate.
19:55:19 <andyf> They current have two disks, one 80GB for the OS (that could probably be a bit smaller), and one 300GB for the data
19:55:56 <andyf> current size on one of the US ones is 150G on the data disk, but that varies and does go up around release time when there's an extra release running
19:58:01 <antranigv> andyf oh we can donate that much for sure. I can provide a VM for you to access, a static IP dedicated and 1TB of storage
19:58:56 <antranigv> for CPU and RAM, the host is running 256 cores and 2TB RAM. I have to allocate 1.5TB to a Ubuntu VM, but the rest is pretty much mine.
19:59:07 <antranigv> it's much smaller than I expected
20:00:07 <neirac> antranigv that's awesome, building omnios should be quick there
20:01:18 <antranigv> yeah, you can use it for building too. I tend to dedicate the vCPUs as well. I currently allocate 200 to the ubuntu machine (altho might get pushed to 240), but the rest is there. or maybe I just keep 200 for he scientists and keep the 56 for me :P 
20:05:11 <neirac> I was happy when I had 16 cores on an old dell but the thing was too loud I was getting deaf so I had to sell it. do a test how much time takes to build omnios with 56 vcpus
20:08:23 <andyf> In terms of RAM and CPUs, we currently have 16GB and 8 vCPUs. Let me take it to the other omnios maintainers. Thanks for the offer!
20:08:36 <antranigv> andyf thank you for keeping the sun on :)
20:14:18 <neirac> andyf here is a current change to lxbrand that could be nice to have https://github.com/TritonDataCenter/illumos-joyent/commit/80cb3c4338b7da5b0912e39e90712cc7ddef8b49 
20:15:58 <andyf> Yes, I saw that land in SmartOS. Nice work, we'll pull it into OmniOS next week
20:18:34 <neirac> andyf great!, thanks Andy
22:47:02 <aeonjeffj> Weird question. I know my way around zfs fairly well and did a lot in Solaris in the 90s. I have missing rpool capacity and can't seem to figure out why.  rpool is a mirror of two ssds, 438GB in size. 
22:47:08 <aeonjeffj> rpool/build          430.12G 37.52G    409.89M    99%    /build  
22:48:50 <aeonjeffj> I can't find any quotas enabled or any explanation for why it is 99%. A recursive du of all top level directories only accounts for about 60GB of the 430GB yet I'm "out of space". rpool recordsize is 128K but I can't imagine it would be so inefficient that I'd lose 370GB
22:54:04 <nomad> The first thing I always check when people ask me about missing capacity is snapshots. Do you have any and are they taking up that space?
23:25:48 <aeonjeffj> Only the install snapshot which isn't large
23:25:49 <aeonjeffj> rpool/ROOT/omnios-r151048@2024-01-24-21:10:50   780M      -     3.35G  -
23:29:14 <aeonjeffj> Oh cr⊙p it's swap and dump. I'm mostly a Linux guy since late 90s. Not used to boot on zfs. But thanks for pointing me in a direction
23:29:56 <nomad> Glad to ... help? :)