17:08:12 I'm creating a zone as per: https://omnios.org/setup/firstzone? but I forgot to set the RAM amount. Now when I go back to zonecfg, it says syntax error when I try to "set ram=4G". Do I have to delete the whole zone and start over? How to edit settings? 17:34:50 jayjwa , here’s an example for setting RAM to an existing zone. No need to delete and start over… 17:34:58 root@server:~# zonecfg -z zone_name 17:34:58 zonecfg:zone_name> add capped-memory 17:35:00 zonecfg:zone_name:capped-memory> set locked=4G 17:35:01 zonecfg:zone_name:capped-memory> set physical=4G 17:35:03 zonecfg:zone_name:capped-memory> end 17:35:04 zonecfg:zone_name> verify 17:35:05 zonecfg:zone_name> commit 17:35:06 zonecfg:zone_name> exit 17:39:57 root@server:~# zoneadm -z zone_name reboot 17:41:59 Thanks. Basically I'm trying this, but at the zonecfg cmd line: https://blog.daveeddy.com/2022/09/19/void-linux-bhyve-image-on-omnios/ and with a different image. It's confusing because it says "ram" there and also "cdrom" but you can't set either by those terms. 17:44:35 In that article, the utility zadm is used while my example use native tools. 17:48:43 Attaching an ISO would then be under zonecfg:name:fs> then? 17:54:44 For a bhyve or kvm zone, yes. I never did that for lipkg or lx zone though since I use Triton images: https://docs.tritondatacenter.com/public-cloud/instances/infrastructure/images 17:57:51 (I’m assuming you want to connect an .iso for installing the OS) 18:00:33 Right. 18:01:32 I've done this so many on Linux/Qemu but everything is so different here. 18:19:00 On Linux, KVM/Qemu is for virtual machines only while, on OmniOS, zones are primarily for containers but can be used also for virtual machines. 18:20:44 or, well, the usual way on illumos systems to run VMs is to run the hypervisor inside a zone for additional isolation and resource management.