![]() ![]() Multipass is nothing like oVirt or RHEV, which are products also based on top of KVM, but are GUI and menu driven, at least justifying their extra resources, by making datacenter deployments and management of their VM's easier. A lot of things didn't pass the commonsense litmus test for me. But they still say that Snap's Install is the only way possible(?) IDK. They say "that is the only way to install it." Actually, You can dl the code and compile it yourself, without the resource overhead, and speed concerns of involving Snap's in the process at all. KVM is then Snap installed with it as a dependency. Mulitipass, in the method they are pushing is Snap's installed, and inside containers. But are pushing what their Marketing is pushing, which I do not say is a lie, but is not exactly the truth. They thought they were great ideas, and made sense. It fell on deaf ears, and they did not understand any them. I got into a discussion with members of Canonical (elsewhere) trying to voice my concerns. It just turned out to be another animal, altogether. Many details on that, that I will not get into. ![]() You would think it would be a traditional VM Host installation of KVM, where you could use and be able to share it for other things. You would think that they would follow their past path of MAAS, and make it thin resources, easy to install, easy to use and menu driven. But I think the way they went about it (the implementation of) falls short. It is meant to be a deployment tool to be able to spin up VM's of 'LTS versions' of Ubuntu using KVM as the base VM Host. With the least amount of effort and resources. ![]() On the VM Host side, I am always looking for easier ways to do things. and Coincidentally, specifically on Canonical's marketing push, and their recommended implementation of "Multipass" recently. TheFu and I have talked about this (Multipass). I do a lot of 'testing', as well as my own development. And except the limitations of it's own installation method. That would be more as a convenience, and only if you don't mind giving up much resources and flexibility doing it. I can say, in my own experience, that I do not think that you need "Multipass". I have QEMU/KVM running fine on that also. It sits most of the time, except when I need to test certain things. Just because MAC hardware, even though it is Intel based, does still have some specific caveats. Which I have as a Multi-boot for versions of MAC OSX, Linux and Win. I also have an old MacBook here that I use to verify Development. Hopefully, some other people with different ideas and experience will chime in. Running a container as root is bad, and not just because is feels wrong, but there are real security issues in doing it. They have to run as root - I've done it for a test backup server, but ended up switching to using the native LXD to host storage access capabilities instead. Should mention that using NFS inside any container (nfs client or server) requires breaking the non-privileged container feature. They use much fewer resources than they did when running in VMs. I have tiny Alpine server, pihole, email gateway and wallabag servers running under lxd. Oh - and there is no GUI to control stuff - not even an integration with virt-manager. I gave up and created a ZFS block device on my LVM storage. The major issue I've had with lxd, besides being a snap package, is that it REALLY wants the backend storage to be ZFS. It works well for normal server needs (not firewalls or other non-standard network needs) and drastically reduces the overhead when compared to a VM. ![]() LXD is shipped as a snap package, like multipass, but I have it running on 2 or 3 systems here. If you are putting a Linux VM onto a Linux host, perhaps using a Linux container would make more sense? LXD is the container system from Canonical, but it feels more like a VM and works more like a VM from the maintenance standpoint. Too much simplification is a bad thing in my book. For my needs, the simplification was just a little too much and didn't allow the flexibility needed, but it might work great for others. Gnome Boxes provides a simple setup for VMs too. There are some snaps that do work on those systems, BTW, so it is something specific to the way mine are setup. It isn't the only snap that doesn't work. My attempts to even run it on 3 different systems have failed completely, since snap packages have problems still. virt-manager and virt-viewer allow controls for USB passthru that work easily with 18.04 and later installs. It provides enterprise stability and capability while still being very user friendly - much like virtualbox or VMware Workstation. I've been using the later for over a decade. There are many other options for using KVM/QEMU under Ubuntu - Gnome Boxes and virt-manager+libvirt come to mind. There are many "cons" to using multipass and a few "pros." What each person thinks for pro/con columns is a personal choice. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |