Install docs clarification needed?

Virtualmin
1

Downloading and Installing Virtualmin - Virtualmin

Start with a freshly installed, Grade A supported Operating System on your server or VPS.

…ok, so install the ISO and quit there!

except…

This script must be run on a freshly installed supported OS. It does not perform updates or upgrades (use your system package manager)…

…which can be interpreted as a suggestion to upgrade the OS before running the installer

i thought the docs used to say to install on a freshly installed and updated OS? maybe i’m wrong, but the installer seems to contradict the documentation - i just think this should be made definitively clear;

  • either install the OS and run the script
  • or install and update the OS and run the script
2

No. That’s just trying to stop people from running the install script some time later, after Virtualmin is already installed. We’ve had folks try to use the install script to upgrade a GPL to Pro system, or to install new versions of Virtualmin. It doesn’t do that.

You can update your OS before or after installation of Virtualmin, if you want. It doesn’t matter. We aren’t telling you to update before running the install script, we’re telling you that all Virtualmin updates after installation are performed using the OS package manager.

We’re just asking (begging) people to stop doing a bunch of preconfiguration before running the install script.

3

I’ll try to make that more clear, somehow.

4

You can update your OS before or after installation of Virtualmin

that would indeed make it clear

5

now, what about KVM?

seems to me that it’s preferred over a shared kernel??? if so, maybe that should also be added in the docs

1 Like
6

I have no idea what you’re talking about. Virtualmin has nothing to do with KVMs or kernels.

7

the ideal scenario would be to install w/v-min on a vanilla OS (Kernel-based Virtual Machine), correct? whereas another virtualization tech, such as OpenVZ, forces the same (and potentially old/modified) kernel across all users on the server which i would guess could cause issues

8

Virtualmin doesn’t know or care anything about kernels.

I personally don’t like OpenVZ, as it has been used by folks who oversell memory, which has surprising and catastrophic consequences for users. KVM is also a lot more popular and more actively maintained by the biggest Linux and cloud companies.

But, Virtualmin has nothing to do with kernel decisions.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.