KVM

From Blue-IT.org Wiki

Revision as of 13:42, 29 October 2013 by Apos (talk | contribs) (Accessing services on KVM guests behind a NAT)

Using VirtualBox and KVM together

This is NOT possible!!!

Use VirtualBox

sudo service qemu-kvm stop
sudo service vboxdrv start

OR use KVM

sudo service vboxdrv stop
sudo service qemu-kvm start

Decide!

Migration from VirtualBox to KVM

This boils down to

  1. creating a clone of the vbox-machine (easiest way of getting rid of snapshots for a play vbox-disk)
  2. converting the images from vbox to qcow
  3. creating and configuring a new kvm-guest
  4. adding some NAT-fu (see next section)
# to do this - on the same machine - you have to STOP kvm and start vboxdr (see above)
# The conversion can take some time. Other virtual machines are not accessible in this time
VBoxManage clonehd -format RAW myOldVM.vdi /home/vm-exports/myNewVM.raw
0%...
cd /home/vm-exports/
qemu-img convert -f raw myNewVM.raw -O qcow2 myNewVM.qcow
# for a snapshot do (not tested)
cd /to/the/SnapShot/dir
VBoxManage clonehd -format RAW "SNAPSHOT_UUID" /home/vm-exports/myNewVM.raw

Accessing services on KVM guests behind a NAT

I am referring to this article:

which ist mentioned in the libvirt wiki:

I installed the qemu-python script of the first article under ubuntu 12.04 LTS, which worked like expected.

So I can access a port in the virtualmachine-guest with the IP/Port of the host (!). From within the host, it is possible to reach the guest via it's real ip. I am using the virtio-Interface (performance).