-
jayjwaI'm creating a zone as per: 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?
-
mighty_spikyjayjwa , here’s an example for setting RAM to an existing zone. No need to delete and start over…
-
mighty_spikyroot@server:~# zonecfg -z zone_name
-
mighty_spikyzonecfg:zone_name> add capped-memory
-
mighty_spikyzonecfg:zone_name:capped-memory> set locked=4G
-
mighty_spikyzonecfg:zone_name:capped-memory> set physical=4G
-
mighty_spikyzonecfg:zone_name:capped-memory> end
-
mighty_spikyzonecfg:zone_name> verify
-
mighty_spikyzonecfg:zone_name> commit
-
mighty_spikyzonecfg:zone_name> exit
-
mighty_spikyroot@server:~# zoneadm -z zone_name reboot
-
jayjwaThanks. Basically I'm trying this, but at the zonecfg cmd line: 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.
-
mighty_spikyIn that article, the utility zadm is used while my example use native tools.
-
jayjwaAttaching an ISO would then be under zonecfg:name:fs> then?
-
mighty_spikyFor a bhyve or kvm zone, yes. I never did that for lipkg or lx zone though since I use Triton images: docs.tritondatacenter.com/public-cl…oud/instances/infrastructure/images
-
mighty_spiky(I’m assuming you want to connect an .iso for installing the OS)
-
jayjwaRight.
-
jayjwaI've done this so many on Linux/Qemu but everything is so different here.
-
mighty_spikyOn Linux, KVM/Qemu is for virtual machines only while, on OmniOS, zones are primarily for containers but can be used also for virtual machines.
-
sommerfeldor, well, the usual way on illumos systems to run VMs is to run the hypervisor inside a zone for additional isolation and resource management.