This is the critical step missing from every “guide” I’ve seen, most of which seem to be near-verbatim copies of the same old article. Remove the cloud-init netplan file, as well as any other configuration files that you don’t want in the final VM template. Remove netplan file(s) rm /etc/netplan/50-cloud-init.yaml This will clear the existing hostname and reset it to localhost. You can safely ignore the message about a mail folder not existingĬlear the hostname truncate -s0 /etc/hostname hostnamectl set-hostname localhost An example of the cloud-init section in oVirt is pictured below. If you plan on installing any packages you’ll also want to setup a network interface with access to the internet or local repos. Assuming you’re using the Ubuntu Cloud Image linked above, you’ll want to go ahead and set a username to login with. Go ahead and fire up the VM you imported. There are plenty of guides for doing this in vSphere and Hyper-V, but oVirt docs seem a bit lacking so if you’re unfamiliar with the process you can check out my article on How to import an OVA to oVirt 4.4. The end goal is to import the OVA as a virtual machine. I’m using the OVA (open virtualization appliance) which should be applicable to oVirt/RHV, Hyper-V, and vSphere (Direct Link: ). The first step is to grab the cloud image in your preferred flavor from. Making a custom Ubuntu 20.04 LTS (Focal Fossa) VM template that works with cloud-initĪfter searching and finding no good resources on how to make a custom VM template that works with cloud-init, I decided I’d write my own guide so others out there don’t feel so intimidated by this process or go through the same headaches of following guides that are outright wrong or miss critical steps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |