Summer. Tired of sitting at the computer, I decided to relax and walk-Skate more. Spam from monitorilok for Android-phone falls regularly. Hard Klava beloved Zevsika from tomorrow will always be with me. (ugh-ugh-ugh). The sin in this situation do not use ssh client on your phone with a keyboard and 3 g for VDSkami control. And yet it would be a great sin to tell everyone in short, how to do it.
Of course, you have customized the KVM Manual/16 on this site. And of course, you have the libvirt daemon. His Console front end is just same virsh.
So. Virsh we have. If not, look at the article/16.
To check, simply enter in the console virsh
You now have a new shell:
Immediately I say that subsequent commands can be entered in the console the console either conventional virsh with virsh.
# command virsh vds
Debian: ~ # virsh command vds
are equivalent. But I recommend using shell virsh because there is autocompletion of commands virsh’a.
Later in the article, I’m not going to use the console commands. Be aware that each of the following commands to write to the console or shell virsh virsh.
So let’s agree that vdsX VDSki is the name that you want to perform an action.
Begin. Poupravlâem “power“ virtual machines:
destroy vdsX — «vydergivaem virtualki» power cable
reboot vdsX–will give the reboot command VDSki, as if it was written out of the console.
vdsX — shutdown correctly turn off VPS. If off is do destroy.
Start–Run vdsX VDS
Save the file-name vdsX–virtualki will save the State file, disable it and frees up RAM. In fact, similar to the hibernate command. Only you can save RAM = many States) for the tests. Note that the file name must be unique, always (or it will overwrite, even dump the other virtualki)
Restore file-name-returns the virtualku of sleep. The virtualku does not need this information is taken from the file. A pity, really. You could create the same virtualok heap and then they alternately load from file and make fun.
vdsX is another suspend hibernate, but memory reserved virtualkoj is not freed. More reliable than save/restore.
resume vdsX vds-returns of the State that we were pushed by suspend
You will look at some information about VDSah:
NodeInfo — will give us information about your server. Useless, but maloli)
list — displays a list of all virtualok and their status is running, halted, suspended, etc. useful for inclusion in reports, by the way.
dominfo vdsX — displays information about the virtualke. There are useful, for example, you can see how much CPU time skušala means (Yes Yes, will it build clouds in the near future =)))
domblkstat vdsX device must display statistics for block device virtualki. Not yet figured out how it works. I will be glad to help. More precisely do not know what to write instead of device.
domifstat vdsX vnetY — allows you to view the information on the network interface virtualki. vnetY should use virtualkoj vdsX to team has given a correct conclusion. The team is valuable because it allows to check whether dropaûtsâ is not virtualki network packets.
ttyconsole vdsX — tells us what/dev/pts is vdsom. It is useful, if you are know what you can do use the pts with.
vncdisplay vdsX–tells us the IP and port the virtual IP KVM … a VNC server for VDSki. The virt-manager, you can add new ones.
Let’s change some limits: virtualok
vdsX summ setmem — changes the limit on memory virtualki. Summ is indicated in kilobytes. Works without a reboot. The memory limit immediately is marked as being in use by the host.
setmaxmem vdsX summ–change the upper limit of memory for virtualki. Summ in kilobytes. The memory limit means will, only if there is free memory on the host. On the limit of memory is marked as used by the host, only if it really is virtualkoj. (setmaxmem did not advise to use for KVM, only in the clouds if)
setvcpus vdsX count — sets the count of virtual cores for VDS. You can only use the virtualki off. Total count for all the VDS does not make the more amount of cores on the host, but better to leave one in store, if not to use the server with all virtualkami.
And for a snack:
vdsX–console should connect us to tty1 virtualki. does not work (often
Autostart–vdsX disable — disables Autostart virtualki when you start the host. If you use the zaûzajte option is for manuals of all VDS is still without br1/br2 (which I recommend not to create when you start the server, and create scripts later) is not loaded.
Autostart vdsX-includes Autostart virtualki.
The rest of the team is worth seeing in man virsh, but hardly you need. There‘s still manage virtual devices VDSov, but this is best done via the virt-manager. Well, some of the commands in my case replaced with virt-install scripts.
P.s.–come back to relax. Today was oŝuŝa