is it possible to ram the ram of a vm in the "create VM" gui in GB increments instead of entering the exact MB required?
eg, 8GB instead of 8192MB
eg, 8GB instead of 8192MB
Last edited:
set vm ram in GB instead of MB in gui
- Thread starter nd6376
- Start date
There are a lot of use cases for <1GB of RAM in VMs. Would you expect 1GB of RAM to be the minimum you can assign?
No, but I would expect that instead of the fixed MB, I can insert either 512M or 4G or 1T.
Just like with PHP and many other software.
That is not really an argument. PHP is just a programming language that parses the input. This can be done in any programming language you want.
Just add a select with "MiB", "GiB" after the input.
But honestly I dont know any guest OS that runs fine on sub 1 GB RAM - but that may be my shortcoming.
I have some VMs with 512 MiB...768 MiB:
Code:
$ lsb_release -a; free
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 13 (trixie)
Release: 13
Codename: trixie
gesamt benutzt frei gemns. Puffer/Cache verfügbar
Speicher: 475560 280936 19584 296 187844 194624
Swap: 808956 17256 791700This is just a specific jumphost, no "real" services. And it still works with 384 MiB too...
Should have been more precise.
I think it should be done like php.ini settings (and many other software) uses these settings.
344M
5G
1T
Right know, I have to calculate "hmm... 1GB is 1024MB. So that means * 2 * 2 = 4096 gives me a 4GB machine.
Instead of just inserting "4G".
Just like I would not use docker deploy.resources.limits set to
I think it should be done like php.ini settings (and many other software) uses these settings.
344M
5G
1T
Right know, I have to calculate "hmm... 1GB is 1024MB. So that means * 2 * 2 = 4096 gives me a 4GB machine.
Instead of just inserting "4G".
Just like I would not use docker deploy.resources.limits set to
4096M but 4G instead.
Last edited:
After a few decades you know them by heart or are just a nerd how can simple calculate them in the head.
Windows? No .... but I have hundreds of Linux VMs running with such a low memory amount. If you're e.g. just running VPNs or do some kind of network routing, it's totally fine. I had to increase it over the years from 128M to kno 384 MB with Debian Trixie, yet you cannot install it with such low memory footprint, but it'll run without swap flawlessly.
I have many CTs, Some running with less than 128MB RAM. Host has only 32GB RAM total. So quite like to specify guest memory in MB!
Cool! That's (of course) the positive aspect of containers.
Unfortunately I do not like them - my virtual assets are VMs. (Actually ~97 percent of them.)
Of course, and I would even say obviously (but seems not so), it is not about replacing the MiB option with GiB, but having a GiB option additionally...