You may find it easier to modify the template build script rather than perform manual changes to an existing template. We use this approach to building our own system VMs and it's worked well.
Building the templates isn't tricky - look in tools/appliance in the source. If you want to run additional customisations, then you would add an extra script to be run inside the template being built - into tools/appliance/systemvmtemplate/template.json. On Thu, 12 Mar 2020 at 19:05, Greg Goodrich <ggoodr...@ippathways.com> wrote: > I was looking to manually update our 4.11.3 system vm templates to perform > the workaround described in > https://github.com/apache/cloudstack/issues/3654, however, I can’t seem > to get the system vm QCOW2 file to boot in virtual box. It tells me it > can’t find a boot device. Can anyone point me to some information on how to > do this, or maybe to another way to update a systemvm template? > > I’m using a Mac running VirtualBox (latest version), and attaching the > QCOW2 file as the drive, specifying 64 bit Debian linux as OS. > Thanks! > > -- > Greg Goodrich | IP Pathways > Senior Developer > 3600 109th Street | Urbandale, IA 50322 > p. 515.422.9346 | e. ggoodr...@ippathways.com<mailto:j...@ippathways.com> > >
