{"id":37530,"date":"2019-10-31T22:18:10","date_gmt":"2019-10-31T19:18:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ip-kvm-cherez-qemu\/"},"modified":"2019-10-31T22:18:10","modified_gmt":"2019-10-31T19:18:10","slug":"ip-kvm-cherez-qemu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ip-kvm-cherez-qemu","title":{"rendered":"IP-KVM prin QEMU","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"IP-KVM prin QEMU\" src=\"\/wp-content\/uploads\/2019\/08\/f9620a262b690b4494984658d33805f9.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDiagnosticarea problemelor la pornirea sistemului de operare pe servere f\u0103r\u0103 KVM este o sarcin\u0103 dificil\u0103. Cre\u0103m pentru noi KVM-over-IP prin intermediul unei imagini de recuperare \u0219i a unei ma\u0219ini virtuale.<\/p>\n<p>\u00cen cazul \u00een care apar probleme cu sistemul de operare <noindex><a rel=\"nofollow\" href=\"http:\/\/slc.tl\/q58Za\">de pe serverul remote<\/a><\/noindex>, administratorul \u00eencarc\u0103 imaginea de recuperare \u0219i efectueaz\u0103 lucr\u0103rile necesare. Aceast\u0103 metod\u0103 func\u021bioneaz\u0103 excelent atunci c\u00e2nd cauza e\u0219ecului este cunoscut\u0103, iar imaginea de recuperare \u0219i sistemul de operare instalat pe server fac parte din aceea\u0219i familie. Dac\u0103 cauza e\u0219ecului nu este \u00eenc\u0103 cunoscut\u0103, este necesar s\u0103 se observe procesul de \u00eenc\u0103rcare a sistemului de operare.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>KVM remote<\/h2>\n<p>\nAccesul la consola serverului poate fi realizat cu ajutorul unor instrumente \u00eencorporate, cum ar fi IPMI sau Intel\u00ae vPro\u2122, sau prin intermediul unor dispozitive externe denumite IP-KVM. Exist\u0103 situa\u021bii \u00een care toate aceste tehnologii sunt indisponibile. Totu\u0219i, aceasta nu este o problem\u0103. Dac\u0103 serverul poate fi repornit de la distan\u021b\u0103 \u00een imaginea de recuperare bazat\u0103 pe un sistem de operare din familia Linux, atunci KVM-over-IP poate fi organizat rapid.<\/p>\n<p>Imaginea de recuperare reprezint\u0103 un sistem de operare complet, care este stocat \u00een memoria RAM. Astfel, putem rula orice software, inclusiv ma\u0219ini virtuelle (MV). Cu alte cuvinte, este posibil s\u0103 pornim o MV \u00een cadrul c\u0103reia va func\u021biona sistemul de operare al serverului. Accesul la consola MV-ului poate fi organizat, de exemplu, prin VNC.<\/p>\n<p>Pentru a porni sistemul de operare al serverului \u00een cadrul MV-ului, este necesar s\u0103 se specifice discurile serverului ca discuri MV. \u00cen sistemele de operare din familia Linux, discurile fizice sunt reprezentate ca dispozitive bloc de tipul <b>\/dev\/sdX<\/b>, cu care se poate lucra ca \u0219i cum ar fi fi\u0219iere obi\u0219nuite.<\/p>\n<p>Anumite hyperviseuri, cum ar fi QEMU \u0219i VirtualBox, permit stocarea datelor MV-ului \u00een format \u201eraw\u201d, adic\u0103 doar datele de stocare f\u0103r\u0103 metadatele hyperviseurului. Astfel, MV-ul poate fi pornit folosind discurile fizice ale serverului.<\/p>\n<p>Aceast\u0103 metod\u0103 necesit\u0103 resurse pentru a porni imaginea de recuperare \u0219i MV-ul \u00een interiorul acesteia. Cu toate acestea, av\u00e2nd la dispozi\u021bie patru sau mai mul\u021bi gigaocte\u021bi de memorie RAM, aceasta nu va fi o problem\u0103.<\/p>\n<h2>Preg\u0103tirea mediului<\/h2>\n<p>\nCa ma\u0219in\u0103 virtual\u0103, poate fi utilizat\u0103 o aplica\u021bie u\u0219oar\u0103 \u0219i simpl\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/www.qemu.org\/\">QEMU<\/a><\/noindex>, care, de obicei, nu face parte din imaginea de recuperare, a\u0219a c\u0103 trebuie instalat\u0103 separat. Imaginea de recuperare pe care o oferim clien\u021bilor se bazeaz\u0103 pe <noindex><a rel=\"nofollow\" href=\"https:\/\/www.archlinux.org\/\">Arch Linux<\/a><\/noindex>, \u00een care se utilizeaz\u0103 managerul de pachete <b>pacman<\/b>.<\/p>\n<p>\u00cen primul r\u00e2nd, este necesar s\u0103 ne asigur\u0103m c\u0103 imaginea de recuperare folose\u0219te cele mai recente versiuni ale software-ului. Verificarea \u0219i actualizarea tuturor componentelor sistemului de operare se pot efectua cu urm\u0103toarea comand\u0103:<\/p>\n<p><code>pacman -Suy<\/code><\/p>\n<p>Dup\u0103 actualizare, este necesar s\u0103 instal\u0103m QEMU. Comanda pentru instalarea prin pacman va ar\u0103ta astfel:<\/p>\n<p><code>pacman -S qemu<\/code><\/p>\n<p>S\u0103 verific\u0103m dac\u0103 QEMU s-a instalat corect:<\/p>\n<p><code>root@sel-rescue ~ # qemu-system-x86_64 --version<br \/>\nVersiunea emulatorului QEMU 4.0.0<br \/>\nDrepturi de autor (c) 2003-2019 Fabrice Bellard \u0219i dezvoltatorii proiectului QEMU<\/code><\/p>\n<p>Dac\u0103 totul este \u00een regul\u0103, imaginea de recuperare este gata de utilizare.<\/p>\n<h2>Pornirea ma\u0219inii virtuale<\/h2>\n<p>\n\u00cen primul r\u00e2nd, trebuie s\u0103 stabilim c\u00e2te resurse s\u0103 aloc\u0103m VM-ului \u0219i s\u0103 determin\u0103m c\u0103ile c\u0103tre discurile fizice. \u00cen cazul nostru, vom aloca dou\u0103 nuclee \u0219i dou\u0103 gigaocte\u021bi de memorie RAM ma\u0219inii virtuale, iar discurile se afl\u0103 pe calea <b>\/dev\/sda<\/b> \u0219i <b>\/dev\/sdb<\/b>. S\u0103 pornim VM-ul:<\/p>\n<p><code>qemu-system-x86_64 <br \/>\n -m 2048M <br \/>\n -net nic -net user <br \/>\n -enable-kvm <br \/>\n -cpu host,nx <br \/>\n -M pc <br \/>\n -smp 2 <br \/>\n -vga std <br \/>\n -drive file=\/dev\/sda,format=raw,index=0,media=disk <br \/>\n -drive file=\/dev\/sdb,format=raw,index=1,media=disk <br \/>\n -vnc :0,password <br \/>\n -monitor stdio<\/code><\/p>\n<p>Un pic mai multe detalii despre ce \u00eenseamn\u0103 fiecare dintre parametrii:<\/p>\n<ul>\n<li><b>-m 2048M<\/b> \u2014 aloc\u0103m 2 GB de memorie RAM pentru VM;<\/li>\n<li><b>-net nic -net user<\/b> \u2014 ad\u0103ug\u0103m o conexiune simpl\u0103 la re\u021bea prin hypervisor folosind NAT (Network Address Translation);<\/li>\n<li><b>-enable-kvm<\/b> \u2014 activ\u0103m virtualizarea complet\u0103 KVM (Kernel Virtual Machine);<\/li>\n<li><b>-cpu host<\/b> \u2014 spunem procesorului virtual s\u0103 ob\u021bin\u0103 \u00eentreaga func\u021bionalitate a procesorului serverului;<\/li>\n<li><b>-M pc<\/b> \u2014 tipul de echipament este PC;<\/li>\n<li><b>-smp 2<\/b> \u2014 procesorul virtual ar trebui s\u0103 fie dual-core;<\/li>\n<li><b>-vga std<\/b> \u2014 alegem o plac\u0103 grafic\u0103 standard care nu suport\u0103 rezolu\u021bii mari;<\/li>\n<li><b>-drive file=\/dev\/sda,format=raw,index=0,media=disk<\/b>\n<ul>\n<li><b>file=\\\/dev\\\/sdX<\/b> \u2014 calea c\u0103tre dispozitivul bloc care reprezint\u0103 discul serverului;<\/li>\n<li><b>format=raw<\/b> \u2014 marc\u0103m c\u0103 \u00een fisierul specificat toate datele sunt \u00een format \u201ebrut\u201d, adic\u0103 a\u0219a cum sunt pe disc;<\/li>\n<li><b>index=0<\/b> \u2014 num\u0103rul discului, care trebuie s\u0103 creasc\u0103 cu unul pentru fiecare disc urm\u0103tor;<\/li>\n<li><b>media=disk<\/b> \u2014 ma\u0219ina virtual\u0103 trebuie s\u0103 recunoasc\u0103 aceast\u0103 stocare ca fiind un disc;<\/li>\n<\/ul>\n<\/li>\n<li><b>-vnc :0, password<\/b> \u2014 pornim serverul VNC \u00een mod implicit pe 0.0.0.0:5900, folosind parola pentru autentificare;<\/li>\n<li><b>-monitor stdio<\/b> \u2014 comunicarea administratorului cu QEMU va avea loc prin fluxuri standard de intrare-ie\u0219ire.<\/li>\n<\/ul>\n<p>\nDac\u0103 totul este \u00een regul\u0103, va porni monitorul QEMU: <\/p>\n<p><code>Monitor QEMU 4.0.0 - tasta\u021bi 'help' pentru mai multe informa\u021bii<br \/>\n(qemu)<\/code><\/p>\n<p>Am specificat c\u0103 autentificarea se face prin parol\u0103, dar nu am indicat parola propriu-zis\u0103. Acest lucru se poate realiza trimi\u021b\u00e2nd comanda change vnc password \u00een monitorul QEMU. Un aspect important: parola nu poate fi mai lung\u0103 de opt caractere.<\/p>\n<p><code>(qemu) schimb\u0103 parola vnc<br \/>\nParol\u0103: ******<\/code><\/p>\n<p>Dup\u0103 aceasta, ne putem conecta cu orice client VNC, cum ar fi Remmina, la adresa IP a serverului nostru cu parola pe care am specificat-o.<\/p>\n<p><img decoding=\"async\" alt=\"IP-KVM prin QEMU\" src=\"\/wp-content\/uploads\/2019\/08\/f735a37d49038b472d6e5c22df4e7570.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<img decoding=\"async\" alt=\"IP-KVM prin QEMU\" src=\"\/wp-content\/uploads\/2019\/08\/02a12b62938a7883363807eaa379279f.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAcum nu doar c\u0103 vedem posibilele erori \u00een timpul \u00eenc\u0103rc\u0103rii, dar putem \u0219i s\u0103 le abord\u0103m.<\/p>\n<p>La finalizarea lucr\u0103rilor, este necesar s\u0103 opri\u021bi ma\u0219ina virtual\u0103. Acest lucru poate fi realizat fie din interiorul sistemului de operare, trimi\u021b\u00e2nd un semnal de oprire, fie prin a da comanda <b>system_powerdown<\/b> \u00een monitorul QEMU. Aceasta va fi echivalentul unei ap\u0103s\u0103ri unice a butonului de oprire: sistemul de operare din interiorul ma\u0219inii virtuale se va \u00eenchide gra\u021bios.<\/p>\n<h2>Instalarea sistemului de operare<\/h2>\n<p>\nMa\u0219ina virtual\u0103 are acces complet la discurile serverului \u0219i, prin urmare, poate fi utilizat\u0103 pentru a instala manual sistemul de operare. Singura limitare const\u0103 \u00een cantitatea de memorie RAM: nu \u00eentotdeauna imaginea ISO poate fi plasat\u0103 \u00een memoria RAM. Vom aloca patru gigaocte\u021bi \u00een memoria RAM pentru a stoca imaginea \u00een <b>\/mnt<\/b>:<\/p>\n<p><code>mount -t tmpfs -o size=4G tmpfs \/mnt<\/code><\/p>\n<p>De asemenea, vom desc\u0103rca imaginea de instalare a sistemului de operare FreeBSD 12.0:<\/p>\n<p><code>wget -P \/mnt ftp:\/\/ftp.freebsd.org\/pub\/FreeBSD\/releases\/amd64\/amd64\/ISO-IMAGES\/12.0\/FreeBSD-12.0-RELEASE-amd64-bootonly.iso<\/code><\/p>\n<p>Acum putem porni VM-ul:<\/p>\n<p><code>qemu-system-x86_64 <br \/>\n -m 2048M <br \/>\n -net nic -net user <br \/>\n -enable-kvm <br \/>\n -cpu host,nx <br \/>\n -M pc <br \/>\n -smp 2 <br \/>\n -vga std <br \/>\n -drive file=\/dev\/sda,format=raw,index=0,media=disk <br \/>\n -drive file=\/dev\/sdb,format=raw,index=1,media=disk <br \/>\n -vnc :0,password <br \/>\n -monitor stdio <br \/>\n -cdrom \/mnt\/FreeBSD-12.0-RELEASE-amd64-bootonly.iso <br \/>\n -boot d<br \/>\n<\/code><\/p>\n<p>Steagul <b>-boot d<\/b> seteaz\u0103 \u00eenc\u0103rcarea de pe unitatea CD. Ne conect\u0103m cu clientul VNC \u0219i vedem \u00eenc\u0103rc\u0103torul FreeBSD.<\/p>\n<p><img decoding=\"async\" alt=\"IP-KVM prin QEMU\" src=\"\/wp-content\/uploads\/2019\/08\/722f904ba4212bcce8746ca473489d50.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDeoarece pentru accesul la internet s-a folosit ob\u021binerea adresei prin DHCP, este posibil ca, dup\u0103 configurare, s\u0103 fie necesar s\u0103 ne boot\u0103m \u00een sistemul proasp\u0103t instalat \u0219i s\u0103 corect\u0103m set\u0103rile re\u021belei. \u00cen unele cazuri, poate fi necesar\u0103 instalarea driverelor pentru adaptorul de re\u021bea, deoarece placa de re\u021bea instalat\u0103 pe server \u0219i emulat\u0103 \u00een VM difer\u0103.<\/p>\n<h2>Concluzie<\/h2>\n<p>\nAceast\u0103 metod\u0103 de organizare a accesului de la distan\u021b\u0103 la consola serverului consum\u0103 o parte din resursele serverului, totu\u0219i, nu impune cerin\u021be speciale \u00een ceea ce prive\u0219te componentele hardware ale serverului \u0219i, prin urmare, poate fi realizat\u0103 \u00een aproape orice condi\u021bii. Utilizarea unei astfel de solu\u021bii permite semnificativ \u00eembun\u0103t\u0103\u021birea diagnostic\u0103rii defec\u021biunilor software \u0219i restaurarea func\u021bionalit\u0103\u021bii serverului de la distan\u021b\u0103.<br \/>\n<br \/>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/selectel\/blog\/464565\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0423\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u043e\u0441\u0442\u0435\u0439 \u043f\u0440\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445 \u0431\u0435\u0437 KVM \u2014 \u043d\u0435\u043f\u0440\u043e\u0441\u0442\u043e\u0435 \u0437\u0430\u043d\u044f\u0442\u0438\u0435. \u0421\u043e\u0437\u0434\u0430\u0435\u043c \u0441\u0435\u0431\u0435 KVM-over-IP \u0447\u0435\u0440\u0435\u0437 \u043e\u0431\u0440\u0430\u0437 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u043c\u0430\u0448\u0438\u043d\u0443. \u0412 \u0441\u043b\u0443\u0447\u0430\u0435 \u0432\u043e\u0437\u043d\u0438\u043a\u043d\u043e\u0432\u0435\u043d\u0438\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0441 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u043d\u0430 \u0443\u0434\u0430\u043b\u0435\u043d\u043d\u043e\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u0435, \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440 \u0437\u0430\u0433\u0440\u0443\u0436\u0430\u0435\u0442 \u043e\u0431\u0440\u0430\u0437 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u043f\u0440\u043e\u0432\u043e\u0434\u0438\u0442 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u044b\u0435 \u0440\u0430\u0431\u043e\u0442\u044b. \u0422\u0430\u043a\u043e\u0439 \u0441\u043f\u043e\u0441\u043e\u0431 \u043e\u0442\u043b\u0438\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442, \u043a\u043e\u0433\u0434\u0430 \u043f\u0440\u0438\u0447\u0438\u043d\u0430 \u0441\u0431\u043e\u044f \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u0430, \u0430 \u043e\u0431\u0440\u0430\u0437 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0438 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u0430\u044f \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0435 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28165,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37530","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0423\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u043e\u0441\u0442\u0435\u0439 \u043f\u0440\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ip-kvm-cherez-qemu\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47IP-KVM \u0447\u0435\u0440\u0435\u0437 QEMU | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0423\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u043e\u0441\u0442\u0435\u0439 \u043f\u0440\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ip-kvm-cherez-qemu\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:18:10+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:18:10+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47IP-KVM prin QEMU | ProHoster","description":"Diagnosticarea problemelor la \u00eenc\u0103rcarea sistemului de operare pe servere.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ip-kvm-cherez-qemu","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47IP-KVM \u0447\u0435\u0440\u0435\u0437 QEMU | ProHoster","og:description":"\u0423\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u0438\u0435 \u043d\u0435\u0438\u0441\u043f\u0440\u0430\u0432\u043d\u043e\u0441\u0442\u0435\u0439 \u043f\u0440\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0435 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u043e\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0430\u0445.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/ip-kvm-cherez-qemu","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:18:10+00:00","article:modified_time":"2019-10-31T19:18:10+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37530","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-23 18:15:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:25:26","updated":"2026-01-23 18:15:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37530","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=37530"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/37530\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/28165"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=37530"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=37530"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=37530"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}