Virtual Machines- is there a better way to jump start a VM?
from ABetterTomorrow@lemm.ee to selfhosted@lemmy.world on 28 Jun 19:18
https://lemm.ee/post/68096081

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away…… etc etc. I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined? FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

#selfhosted

threaded - newest

over_clox@lemmy.world on 28 Jun 19:22 next collapse

Save the machine state after you get it booted up and configured. Host+T

nfms@lemmy.ml on 28 Jun 19:23 next collapse

www.alpinelinux.org/about/ Check out Alpine. Might just be enough for what you want

ABetterTomorrow@lemm.ee on 28 Jun 19:25 collapse

I don’t think it’s a OS thing, I think it’s a hypervisor thing.

[deleted] on 28 Jun 19:24 next collapse
.
scrubbles@poptalk.scrubbles.tech on 28 Jun 19:45 next collapse

There’s many ways to do this. Saving the disk state is one, I believe that’s what the other person suggested - essentially stores the disk as an image which then you use for future vms as your jumping off point. This is also essentially how workstations are deployed at companies. (Essentially being the key word). Cloud providers have different names for this too, in AWS this is called their AMI.

Another option is Ansible, which essentially handles deploying a VM by running your scripts for you. I haven’t played too much with this, and I doubt it works with VirtualBox, but it’s something you may want to look into, it would definitely uplevel your skills.

Thirdly is dependent on what you actually use your VM for, you haven’t given your use cases but this is one of the reasons containerization became such a thing - because when running an app we mostly don’t care about the underlying system. It may be worth it to learn about docker.

ABetterTomorrow@lemm.ee on 29 Jun 12:22 collapse

I’m playing with a multicast data delivery software I’m building. Doing tests from a sever (VM) to 20+ clients and/or other server (VMs). All running through a Open5GS gNodeB (5G network core). Also testing out potential software to be a docker image. I’m slowly converting to containers but I might just need to make the leap.

scrubbles@poptalk.scrubbles.tech on 29 Jun 15:13 collapse

Sounds like it, I think docker is exactly what you’re looking for

ramielrowe@lemmy.world on 28 Jun 19:59 next collapse

I’d take a look at packer and ansible. Packer can be used to prepare a new base image for your VMs. And ansible can be used to automate the provisioning of a VM once it’s booted.

ABetterTomorrow@lemm.ee on 29 Jun 12:15 collapse

Mandible is on my list of things to learn and play with. I’ll check it out thank you.

AbidanYre@lemmy.world on 28 Jun 20:05 next collapse

Some combination of Ansible and cloud-init is probably what you’re looking for.

catloaf@lemm.ee on 28 Jun 22:24 collapse

This. Cloud-init, or autoinstall for Ubuntu, to get the install done, then use ansible for anything more.

NotProLemmy@lemmy.ml on 28 Jun 20:07 next collapse

Use virt-manager

BananaTrifleViolin@lemmy.world on 28 Jun 20:26 next collapse

Some good advice already in this thread.

Also worth considering QEMU as an alternative to VirtualBox. The Virt-manager tool is decent way of managing machines, and it’s relatively straight forward to create a base machine if you’re duplicating it. Virtualbox is perhaps initially more user friendly for absolute beginners, but once you have any familiarity with virtualization I’d suggest QEMU offers much more.

Also I find integration between the guest and the host linux system is generally more straight forward. Most linux systems already ship with samba and other relevant tools QEMU uses to interact between host and guest. There isn’t a need to faff around with the guest-additions stuff. Plus KVM virtual machines can run with near native performance.

ABetterTomorrow@lemm.ee on 29 Jun 12:17 collapse

Thank! I’ll check out QEMU. Sounds like something I need.

DeathByDenim@lemmy.world on 29 Jun 00:17 next collapse

There is also Vagrant which lets you specify VM specs, but also lets you install software in the VMs automatically. It also works for other VM software then just Virtualbox.

ABetterTomorrow@lemm.ee on 29 Jun 12:22 collapse

Thank you I’ll check it out.

MangoPenguin@lemmy.blahaj.zone on 29 Jun 01:33 next collapse

Simple method is just keep a ready to go VM and clone it.

ABetterTomorrow@lemm.ee on 29 Jun 12:22 collapse

Thank you!

MangoPenguin@lemmy.blahaj.zone on 29 Jun 15:29 collapse

NP! That’s how I do it on proxmox, I’ll start the VM every so often and update it. Only takes a few seconds to clone so it’s nice and quick to do.

ABetterTomorrow@lemm.ee on 29 Jun 17:36 collapse

Just read their doc and saw a video about. Very streamlined. I love it.

WhyJiffie@sh.itjust.works on 29 Jun 04:22 next collapse

snapshots, clones, or automated setup with ansible or such

Zwuzelmaus@feddit.org on 29 Jun 04:34 next collapse

Use qemu, or proxmox (it includes qemu).

Create one VM to your liking, then make it a template.

So when you need a new VM, you clone the template, and that’s it.

koala@programming.dev on 29 Jun 16:35 next collapse

Incus has a great selection of images that are ready to go, plus gives scripted access to VMs (and LXC containers) very easily; after incus launch to create a VM, incus exec can immediately run commands as root for provisioning.

lka1988@lemmy.dbzer0.com on 29 Jun 16:50 collapse

I make a unique user for each VM - root account is secured with SSH login disabled and a unique password, which is stored in my password manager.

Also, don’t use Virtualbox. It’s Oracle garbage. Use virt-manager instead.