I have now tried to force ksm to work by having two VMs that use more RAM than available on the node.
VM1
http://prntscr.com/f2w1dj
VM2
http://prntscr.com/f2w1ir
node
http://prntscr.com/f2w1rc
As you can see KSM Sharing is still at 0kb and the ram usage of the node is very high.
I have now configured the "IP filter" for outgooing and the "Firewall in" for incomming traffic. Seems that this is the only option.
@guletz Thx for your input. Unfotunately this works only for unused IPs.
I have now installed the ksm deamon
apt-get install ksm-control-deamon
How to check now if KSM is running?
In WebGUI at the node it is still showing me the same
What I forgot to mention is, that I did found the config for "IP filter" but with enabling this, and configuring a IPSet "ipfilter-net0" to a specific IP form the subnet, does prevent outgooing connctions when the IP is changed on VM. The problem is, that incoming connections still work fine...
Hello @ all,
I am asking myself how to bind VMs to work with just one IP form a subnet.
I have a Hetzner server configured with a routed x.x.x.x/29 subnet.
My config looks the following:
# /etc/network/interfaces
### Hetzner Online GmbH - installimage
# Loopback device:
auto lo
iface lo inet...
Hello @ all,
I am asking myself why a restore form an NFS storage (1Gbit/s) is causing an IO delay of over 60% even if the disks used on the node are NVMe SSDs that should be minimum 10 times faster then the possible transfer rate over the 1Gbit/s network of the NFS Storage?
It also caused a...
@DerDanilo
If u have configured a vmbrX to use a subnet, this would mean that every VM with this bridge coud use any of the IPs in the subnet. This is kind of bad because a "VM client" could change the IP by himself to a different one in the same subnet, right?
Hello, thx for your answer. I yesterday found after a very long time trying, a solution. Maybe it helps somebody:
1) Change controller type to "VirtIO SCSI" in options of the VM
2) Mount the newest VirtIO driver ISO
3) Create a new (small) SCSI drive
4) Boot Windows VM, Install the VIOSCSI...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.