hi

I would like to ask how to set up cloud-init on SmartOS under the BHYVE brand with a custom ISO installation. I mean that I'm not using the official Joyent image. What I want to do is configure the network with cloud-init in a BHYVE VM. I have installed cloud-init, all related services are enabled, I also set up the serial console in the grub, etc. It seems to be working because under '/var/lib/cloud/instances' the VM UUID is created and I can see the IP

settings I specified in the metadata on the SmartOS host in the 'obj.pkl' file, but for some reason, it doesn't execute them. The datasource_list [ SmartOS ] is, of course, set. I checked the official Joyent image and applied the same settings that are in the '/etc/cloud' folder, and the kernel parameters in the grub are the same, yet it doesn't work for me.

Any ideas?

problem solved

unix - nice

I tried to rebuild my one LX zone today, using:

632a25ad-15dc-42f0-a23b-743b37f62cbb alpine-3 20240726 linux lx-dataset 2024-07-26

It's tres unhappy. I think the main problem is that dns is hosed.

e.g.:

cats:/var/log# host cats.h-net.org

netmgr/udp.c:1021:isc_nm_udpconnect(): fatal error: RUNTIME_CHECK(result == ISC_R_SUCCESS || result == ISC_R_NOTIMPLEMENTED) failed

Aborted (core dumped)

Can you ping it?

yes, and since ssh is running right now, I can ssh to it.

(In an earlier attempt, ssh wouldn't run.)

I mean, can you ping cats.h-net.org?

nginx won't start because it can't look up its syslog server to send logs to.

yes

by name?

yes

dns service in the environment is fine

but something about resolution on this machine is hosed

this guest

Can you ping it by name from inside the guest?

yes, but its name is in /etc/hosts

What if you take it out?

`dig` does similar things to `host`

oddly, `apk update` works

dig and host both set privileged flats on packets. They don't just do gethostbyname().

yes, can ping from inside the guest by name even without its name in /etc/hosts

oh, and this is an alpine image

ah, there it is, I did say that

Do you have a dns server declaration in the nginx config?

no, haven't ever needed to

lemme see

doesn't help

but doc says that's for looking up upstream servers (in proxy, I think?) so maybe it doesn't use it to look up syslog servers to which it will send access log data.