Difference between revisions of "Installation (KVM)"
Jump to navigation
Jump to search
(WIP) |
(Added Allow VNC Console Access) |
||
| Line 11: | Line 11: | ||
== Networking == | == Networking == | ||
== Configuration == | |||
=== Allow VNC Console Access === | |||
By default virtual machine consoles are bound to 127.0.0.1 on the host KVM server. So you can't connect from a remote machine using VNC to see the VM's console (unless you tunnel through SSH). Bind to 0.0.0.0 to make remote console access. Note that the VM configuration also needs to be changed to listen on 0.0.0.0. | |||
# Edit <code>/etc/libvirt/qemu.conf </code> and uncomment the following line | |||
#* <code> vnc_listen = "0.0.0.0" </code> | |||
# Restart libvirtd | |||
#* <code>service libvirtd restart</code> | |||
[[Category:KVM]] | [[Category:KVM]] | ||
[[Category:Ubuntu]] | [[Category:Ubuntu]] | ||
Revision as of 22:21, 17 February 2018
Prerequisites
This guide assumes you have a working Ubuntu Server with one physical NIC that will used for networking to the host server, and also for a bridged network for guest virtual machines.
Ensure your server has CPU's that support hardware virtualisation, you should get one output of flags per CPU (which will include either svm or vmx)
egrep '(vmx|svm)' /proc/cpuinfo
Installation
Install using the following command
apt-get install qemu-kvm libvirt-bin virtinst bridge-utils cpu-checker
Networking
Configuration
Allow VNC Console Access
By default virtual machine consoles are bound to 127.0.0.1 on the host KVM server. So you can't connect from a remote machine using VNC to see the VM's console (unless you tunnel through SSH). Bind to 0.0.0.0 to make remote console access. Note that the VM configuration also needs to be changed to listen on 0.0.0.0.
- Edit
/etc/libvirt/qemu.confand uncomment the following linevnc_listen = "0.0.0.0"
- Restart libvirtd
service libvirtd restart