11:27:45 when https://downloads.omnios.org/media/bloody/ gets rebuild? my miniroot just fails on pci symbols, so I thought I better wait for the ones in here 12:13:36 That sounds like you're missing https://github.com/omniosorg/kayak/commit/fadaf6ee465975d6d31214ba434d068538787c7e which is a couple of months old. Are your repos all up to date? There will be a new bloody release and media sometime today, which will have the vioscsi driver. 12:13:51 Bloody is usually updated weekly, and media every few weeks depending on what's changing 12:34:27 Hmm latest r151046 seems to now hang crash on linode with https://imgur.com/nwtEHS5 12:34:54 andyf it's only a 1G memory system though, so maybe one of the recent changes is causing issues but I would not expect hat withint a release to happen 12:37:18 interesting, booting an older BE doesn't help either 12:48:14 the smb stuff in the stack are weird though 12:48:25 I haven't been able getting a succesful boot 12:48:38 while I have 2 other VMs running on the n release 13:00:30 Anybody know an illumos friendly EU hosting provider that does not cost an arm and a leg per month? 13:00:46 Linode was great for the last 3ish years but seems there new hypervisors don't boot illumos anymore 13:03:46 Looks like I am now hitting https://github.com/illumos/illumos-gate/blob/445784c00080f22524a1a4659cf8b7b2e1ad84d1/usr/src/uts/common/vm/vm_page.c#L2311C1-L2312C1 13:04:08 Which hasn't been changed for 19 years 13:04:23 That would also explain why I am hitting it on all versions I have going back 13:31:25 https://imgur.com/nwtEHS5 13:31:33 Looks like it got booted on a newer hypervisor 14:11:46 I've had some success with Digital Ocean 14:11:59 Tribblix is currently hosted on AWS 14:12:55 The costs for the instance and storage are actually the same, but AWS charges a fortune for bandwidth whereas DO gives you a good inclusive allowance 14:28:13 I never got omniops to work on DO when I tried 14:28:27 had a look at hetzner as some collegues use that for there linu stuff and they seem happy 14:28:35 But can't get omnios to boot either 14:29:01 Well I tried dd the cloud.raw and bhyve images via the resqueue system 14:29:03 But no luck 14:29:28 Ideally I'd like to get linode to boot again though, pretty happy with them 14:37:42 It's probably the disk type on hetzner tbh 14:37:51 I'll check what it is in the rescue image 14:38:33 Yeah vioscsi 14:42:49 sjorge - that seems unfortunate, the new hyperisor. 14:43:11 Yeah, luckily my mail server is still up that DC is schedule to be update next months 14:43:14 I wonder what they've done that triggers this for you (although 1G is really minimal with ZFS) 14:43:31 some maintanance 14:43:36 in the Dc it was hosted 14:43:50 So I assume they rebooted the old hypervisor and it brought the VM up on a newer node 14:44:06 1G has been a bit tight but but working pretty well for my tiny work loads 14:44:36 I looked around but there is no tunable to it seems to try and change the bahvior to try and allocate less 14:44:39 At least not that I found 14:46:06 andyf do is there a raw image somewhere that has the vioscsi driver installed (and boots over graphics console) 14:46:10 No serial on hetzner 14:46:15 but there is a VNC based kvm 15:02:17 No. The next raw image will have vioscsi, but all of them use the serial console. 15:02:27 I think you can get to loader early via VGA and reconfigure it though 15:05:25 I only saw the BTX line but nothing after that one... one of the cloiud images 15:05:44 Do the bloody images have vioscsi ? 15:05:48 I could grab one of those too I guess 15:08:05 The bloody cloud images have vioscsi, yes, the installer does not yet. 15:08:13 but you don't need the installer if you use cloud images 15:08:47 OK let me try with that one 15:08:56 it might not show more than the BTX line because loader can't load it's confiog 15:11:50 Let's see what omnios-bloody-20240215.cloud.raw.zst does 15:12:49 https://imgur.com/ibP5DuB same 15:12:53 Just this and nothing 15:14:36 andyf do you think the 1G is the issue, I could bump it to 2G for 2x the price I pay now 15:14:45 But I can never shrink it if that was not the problem 15:16:03 Yes, I think it probably is. It seems pretty clear that it can't allocate enough kernel memory. What would be interesting is why it either need to allocate more than it used to, or why there is less available now. Either could be true based on the hypervisor or SMBIOS data or whatever. 15:21:15 Let's try that I guess 15:21:36 It looks to me that we're getting nonsense out of smbios 15:21:41 Worse case it's one month of extra billing as if it doesn't work I'll probably delete it once I do find a place to run. 15:21:57 Can you exclude the smbios kernel module? 15:22:13 It's still resizing to 2G linode vm, can take up to 1h :| 15:22:26 But I do have loader access so I think I could probably disable that 15:24:08 Dropping to the 'ok ' prompt and typing 'boot -B disable-smbios=true' is worth a try 15:25:55 https://gist.github.com/sjorge/e289838988ce141096cdb4d9a6242e34 2G image did not help, dif error now 15:26:02 will try with boot -B disable-smbios=true 15:27:03 OK now I can't catch the loader prompt as it's gone to fast -_- 15:27:13 probably because this image also adds an extravcpu 15:27:55 Same with smbios disable 15:31:59 sjorge: https://spearhead.cloud is a Triton public cloud provider in Romania. I'm not sure about pricing, but at least they are illumos friendly! 15:32:41 Interesting, adding it on the list of to check out 15:34:21 If you need an image that drops to the debugger by default, I can build one. 15:35:31 Ooh pricing is nearly 4x of what I pay now on linunode for spearhead 15:35:35 That's a bit much 15:35:50 At that point phrotonmail + a tiny freebsd VM makes more sense 15:36:06 @andyf I'm booting from disk on linode 15:36:18 But when I can beat the boot to loader, I tried kmdb 15:36:22 But it never get's there 15:36:31 It hits the issues super early in boot I think 15:41:46 Hmmm seems proton mail is cheaper than I though, I'll have to seriously consider that option 15:41:51 It would save me some pain 15:42:14 You can try -B kbm_debug=1 for more early output too. 15:51:03 https://gist.github.com/sjorge/59d1021916230151a15b53ccd9e9334c 15:59:47 Seems i can get freebsd to install on hetzner... I guess I'll rebuild on that so my site is back up today and then figure out if the linode one is salvagble 16:05:19 Hey all; we did the following: zfs snap -r rpool/zones/zone0@ready; zfs send rpool/zones/zone0@ready | zfs recv rpool/zones/zone1 ; zonecfg -z zone0 export -f zone1.cfg ; (modify zone1.cfg) ; zonecfg -z zone1 -f zone1.cfg; zoneadm -z zone1 attach -F; 16:05:31 at this point we can boot zone1, however, the IP address is not set... 16:06:13 in zone0 there was zone0/_a address. I assumed there would be also zone1/_a in zone1, but there's not 16:06:15 any thoughts? 16:29:20 okay... we just needed to change the IP interface name in /etc/ipadm/ipadm.conf in zone1 16:48:23 antranigv ah the cloning the zone took all the data to the new zone but it did not repect the allowed-address as ipadm.conf had 'invalid' config? 16:52:33 neirac yes. just needed to sed the ipadm.conf file in the new zone. 16:52:52 I don't understand why the zone with allowed-address needs an ipadm.conf file anyway. 16:53:52 So the two concepts are kind of independent. 16:54:09 allowed-addresses is about saying from outside the zone what's allowed or not to come from that zone's netstack. 16:54:12 sjorge, nwilkens: I had bad experiences with Spearhead staff. and I tried twice, few years between tries, thinking that maybe it was me... 16:54:18 It has nothing to do with what addresses are used inside the zone. 16:54:42 In general manually editing ipadm.conf is fraught and not intended to be used with sed. 16:54:56 But basically that is a record of what IP interfaces and properties should exist. 16:55:17 So that's always something that exists on a per-zone basis as the two ipmgmtd instances are independent effectively (it's a bit more nuanced, but it's better to think of it that way). 16:55:34 If you think of the zone as an independent host logically, it makes sense that it'd have to have its own networking configuration. 16:56:08 The allowed-addresses really is just a way of providing an ACL of what addresses the zone can send traffic out with. 17:13:59 rmustacc got it 17:14:39 rmustacc I still have to think about the best way to do a deep copy "zfs send/recv" of a zone, either on same host or another 17:15:08 in our case we wanted to create ldap1 from ldap0, where ldap0 is the current prod, but ldap1 should be our testing. 17:15:28 Another question raised while we were testing things... zadm snapshot/rollback 17:15:57 We got an error saying "WARNING: rollback is not supported on BE-aware brands." 17:16:13 So I thought hey, I'll use beadm from inside the zone... I guess? 17:16:21 I need to figure that out 17:16:47 basically I need to zadm shutdown ldap1, rollback to a be named ready, and then continue 17:17:08 continue == zadm boot ldap1; destroy things again by testing LDAP :P 17:20:45 antranigv: what about: zfs snapshot of filesystem ldap0, then zfs clone to ldap1 and adjurst paths eventually. costs are near zero. 17:25:03 tomww as a matter of fact, the `zoneadm -z ldap1 clone ldap0` command does that automatically and work flawlessly. I was worried that we might "promote" ldap1 to production if this large changed worked fine, so I really wanted a deep copy. 17:38:13 this prtconf -D output means the driver is attached or not ? pci108e,8 (driver name: vioscsi) 17:38:38 because I see also pci108e,1, instance #0 (driver name: vioif) , and vioif I do see in modinfo output 17:39:31 That generally means it's attached. 21:42:34 Good thing most of my ‘can get it to work on illumos’ VMs are home are freebsd, website back but on freebsd 21:42:44 Should be cheaper too starting next month 21:43:05 Now i need to figure out ehat to do for email before thst vm bites the dust 22:56:44 sjorge what website is this? :) 23:11:34 Just my personal ones 23:12:00 A rarely used blog :|, travel pictures, my map software I use for my dnd games, ... 23:19:31 prtconf -d says this pci108e,8 (pci1af4,1004) [Red Hat, Inc. Virtio SCSI] (driver not attached) ; I don't see any message about why the driver did not attached