06:02:07 vetal this sounds like the value names are not getting translated... 08:27:31 tsoome: Yes, I think so. Do you think that reason for a ticket ? Also is there any docs how to use it? 08:28:22 ticket is always good 08:34:59 man eeprom is documenting acpi-user-options 08:36:04 I think this whole mechanism needs review, there is too much talk about solaris 10;) 08:39:12 is it possible to integrate inter-zone dns via the zone names? comparable to docker-compose service names? e.g. in docker-compose i can give a container a name (e.g. postgres-service), and via its name it is accessible for other services. e.g. i can use URIs like postgres://postgres-service from another service 09:04:55 id like to cut out handling IP addresses 10:13:27 properguestt: not that I'm aware of 14:39:46 it seems like it could be a neat idea.. though at the same time, being limited to a single physical system seems like it'd limit its usefulness 14:40:49 also, you can give a zone multiple ip addresses... how would that be handled? 14:41:38 in docker-compose you make sure that the containers share a common virtual network 14:41:39 that or you give it a vnic (and often limit the vnic to only allow a specific ip address, which is effectively the same thing) 14:44:53 the host OS could handle dhcp and dns for each virtual network 14:45:12 and for the containers 16:00:51 danmcd / andyf saw the mail about new bhyve sync and uart, would the normal vm’s serial console also use that code? If so, been accessing my vms over serial for a while now without issues 16:14:28 It is the serial console, but... it's used by mdata-client too, and it failed on {Free,Net}BSD guests until jperkin fixed it. 16:15:08 https://smartos.org/bugview/OS-8556 16:15:10 → OS-8556: bhyve uart is too fast (Resolved) 16:15:36 His tracking down of this is all there on the bug report; pretty instructive. 17:45:00 Interesting, I have bot hit that at all with just using the serial console 17:45:09 But I doubt I hit those rates 20:09:19 jbk: multiple addresses wouldn't be a problem as you can assign multiple A records to a DNS hostname. 20:10:19 jbk: multi-host configs could be dealt with via dns dynamic update 20:22:55 yeah, but most things tend to take the first response (which even if the DNS server is rotating or randomizing the order), tends to cause more problems than it solves 20:23:08 unless it's being used by a client that really is explicitly expecting it 20:23:11 incus (fork of lxd; container daemon on linux) manages dhcp and dns for inter-container communication using virtual networks without the user manually handling any IPs 22:00:28 properguestt: If it's all on one system, and you were itching to get going, I would probably just write out new /etc/hosts files in all the zones haha 22:00:56 very pragmatic solution 22:01:35 is it actually possible to share unix sockets between containers? maybe using bindmount/nullfs? 22:01:43 *zones 22:17:46 The global zone can see the non-global zone file systems. 22:18:03 I guess if you set up some shared loopback mount, then I guess you probably could.