cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Goodrich <>
Subject Re: Altering systemvm templates - VirtualBox?
Date Sun, 15 Mar 2020 17:58:00 GMT
Thanks for the feedback, Rohit and Richard. I actually used a third approach, which was to
import the template into cloudstack as a regular template. I then spun up an instance, and
after manually configuring the network, went ahead and made the changes. I then did an undo
on my manual networking, and downloaded the instance. It seems to be working for us in our
staging environment. I will be looking to this feedback to make some more permanent changes
to our approach for the future, as I want a repeatable automated process around this for when
it is necessary. Thanks again!

Greg Goodrich | IP Pathways
Senior Developer
3600 109th Street | Urbandale, IA 50322
p. 515.422.9346 | e.<>

On Mar 14, 2020, at 8:37 AM, Richard Lawley <<>>

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

On Thu, 12 Mar 2020 at 19:05, Greg Goodrich <<>>

I was looking to manually update our 4.11.3 system vm templates to perform
the workaround described in, 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.

Greg Goodrich | IP Pathways
Senior Developer
3600 109th Street | Urbandale, IA 50322
p. 515.422.9346 | e.<><>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message