<?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>Malaysia VMware Communities &#187; Netware</title>
	<atom:link href="http://malaysiavm.com/blog/tag/netware/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Netware 6.5 on VMware</title>
		<link>http://malaysiavm.com/blog/netware-65-on-vmware/</link>
		<comments>http://malaysiavm.com/blog/netware-65-on-vmware/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 16:43:31 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[Workstations]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[Netware]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[VMware Server]]></category>
		<category><![CDATA[VMware Workstation]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=565</guid>
		<description><![CDATA[I had recently setup a development environment to verify the potential of migrating the existing age servers which running with Netware 6.5 from physical to virtual. The reason of doing this is purely due to the expiration of our server life cycle, and potential to reduce the capex requirement for replacing with new servers. As [...]]]></description>
			<content:encoded><![CDATA[<p>I had recently setup a development environment to verify the potential of migrating the existing age servers which running with <a href="http://malaysiavm.com/blog/tag/netware">Netware</a> 6.5 from physical to virtual. The reason of doing this is purely due to the expiration of our server life cycle, and potential to reduce the capex requirement for replacing with new servers. As we know that the <a href="http://malaysiavm.com/blog/tag/novell">Novell</a> Netware 6.5 will not able to utilize the quad cores processing power which is consider a common servers resources today.</p>
<p>I had tried to setup the VM for Netware 6.5 on <a href="http://malaysiavm.com/blog/tag/vmware">VMware</a> ESX 3.5, VMware Server 2.0 and VMware <a href="http://malaysiavm.com/blog/tag/workstation">Workstation</a> 6.5, and it was surprised myself that the workstation edition, I can easily provide 2 Vcpu for a single VM which run the Netware 6.5, which <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> 3.5 and VMware Server 2.0 is refused by default. I went for some google search and technical research, it show that the Netware will not require to have 2 Vcpu in most cases, even if you need to do so, you have to know the back door to overcome this.</p>
<p><span id="more-565"></span></p>
<p>To force 2 <a href="http://malaysiavm.com/blog/tag/vcpu">Vcpu</a> per VM, you will require to log in through the web console on the ESX host, and power off the <a href="http://malaysiavm.com/blog/tag/vm">VM</a>. Edit the Vcpu numbers from 1 to 2 or 4. My test result, 2 might be the better option on ESX. Power up your VM now, you should able to see the 2 Vcpu on <a href="http://malaysiavm.com/blog/tag/netware">Netware</a> 6.5 which run on ESX 3.5. Weird thing happen now, you will notice that the CPU utilization is very high and consistently over 50% even with fresh install Netware 6.5. When you do a monitor command from netware, you will only see the 5% utilization from the <a href="http://malaysiavm.com/blog/tag/cpu">CPU</a>. I am sure there is bugs from VMware regarding this.</p>
<p>Now we go to VMware <a href="http://malaysiavm.com/blog/tag/server">Server</a> 2.0, you need to export the image from <a href="http://malaysiavm.com/blog/tag/esx">ESX</a> 3.5 to VMware Server, and power it up. Please do not modify the number of cpu per vm on the webconsole, as it is not allow to be run more than 1Vcpu for <a href="http://malaysiavm.com/blog/tag/netware">Netware</a> 6.5 on vmware server by default. In this case, the CPU utilization on VMware server is much more acceptable which only 30% utilize.</p>
<p>Due to a low demand on Netware today, I believe it is the reason of VMware is not investing too much time of fixing the netware issues. But again, I believe it  is sufficient to host the netware server on <a href="http://malaysiavm.com/blog/tag/vmware">VMware</a> as it will not require the extra resources as we normally have on any server today.</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/netware-65-on-vmware/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.318 seconds -->

