Skip to main content

Upgrade CPU/RAM in KVM.

Upgrade CPU/RAM in KVM.

You can follow the following steps to increase memory size of your KVM virtual machine.
  1. Update the configuration using command sudo virsh edit
  2. reboot VM server.

Listing virtual servers.

 [ahmed@ahmed-server ~]$ sudo virsh  list
  Id    Name                           State
 ----------------------------------------------------
  8     VM-1                           running
  12    VM-2                           running
  13    VM-3                           running
  15    VM-4                           running

Getting Information about VM.

 [ahmed@ahmed-server ~]$ sudo virsh dominfo VM-1
 Id:             8
 Name:           VM-1
 UUID:           588ff640-25be-9b18-5eb3-f93c471848e6
 OS Type:        hvm
 State:          running
 CPU(s):         4
 CPU time:       503.3s
 Max memory:     8388608 KiB
 Used memory:    8388608 KiB
 Persistent:     yes
 Autostart:      disable
 Managed save:   no
 Security model: none
 Security DOI:   0

Edit Hardware for each VM.

 [ahmed@ahmed-server ~]$ sudo virsh edit VM-1
 Domain VM-1 XML configuration edited.

Checking VM information.

 [ahmed@ahmed-server ~]$ sudo virsh dominfo VM-1
 Id:             8
 Name:           VM-1
 UUID:           588ff640-25be-9b18-5eb3-f93c471848e6
 OS Type:        hvm
 State:          shut off
 CPU(s):         8
 Max memory:     33554432 KiB
 Used memory:    33554432 KiB
 Persistent:     yes
 Autostart:      disable
 Managed save:   no
 Security model: none
 Security DOI:   0
Once this is done restart the server.
And we are done.
 More Details : https://github.com/zubayr/big_config/blob/master/kvm/README.md

​
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more