{"id":597,"date":"2016-04-27T10:38:09","date_gmt":"2016-04-27T09:38:09","guid":{"rendered":"http:\/\/www.haxed.me.uk\/?p=597"},"modified":"2016-04-27T12:27:49","modified_gmt":"2016-04-27T11:27:49","slug":"installing-kvm-virt-manager-xenserver-rackspace-onmetal","status":"publish","type":"post","link":"https:\/\/haxed.me.uk\/index.php\/2016\/04\/27\/installing-kvm-virt-manager-xenserver-rackspace-onmetal\/","title":{"rendered":"Installing KVM, libvirtd virt-manager and Xenserver for Rackspace onmetal using ZFS & X11 Forwarding"},"content":{"rendered":"

So, you want to run your own hypervisor using xenserver, but you want to have some of the flexibility of KVM too. This instructional guide explains how to install and configure KVM with virt-manager and with X11 forwarding. We will go step by step. In this case I am using a mac.<\/p>\n

Step 1 – Create Rackspace onmetalv2 server<\/h1>\n

\"Screen<\/a>
\nIn this case I’ll be using a 40 cpu 128GB machine as the host utilizing the new onmetalv2 server range offered by Rackspace public cloud.<\/p>\n

Please note that this is a bare metal server, not a cloud server, however it is offered by the same cloud platform at mycloud.rackspace.co.uk<\/p>\n

Step 2 – Install and configure KVM <\/h1>\n
\r\nsudo yum update -y\r\nsudo yum -y install kvm virt-manager libvirt virt-install qemu-kvm xauth dejavu-lgc-sans-fonts\r\n<\/pre>\n
 Step 3 – Start and configure libvirtd <\/h1>\n
\r\nchkconfig libvirtd\r\nservice libvirtd status\r\nservice libvirtd restart\r\nservice libvirtd status\r\n<\/pre>\n
 Step 4 – MAC SYSTEMS – Install X Quartz <\/h1>\n
For mac users simply install X Quartz, which can be found at http:\/\/www.xquartz.org\/<\/a><\/p>\n
 Step 4a – Windows Systems – Install Xming <\/h1>\n
Windows users can get in on the action too, using xming which can be found at https:\/\/sourceforge.net\/projects\/xming\/<\/a><\/p>\n
 Step 5 – MAC SYSTEMS ONLY – Configure X11 Forwarding<\/h1>\n
Xming will work out of the box for windows, but for Mac users you need to make sure you have enabled X11 forwarding. <\/p>\n
\r\ntouch ~\/.ssh\/config\r\necho \"ForwardX11 yes\" >> ~\/.ssh\/config \r\n<\/pre>\n
This simply allows X11 forwarding for Mac users which needs to be done at the client side. Then you can virtualize any application you like on the client, but running the application such as firefox , or even a virtual machine on the remote server. SSHv2 is beautiful. That’s it you’ve completed the most important steps.<\/p>\n
 Running virt-manager for the first time <\/h1>\n
 \r\n[root@on-metal-test-2 ~]# virt-manager\r\n<\/pre>\n
After running the above command you will see something like the image below. You’ll see an X window open on your local client machine, which is associated with an application running on the remote server your connected to via SSH. This is pretty damn cool. <\/p>\n
\"Screen<\/a><\/p>\n
Lets take this further and install firefox to demonstrate how awesome this is!<\/p>\n
\r\nyum install firefox -y\r\n<\/pre>\n
Now we’re using firefox thru ssh, much better and more convenient to use X11 forwarding for this, than using a proxy for instance on the client configured with tunnel or vpn.<\/p>\n
\"Screen<\/a><\/p>\n
Nice!<\/p>\n
Lets take it a bit further and start installing xen server with KVM. I am very tempted to use ZFS for this since onmetal v2 has 2 1600GB disks…<\/p>\n
 Create partitions for KVM store <\/h1>\n
\r\nfdisk -l \r\nfdisk \/dev\/sdc\r\n\r\n# type m , then type n, then type p, enter, enter, enter, enter, then type w\r\n\r\nfdisk \/dev\/sdd\r\n\r\n# type m , then type n, then type p, enter, enter, enter, enter, then type w\r\n <\/pre>\n
 Create filesystem for KVM store <\/h1>\n
\r\n[root@on-metal-test-2 ~]# mkfs.ext3 \/dev\/sdc1 && mkfs.ext3 \/dev\/sdd1\r\nmke2fs 1.42.9 (28-Dec-2013)\r\nDiscarding device blocks: done\r\nFilesystem label=\r\nOS type: Linux\r\nBlock size=4096 (log=2)\r\nFragment size=4096 (log=2)\r\nStride=0 blocks, Stripe width=0 blocks\r\n97656832 inodes, 390624640 blocks\r\n19531232 blocks (5.00%) reserved for the super user\r\nFirst data block=0\r\nMaximum filesystem blocks=4294967296\r\n11921 block groups\r\n32768 blocks per group, 32768 fragments per group\r\n8192 inodes per group\r\nSuperblock backups stored on blocks:\r\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\r\n\t4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,\r\n\t102400000, 214990848\r\n\r\nAllocating group tables: done\r\nWriting inode tables: done\r\nCreating journal (32768 blocks): done\r\nWriting superblocks and filesystem accounting information: done\r\n\r\nmke2fs 1.42.9 (28-Dec-2013)\r\nDiscarding device blocks: done\r\nFilesystem label=\r\nOS type: Linux\r\nBlock size=4096 (log=2)\r\nFragment size=4096 (log=2)\r\nStride=0 blocks, Stripe width=0 blocks\r\n97656832 inodes, 390624640 blocks\r\n19531232 blocks (5.00%) reserved for the super user\r\nFirst data block=0\r\nMaximum filesystem blocks=4294967296\r\n11921 block groups\r\n32768 blocks per group, 32768 fragments per group\r\n8192 inodes per group\r\nSuperblock backups stored on blocks:\r\n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,\r\n\t4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,\r\n\t102400000, 214990848\r\n\r\nAllocating group tables: done\r\nWriting inode tables: done\r\nCreating journal (32768 blocks): done\r\nWriting superblocks and filesystem accounting information: done\r\n<\/pre>\n
Now we have created the filesystem. What about creating the ZFS partition. To do this we need to go thru a fairly laborious process (at least if you don’t know what your doing). As I discovered my yum installation wasn’t automatically providing the correct devel source for the kernel to use the ZFS DKMS module. As ZFS is really a native BSD package. <\/p>\n
One of the problems I had was this<\/p>\n
\r\nLoading new spl-0.6.5.6 DKMS files...\r\nBuilding for 3.10.0-327.10.1.el7.x86_64\r\nModule build for kernel 3.10.0-327.10.1.el7.x86_64 was skipped since the\r\nkernel source for this kernel does not seem to be installed.\r\n  Installing : zfs-dkms-0.6.5.6-1.el7.centos.noarch                                                                                                                       4\/6\r\nLoading new zfs-0.6.5.6 DKMS files...\r\nBuilding for 3.10.0-327.10.1.el7.x86_64\r\nModule build for kernel 3.10.0-327.10.1.el7.x86_64 was skipped since the\r\nkernel source for this kernel does not seem to be installed.\r\n\r\n<\/pre>\n
This can be checked out in more detail by running an;<\/p>\n
\r\nyum search --show-duplicates kernel-devel\r\n# and\r\nrpm -qa | grep kernel\r\n<\/pre>\n
This gave me the right version of the devel kernel I needed to install ZFS to my current kernel with a module, as opposed to completely recompiling the whole thing. Nice!<\/p>\n
 Install ZFS and kernel devel<\/h1>\n
\r\nsudo yum localinstall --nogpgcheck http:\/\/archive.zfsonlinux.org\/epel\/zfs-release.el7.noarch.rpm\r\nsudo yum install epel-release\r\n\r\nsudo yum install zfs kernel-devel-3.10.0-327.10.1.el7.x86_64\r\n <\/pre>\n
 Enable ZFS <\/h1>\n[root@on-metal-test-2 adam]# \/sbin\/modprobe zfs<\/p>\n
 Create the 2 disk mirror using ZFS<\/h1>\n
\r\n[root@on-metal-test-2 adam]# zpool create -f kvmstore mirror sdc1 sdd1\r\n<\/pre>\n
 Check KVM store disk <\/h1>\n
\r\n[root@on-metal-test-2 adam]# df -h\r\nFilesystem      Size  Used Avail Use% Mounted on\r\n\/dev\/md126p1    220G  2.3G  209G   2% \/\r\ndevtmpfs         63G     0   63G   0% \/dev\r\ntmpfs            63G     0   63G   0% \/dev\/shm\r\ntmpfs            63G   26M   63G   1% \/run\r\ntmpfs            63G     0   63G   0% \/sys\/fs\/cgroup\r\ntmpfs            13G  4.0K   13G   1% \/run\/user\/0\r\nkvmstore        1.5T     0  1.5T   0% \/kvmstore\r\n<\/pre>\n
 Run Virt manager to create Xenserver VM <\/h1>\n
Now we’ve created our partition and filesystem and configured ZFS we can run the virtual machines off the new kvm partition store. simples<\/p>\n
 Click top left icon on corner to create new VM <\/h3>\n
\"Screen<\/a><\/p>\n
 Download the Xenserver ISO to \/root of hypervisor<\/h3>\n
\r\nroot@on-metal-test-2 ~]# wget http:\/\/downloadns.citrix.com.edgesuite.net\/10175\/XenServer-6.5.0-xenserver.org-install-cd.iso\r\n--2016-04-27 10:29:22--  http:\/\/downloadns.citrix.com.edgesuite.net\/10175\/XenServer-6.5.0-xenserver.org-install-cd.iso\r\nResolving downloadns.citrix.com.edgesuite.net (downloadns.citrix.com.edgesuite.net)... 104.86.110.32, 104.86.110.49\r\nConnecting to downloadns.citrix.com.edgesuite.net (downloadns.citrix.com.edgesuite.net)|104.86.110.32|:80... connected.\r\nHTTP request sent, awaiting response... 200 OK\r\nLength: 603744256 (576M) [application\/octet-stream]\r\nSaving to: \u2018XenServer-6.5.0-xenserver.org-install-cd.iso\u2019\r\n\r\n100%[====================================================================================================================================>] 603,744,256 17.6MB\/s   in 38s\r\n<\/pre>\n
 Select Local Media (we’re going to use a Xenserver ISO) <\/h3>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
Click browse, then press the bottom left + icon to add some pools. We’re going to add \/root which has our iso in it, and we’re also going to add kvmstore aswell.<\/p>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
Congratulations you have now added the stores. Now all we need to do is finish configuring the VM.<\/p>\n
We want to select the root partition now we have set up the pool, and choose the xenserver iso we just recently downloaded.<\/p>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
We are almost there now! Lets set the number of cpu and ram! Also lets make sure we use the kvmstore we just setup instead of the ‘main disk’ of the server.<\/p>\n
\"Screen<\/a><\/p>\n
Select our KVM store ‘pool’ on the left hand side, and then press + to add the kvmstore.qcow2 volume, see the images for illustration.<\/p>\n
\"Screen<\/a><\/p>\n
\"Screen<\/a><\/p>\n
click choose volume at the bottom left to confirm! And finally name the server <\/p>\n
\"Screen<\/a><\/p>\n
awwww crap ,\u00a0we got this error because the libvirtd kvm configuration isnt running as root<\/p>\n
\"Screen<\/a><\/p>\n
This can be quickly resolved by editing the \/etc\/libvirt\/qemu.conf  and making sure user = “root” and group = “root” are present.<\/p>\n
\"Screen<\/a><\/p>\n
Job done!<\/p>\n","protected":false},"excerpt":{"rendered":"
So, you want to run your own hypervisor using xenserver, but you want to have some of the flexibility of KVM too. This instructional guide explains how to install and configure KVM with virt-manager and with X11 forwarding. We will … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49,9,7,52,5],"tags":[],"class_list":["post-597","post","type-post","status-publish","format-standard","hentry","category-kvm","category-linux","category-management-tools","category-virtualization","category-xen"],"_links":{"self":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts\/597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/comments?post=597"}],"version-history":[{"count":10,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts\/597\/revisions"}],"predecessor-version":[{"id":626,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/posts\/597\/revisions\/626"}],"wp:attachment":[{"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/media?parent=597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/categories?post=597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/haxed.me.uk\/index.php\/wp-json\/wp\/v2\/tags?post=597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}