<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Xen Hypervisor Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://vavai.net/tag/xen-hypervisor/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/xen-hypervisor/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Thu, 05 Aug 2010 03:50:33 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>KVM Virtualization on openSUSE 11.3</title>
		<link>https://vavai.net/kvm-virtualization-on-opensuse-11-3/</link>
					<comments>https://vavai.net/kvm-virtualization-on-opensuse-11-3/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Thu, 05 Aug 2010 03:50:33 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[KVM]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Xen Hypervisor]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1216</guid>

					<description><![CDATA[<p>It&#8217;s looks like that I&#8217;m off and hiatus from blog for a while so it&#8217;s time to starting a new article and hope it&#8217;s not for the last one 😀 . KVM (Kernel-based Virtual Machine) is currently popular terms among the virtualization technology. What makes it popular and become the strong competitor for Xen Hypervisor...</p>
<p>The post <a href="https://vavai.net/kvm-virtualization-on-opensuse-11-3/">KVM Virtualization on openSUSE 11.3</a> appeared first on <a href="https://vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>It&#8217;s looks like that I&#8217;m off and hiatus from blog for a while so it&#8217;s time to starting a new  article and hope it&#8217;s not for the last one <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /> .<br />
KVM (<em>Kernel-based Virtual Machine) </em>is currently popular terms among the virtualization technology. What makes it popular and become the strong competitor for Xen Hypervisor are the technology behind KVM and Red Hat decision to move focus on KVM instead of Xen for next release Red Hat Enterprise Linux 6.0. What makes KVM gains an advantage on the technology side are the inclusion KVM module into Linux kernel so we do not need a patch or different kernel as we need for Xen Hypervisor. Beside the two virtualization technology above, those are various virtualization technology running on Linux : VMWare, VirtualBox, OpenVZ etc but Xen and KVM are quite popular among others.<br />
SUSE Linux Enterprise Server 11 was added KVM beside Xen Hypervisor on Service Pack 1 release. openSUSE 11.3 released on July 15, 2010 also appendÂ  KVM as Virtualization package beside the default Xen Hypervisor. Following article covers KVM installation on openSUSE 11.3 64 bit (the 32 bit installation should be similar).</p>
<ol>
<li>Install KVM module by using YAST orÂ  Zypper.Â  Install following package : <strong>kvm, libvirt, libvirt-python, virt-utils, yast2-vm, virt-manager, virt-viewer, bridge-utils, vm-install</strong>. We may also install virtualization stuff by using <strong>YAST | Virtualization | Install Hypervisor and Tools</strong> and then adds KVM package withinÂ  YAST | Software | Software Management, but the second tips will also installingÂ  Xen Hypervisor  <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> . SLES 11 SP1 has different way to install KVM by asking which Virtualization technology should be install if we choose second tips. I don&#8217;t know why openSUSE take different method to install and not as simple as SLES 11 SP1 has.</li>
<li>Activate Virtual Daemon. Open <strong>YAST |  System | System Services (runlevel)</strong> and mark <strong>libvirtd</strong> as enable services<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://54.254.121.108/wp-content/uploads/2010/08/kvm-runlevel.jpeg"><img fetchpriority="high" decoding="async" class="alignnone size-full wp-image-1887" title="kvm-runlevel" src="http://54.254.121.108/wp-content/uploads/2010/08/kvm-runlevel.jpeg" alt="" width="473" height="475" /></a></li>
<li>Open YAST | Virtualization | Virtual Machine Manager<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/08/kvm-virt-manager.jpeg"><img decoding="async" class="alignnone size-full wp-image-1888" title="kvm-virt-manager" src="http://vavai.com/wp-content/uploads/2010/08/kvm-virt-manager.jpeg" alt="" width="480" height="319" /></a></li>
<li>If Virtual Machine Manager has noÂ  &#8220;localhost (QEMU) option, add the KVM instance by clickingÂ  menu <strong>File | Add Connection</strong> and choose KVM/QEMU and then click <strong>Connect</strong><br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/08/kvm1.jpeg"><img decoding="async" class="alignnone size-full wp-image-1889" title="kvm1" src="http://vavai.com/wp-content/uploads/2010/08/kvm1.jpeg" alt="" width="353" height="445" /></a></li>
<li>After that, we may create a new virtual appliance by clickÂ  <strong>New</strong> and follows theÂ  wizard.<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/08/kvm2.jpeg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1890" title="kvm2" src="http://vavai.com/wp-content/uploads/2010/08/kvm2.jpeg" alt="" width="463" height="388" /></a></li>
</ol>
<p>Managing KVM on openSUSE/SLES seems to be similar as managing Xen Hypervisor because both virtualization using same front-end application (libvirt) on openSUSE/SLES YAST. KVM need a motherboard supporting virtualization extensions as it&#8217;s feature, e.g : Intel VT (Virtualization technology) or AMD-V. To check whether your motherboard supporting virtualization extension, run the following command on konsole/terminal :<br />
Intel VT :<br />
[code language=&#8217;cpp&#8217;]<br />
grep &#8211;color vmx /proc/cpuinfo<br />
[/code]<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://54.254.121.108/wp-content/uploads/2010/08/virtualization-extension1.jpeg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1217" title="virtualization-extension" src="http://54.254.121.108/wp-content/uploads/2010/08/virtualization-extension1.jpeg" alt="" width="480" height="239" /></a><br />
AMD-V<br />
[code language=&#8217;cpp&#8217;]<br />
grep &#8211;color svm /proc/cpuinfo<br />
[/code]<br />
Some motherboard disable virtualization extension by default so you must check BIOS setting to see whether virtualization extension has been activated or not.</p>
<p>The post <a href="https://vavai.net/kvm-virtualization-on-opensuse-11-3/">KVM Virtualization on openSUSE 11.3</a> appeared first on <a href="https://vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://vavai.net/kvm-virtualization-on-opensuse-11-3/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 29/47 objects using Disk
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d3b35uem336dgh.cloudfront.net
Lazy Loading (feed)
Minified using Disk
Database Caching 18/31 queries in 0.013 seconds using Disk

Served from: vavai.net @ 2026-11-21 18:25:51 by W3 Total Cache
-->