stevepedwards.com/DebianAdmin linux mint IT admin tips info

QEMU/KVM on Mint

Following the commands at:

http://runlevel-6.github.io/blog/2015/01/13/linux-mint-with-hypervisor/

I found there are some extra steps that may need to be taken to get a VM running on Mint, due mainly to permissions issues.

I assume you have an Intel or AMD CPU that offers virtualisation for this Post.

You can find out if your chip does by using:

DellMint stevee # cat /proc/cpuinfo | grep svm

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy vmmcall

for AMD, or:

cat /proc/cpu | grep vms

for Intel chips.

Now follow the links commands:

apt-get update

apt-get upgrade

apt-get install openssh-server
apt-get install qemu-system
apt-get install qemu-utils
apt-get install libvirt-bin
apt-get install virt-manager
apt-get install python-spice-client-gtk
apt-get install virt-viewer

Now you should see the VM Manager in the Desktop Menu:

Open the VMM and create a LOCAL connection for your user:

If you can't connect for a reason that shows a dialogue box stating things to check; like you are in the libvirtd group etc, but you are in it, and all else is valid,

libvirtfail.png

then it may be a perms issue here too, so stop the libvirtd service, and chown the PID file from root group to libvirtd group and restart:

ls -al /var/run/libvirtd.pid

-rw-r--r-- 1 root root 4 Oct 31 21:58 /var/run/libvirtd.pid

sudo service libvirt-bin stop

sudo chown root:libvirtd  /var/run/libvirtd.pid

sudo service libvirt-bin start

Re-open the VMM. It should now be connected.

VMM.png

Use autoconnect so when VMM starts you see each already installed VM.

I already have one created for Win7 so ignore that, create a new VM for the new connection using the PC button or connection rclick:

I'll be using an ISO image stored locally on the machine – file ownership permissions will matter as you are using the VMM in your user name – beware ISO files belonging to others.

For some weird reason, user stevee or root could not change the permissions of this file!

DellMint stevee # chown
stevee.libvirt /media/stevee/Quadra/SBS2k3/Win2003.iso

DellMint stevee # ls -als /media/stevee/Quadra/SBS2k3/Win2003.iso

2586784 -rw------- 2 stevee stevee 2648866816 Nov 28 2014 /media/stevee/Quadra/SBS2k3/Win2003.iso

I had to copy the ISO to my home Downloads folder before VMM access...?

As you see, you also need to be in the libvirtd group to use the VMM.

Starting over to browse to the new folder, I untick the "Allocate entire disk" and continue:

Once the file was moved to user's Downloads, VMM can access it and the install begins:



It takes 9 seconds to "format" the virtual 8GB drive space, and obviously it's a lot quicker to install than in reality.

And after a reboot:

Note you have to use the menu option at first Win login to send Crl-Alt-Del, else Mint options to shut down instead!

Win2003login.jpg

 

Now you can look at other options like using this VM 2003 server to act as a PXE server for other Windows OS images like Win7.

For a Win server VM that normally wants to be the main DHCP server, but in this case its undesirable, so beware some funky IP subnet numbers your home router may assign it during the setup!

DHCPfromVigor.jpg

To view these VMs remotely you can use the VMM on another Mint PC and use the remote SSH function.

For Windows, you can DL the 32/64 bit Spice viewers MSIs from:

http://virt-manager.org/download/

This didn't work for me, but needs research.

I'm using VNC anyway so not a big deal just yet.

6/8/15

Just found something unexpected running XP in a VM in Mint: accessing a shared drive on another Mint PC and doing some housekeeping, deleting many folders, spur of the moment, I found the processes happened incredibly fast compared to "normal" netshare actions/deletions over the network from either a Win or Mint box.

Whether the VM code is optimised/written better for efficient running more so than normal "host" code, I don't know - but it made large folder deletions a lot less time consuming going via the XP VMM network share! Odd...?

Comments are closed.

Post Navigation