08:10:18 <fenix> OmniOS r151058 has been released - https://omnios.org/article/r58 - the old LTS r151046 is now end-of-life
15:20:11 <ENOMAD> Anyone seen this on an OmniOS host before? "May  4 00:04:45 fs1 ixgbe: [ID 611667 kern.info] NOTICE: ixgbe1: ixgbe_rx_copy: allocate buffer failed"
15:20:33 <ENOMAD> One of our file servers went south this morning. It recovered fairly quickly, but not before all the VMs that got their VDIs from it died.
18:55:42 <extrowerk> new release, yess!
19:36:15 <extrowerk> naive question: where does this wording "<change-No> want xxx" in the PR description?
19:39:28 <veg> congrats on the new release!
19:51:37 <extrowerk> just updated, all systems up and running again
20:42:05 <tux0r> as always, thank you @ omnios team :) 
20:52:55 <danmcd> Updating HDC to '058 tonight!
22:11:14 <veg> my bhyve VMs are no longer booting after upgrade, I assume because of the virtio changes?
22:11:47 <veg> any config toggles one may have found to remedy the situation?
22:16:37 <andyf> What are the VMs? 
22:18:18 <andyf> There are some Linux guests which break the virtio spec. You can disable the new modern virtio interface by setting 'virtio.modern=false' in the VM parameters.
22:20:18 <veg> thanks andyf, I just came back to comment that solution
22:20:27 <veg> my guests are OpenBSD
22:21:15 <andyf> Oh, interesting. The linux bug is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045443 but I wonder if openbsd has something similar, or if it's us.
22:21:37 <veg> I just did zonecfg -z $zone 'add attr; set name=extra; set type=string; set value="-o virtio.modern=false"; end'
22:24:44 <veg> I found the following in init.log: Assertion failed: mr->name == memp->name, file ../common/mem.c, line 362, function unregister_mem
22:25:05 <andyf> I'll have to try and boot up openbsd myself.
22:25:52 <veg> looks similar to https://smartos.org/bugview/OS-6836 ?
22:25:53 <fenix> → OS-6836: bhyve Assertion failed: mr->name == memp->name, file mem.c, line 265 (Open)
22:27:27 <andyf> It certainly does. 2018!
22:35:42 <andyf> I get the same on a VM I just set up. Interesting, especially if it's triggered by the modern virtio mode
22:46:42 <veg> looks like it! I just tried "virtio.legacy=false" as well (in case the transitional glue was the culprit), but it produces the same mr->name == memp->name assert
23:08:05 <andyf> I will look into it. Mine is doing it even with virtio.modern=false, it's happening in the nvme device for me.