Nginx VM
-
@Dashrender said in Nginx VM:
@scottalanmiller said in Nginx VM:
@brandon220 said in Nginx VM:
I know you can create the xml and tar a copy but there has to be an "easier" way.
That's so easy, I'm not sure what an "easier way" would really look like.
That is NOT as easy as one step. Period...
Just because there are fewer steps doesn't make those steps easier. So how much easier is it?
-
Is any platform really just one step? There is a lot of detail needed to move a VM from one machine to another. A single step can't account for all of that. I don't think Hyper-V or ESXi offer that, either.
-
@black3dynamite said in Nginx VM:
@brandon220 said in Nginx VM:
Another question - Is there any reason NOT to use UEFI boot on all guests in KVM?
I wasn't able to create snapshots with UEFI VMs but that was from the GUI. I haven't using tried creating snapshots via command.
In KVM, you can't snapshot UEFI VM's.
-
@FATeknollogee said in Nginx VM:
@black3dynamite said in Nginx VM:
@brandon220 said in Nginx VM:
Another question - Is there any reason NOT to use UEFI boot on all guests in KVM?
I wasn't able to create snapshots with UEFI VMs but that was from the GUI. I haven't using tried creating snapshots via command.
In KVM, you can't snapshot UEFI VM's.
That's just poop.
-
@brandon220 said in Nginx VM:
@scottalanmiller I've just been using virt-manager and some ssh. I have Cockpit running on the host but haven't used it for management. It doesn't seem to reflect the guests that are running in the Cockpit gui. The cockpit-machines package is installed.
oVirt provides a mechanism for moving VMs between the hosts.
https://www.ovirt.org/documentation/vmm-guide/chap-Administrative_Tasks.html
Look under "Exporting and Importing Virtual Machines"
-
@FATeknollogee said in Nginx VM:
@black3dynamite said in Nginx VM:
@brandon220 said in Nginx VM:
Another question - Is there any reason NOT to use UEFI boot on all guests in KVM?
I wasn't able to create snapshots with UEFI VMs but that was from the GUI. I haven't using tried creating snapshots via command.
In KVM, you can't snapshot UEFI VM's.
Do you know why?
-
@black3dynamite said in Nginx VM:
@FATeknollogee said in Nginx VM:
@black3dynamite said in Nginx VM:
@brandon220 said in Nginx VM:
Another question - Is there any reason NOT to use UEFI boot on all guests in KVM?
I wasn't able to create snapshots with UEFI VMs but that was from the GUI. I haven't using tried creating snapshots via command.
In KVM, you can't snapshot UEFI VM's.
Do you know why?
On the IRC user group, I asked & was told it's a feature that has not been enabled.
-
@black3dynamite Found the thread, it was on the virt-tools-list not IRC.
https://www.redhat.com/archives/virt-tools-list/2017-September/msg00008.html -
@scottalanmiller said in Nginx VM:
Is any platform really just one step? There is a lot of detail needed to move a VM from one machine to another. A single step can't account for all of that. I don't think Hyper-V or ESXi offer that, either.
OK, that's true - but really - please type out all of the exact steps to do it in KVM.
I've done it a few times (my first time actually) over the last few days in Hyper-V. it's all point and click in the GUI - and I'm sure with the commandline it would be like 100 characters .
-
@Dashrender said in Nginx VM:
@Pete-S said in Nginx VM:
I think 20GB is outrageously large. 8GB or preferably 4GB.
Thin provision though - so what does it really matter?
Not much but it increases the risk of starving other VMs if one or several VMs goes crazy since storage is overcommitted on thin provisioning.
A VM with ngnix reverse proxy and ssh goes in under 1 GB (on debian) so with 4GB storage there are already several GBs worth of unused space. What more do you possibly need?
That's why I think going to 20GB is just too much without any benefit. We are not running a desktop or windows are we?
If you want to do something completely different with the VM that requires more space you can just make a new one.
-
@Dashrender said in Nginx VM:
OK, that's true - but really - please type out all of the exact steps to do it in KVM.
Part of the issue is that it is not a hypervisor task. So asking about a hypervisor doesn't really make sense. It's in the hypervisor management set. And I provided two simple ways to do it already, all typed out, in links.
-
@Dashrender said in Nginx VM:
I've done it a few times (my first time actually) over the last few days in Hyper-V. it's all point and click in the GUI - and I'm sure with the commandline it would be like 100 characters .
Point and click in KVM too.
-
@Pete-S said in Nginx VM:
@Dashrender said in Nginx VM:
@Pete-S said in Nginx VM:
I think 20GB is outrageously large. 8GB or preferably 4GB.
Thin provision though - so what does it really matter?
Not much but it increases the risk of starving other VMs if one or several VMs goes crazy since storage is overcommitted on thin provisioning.
A VM with ngnix reverse proxy and ssh goes in under 1 GB (on debian) so with 4GB storage there are already several GBs worth of unused space. What more do you possibly need?
That's why I think going to 20GB is just too much without any benefit. We are not running a desktop or windows are we?
If you want to do something completely different with the VM that requires more space you can just make a new one.
So with a 4GB vDisk and no swap?
-
@black3dynamite said in Nginx VM:
@Pete-S said in Nginx VM:
@Dashrender said in Nginx VM:
@Pete-S said in Nginx VM:
I think 20GB is outrageously large. 8GB or preferably 4GB.
Thin provision though - so what does it really matter?
Not much but it increases the risk of starving other VMs if one or several VMs goes crazy since storage is overcommitted on thin provisioning.
A VM with ngnix reverse proxy and ssh goes in under 1 GB (on debian) so with 4GB storage there are already several GBs worth of unused space. What more do you possibly need?
That's why I think going to 20GB is just too much without any benefit. We are not running a desktop or windows are we?
If you want to do something completely different with the VM that requires more space you can just make a new one.
So with a 4GB vDisk and no swap?
No swap? Sure, if you want and have enough RAM allocated for your application. Would also depend if you use memory ballooning or not on the hypervisor.
I'd just start with 1vCPU and 1GB RAM then I get 1GB swap by the installer by default. With the system using less than 1GB storage for the OS then there are a little more than 2GB unused on 4GB storage. Reverse proxies don't use storage so the 2GB will remain unused forever.
You can always trim down RAM and storage but it's got to be worth the effort as well so no point in going crazy. 512 MB RAM would probably work fine too. You can set up if and how many buffers you want to use in nginx.
-
@Pete-S said in Nginx VM:
No swap? Sure, if you want and have enough RAM allocated for your application. Would also depend if you use memory ballooning or not on the hypervisor.
Yeah, but basically that would be trading low cost, low risk disk space for high cost, high risk RAM space. It's specifically to avoid those big dangers that we lean towards larger disks in the first place.
Even if we have a 512MB RAM VM, we might add 2GB of swap that, in theory, is never touched. But if something goes wrong, we get time to react. And with thin provisioning, we don't use the disk space unless necessary.
-
@black3dynamite said in Nginx VM:
@Pete-S said in Nginx VM:
@Dashrender said in Nginx VM:
@Pete-S said in Nginx VM:
I think 20GB is outrageously large. 8GB or preferably 4GB.
Thin provision though - so what does it really matter?
Not much but it increases the risk of starving other VMs if one or several VMs goes crazy since storage is overcommitted on thin provisioning.
A VM with ngnix reverse proxy and ssh goes in under 1 GB (on debian) so with 4GB storage there are already several GBs worth of unused space. What more do you possibly need?
That's why I think going to 20GB is just too much without any benefit. We are not running a desktop or windows are we?
If you want to do something completely different with the VM that requires more space you can just make a new one.
So with a 4GB vDisk and no swap?
I would keep swap space. Swap's main purpose today is to protect against a crash. If something starts using memory that you don't expect, it will slow down before it dies and give you way more time to catch it and fix it.
-
@Reid-Cooper I think this is good sensible advice. No reason not to have a little swap at least.
-
I'd normally keep swap space too but I know for sure you can run without it successfully because we used to do that with embedded linux for years - with devices that had years of uptime.
With memory ballooning you can overcommit RAM and the hypervisor can swap guest RAM to disk if it comes to that. I don't know which hypervisors supports it though. As always it depends on how much you want to cram out of your gear.
