<?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>Ubiquitous Talk &#187; VMware</title>
	<atom:link href="http://blog.laspina.ca/ubiquitous/tag/vmware/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.laspina.ca</link>
	<description>Blogging for technical minds.</description>
	<lastBuildDate>Mon, 31 May 2010 04:29:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Encapsulating VT-d Accelerated ZFS Storage within ESXi</title>
		<link>http://blog.laspina.ca/ubiquitous/encapsulating-vt-d-accelerated-zfs-storage-within-esxi</link>
		<comments>http://blog.laspina.ca/ubiquitous/encapsulating-vt-d-accelerated-zfs-storage-within-esxi#comments</comments>
		<pubDate>Thu, 06 May 2010 21:28:19 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Storage]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[Acceleration]]></category>
		<category><![CDATA[Dedup]]></category>
		<category><![CDATA[Encapsulation]]></category>
		<category><![CDATA[IOMMU]]></category>
		<category><![CDATA[NFS]]></category>
		<category><![CDATA[VT-d]]></category>
		<category><![CDATA[zfs]]></category>

		<guid isPermaLink="false">http://blog.laspina.ca/?p=563</guid>
		<description><![CDATA[Some time ago I found myself conceptually provisioning ESXi hosts that could transition local storage in a distributed manner within an array of hypervisors. The architectural model likens itself to an amorphous cluster of servers which share a common VM client service that self provisions shared storage to it&#8217;s parent hypervisor or even other external [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/encapsulating-vt-d-accelerated-zfs-storage-within-esxi/feed</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Running ZFS over NFS as a VMware Store</title>
		<link>http://blog.laspina.ca/ubiquitous/running-zfs-over-nfs-as-a-vmware-store</link>
		<comments>http://blog.laspina.ca/ubiquitous/running-zfs-over-nfs-as-a-vmware-store#comments</comments>
		<pubDate>Sun, 14 Feb 2010 07:10:48 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[Dedup]]></category>
		<category><![CDATA[NFS]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[zfs]]></category>
		<category><![CDATA[ZIL]]></category>

		<guid isPermaLink="false">http://blog.laspina.ca/?p=491</guid>
		<description><![CDATA[
NFS is definitely a very well rounded high performance file storage system and it certainly serves VMware Stores successfully over many storage products. Recently one of my subscribers asked me if there was a reason why my blogs were more centric to iSCSI. Thus the question was probing for a answer to a question many [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/running-zfs-over-nfs-as-a-vmware-store/feed</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>Securing COMSTAR and VMware iSCSI connections</title>
		<link>http://blog.laspina.ca/ubiquitous/securing-comstar-and-vmware-iscsi-connections</link>
		<comments>http://blog.laspina.ca/ubiquitous/securing-comstar-and-vmware-iscsi-connections#comments</comments>
		<pubDate>Tue, 30 Jun 2009 00:40:17 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[CHAP]]></category>
		<category><![CDATA[comstar]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[initiator]]></category>
		<category><![CDATA[iscsi]]></category>
		<category><![CDATA[itadm]]></category>
		<category><![CDATA[Mutual]]></category>
		<category><![CDATA[target]]></category>

		<guid isPermaLink="false">http://blog.laspina.ca/?p=189</guid>
		<description><![CDATA[Connecting VMware iSCSI sessions to COMSTAR or any iSCSI target provider securely is required to maintain a reliable system. Without some level of initiator to target connection gate keeping we will eventually encounter a security event. This can happen from a variety of sources, for example a non-cluster aware OS can connect to an unsecured VMware shared storage LUN and cause severe damage [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/securing-comstar-and-vmware-iscsi-connections/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>VMware Kernel Return Codes</title>
		<link>http://blog.laspina.ca/ubiquitous/vmware-kernel-return-codes</link>
		<comments>http://blog.laspina.ca/ubiquitous/vmware-kernel-return-codes#comments</comments>
		<pubDate>Wed, 20 May 2009 04:41:03 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[Kernel]]></category>
		<category><![CDATA[logs]]></category>
		<category><![CDATA[lookup]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=79</guid>
		<description><![CDATA[From time to time I find myself reaming through VMware log files in an effort to diagnose various failure events. This is certainly not my favorite task so to make the process a little less painful I decided to extract the vmkernel return codes from the VMware open source libraries and place an easily accessible tabled version of them on my blog. While [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/vmware-kernel-return-codes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting ESX VMFS Stores with Automation</title>
		<link>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation</link>
		<comments>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation#comments</comments>
		<pubDate>Mon, 30 Mar 2009 03:31:48 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[automated]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[cron]]></category>
		<category><![CDATA[scripts]]></category>
		<category><![CDATA[undelete]]></category>
		<category><![CDATA[vmfs]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=98</guid>
		<description><![CDATA[Some time ago I shared some interesting information about VMFS volumes that I found using direct analysis in my blog named Understanding VMFS volumes. This spawned some discussions on the VMware Community forums and it became apparent that an automated backup of the critical VMFS info could be useful in the event of an undesirable security event that impacts our [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/protecting-esx-vmfs-stores-with-automation/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Awarded VMware vExpert Status</title>
		<link>http://blog.laspina.ca/ubiquitous/awarded-vmware-vexpert-status</link>
		<comments>http://blog.laspina.ca/ubiquitous/awarded-vmware-vexpert-status#comments</comments>
		<pubDate>Sun, 01 Mar 2009 04:39:03 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vexperts]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=112</guid>
		<description><![CDATA[While I was away at the OpenSolaris Storage Summit in San Francisco a really nice email appeared in my inbox which put a grateful smile on my face. John Troyer and his team felt that I was worthy of the vExperts award. I&#8217;m honoured to receive the recognition and thank-you to the judging panel members 
Congrats to all the other recipients as [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/awarded-vmware-vexpert-status/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multi Protocol Storage Provisioning with COMSTAR</title>
		<link>http://blog.laspina.ca/ubiquitous/multi_protocol_storage_provisioning_with</link>
		<comments>http://blog.laspina.ca/ubiquitous/multi_protocol_storage_provisioning_with#comments</comments>
		<pubDate>Mon, 26 Jan 2009 06:01:42 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Storage]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[clones]]></category>
		<category><![CDATA[comstar]]></category>
		<category><![CDATA[fc]]></category>
		<category><![CDATA[fcoe]]></category>
		<category><![CDATA[gateway]]></category>
		<category><![CDATA[iscsi]]></category>
		<category><![CDATA[iser]]></category>
		<category><![CDATA[multi]]></category>
		<category><![CDATA[opensolaris]]></category>
		<category><![CDATA[protocol]]></category>
		<category><![CDATA[provision]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[reprovision]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[snapshot]]></category>
		<category><![CDATA[sparse]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[thin]]></category>
		<category><![CDATA[vmfs]]></category>
		<category><![CDATA[zfs]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=75</guid>
		<description><![CDATA[ COMSTAR is a new breed of open source storage product available to the world. What was traditionally a closed and proprietary storage capability is now available to our open source communities. With OpenSolaris and COMSTAR the ability to freely provision virtual storage services over very mature high end protocols on standard commodity server hardware is now a reality. High performance transports [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/multi_protocol_storage_provisioning_with/feed</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Understanding VMFS volumes</title>
		<link>http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes</link>
		<comments>http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes#comments</comments>
		<pubDate>Wed, 21 Jan 2009 23:16:42 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[deleted]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[esxi]]></category>
		<category><![CDATA[fdisk]]></category>
		<category><![CDATA[guid]]></category>
		<category><![CDATA[header]]></category>
		<category><![CDATA[hex]]></category>
		<category><![CDATA[lun]]></category>
		<category><![CDATA[lvm]]></category>
		<category><![CDATA[partition]]></category>
		<category><![CDATA[path]]></category>
		<category><![CDATA[recover]]></category>
		<category><![CDATA[resignature]]></category>
		<category><![CDATA[sector]]></category>
		<category><![CDATA[uuid]]></category>
		<category><![CDATA[vml]]></category>
		<category><![CDATA[volume]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=68</guid>
		<description><![CDATA[Understanding VMFS volumes is an important element within VMware ESX environments. When storage issues surface we need to correctly evaluate the VMFS volume states and apply the appropriate corrective actions to remediate undesirable storage events. VMFS architecture is not publically available and this certainly adds to the challenge when we need to correct a volume configuration or change [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/understanding-vmfs-volumes/feed</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>A centrally based method for patching ESX3 VMWare Servers</title>
		<link>http://blog.laspina.ca/ubiquitous/a_centrally_based_method_forpatching-esx3-vmware-servers</link>
		<comments>http://blog.laspina.ca/ubiquitous/a_centrally_based_method_forpatching-esx3-vmware-servers#comments</comments>
		<pubDate>Mon, 08 Dec 2008 05:45:40 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[patch]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=61</guid>
		<description><![CDATA[I have updated my ESX servers manually many times and I find the process to say at the least is &#8221;annoying&#8221; so I decided to change it to an http based method with a modified patch configuration. I found that it really works well. 
I did some searching prior to the method I settled on and found [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/a_centrally_based_method_forpatching-esx3-vmware-servers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware image customization in progress issue</title>
		<link>http://blog.laspina.ca/ubiquitous/vmware_image_customization_in_progress</link>
		<comments>http://blog.laspina.ca/ubiquitous/vmware_image_customization_in_progress#comments</comments>
		<pubDate>Mon, 17 Nov 2008 09:22:25 +0000</pubDate>
		<dc:creator>Mike La Spina</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[image]]></category>
		<category><![CDATA[sysprep]]></category>
		<category><![CDATA[template]]></category>
		<category><![CDATA[vm]]></category>

		<guid isPermaLink="false">http://ux1.laspina.ca/?p=32</guid>
		<description><![CDATA[I just came across this very annoying VMware guest customization artifact. I neglected to update the sysprep directories at 
C:\&#60;ALLUSERSPROFILE&#62;\Application Data\Vmware\VMware VirtualCenter\sysprep
with a current version and it resulted in a failed image customization that would not go away. On each system restart a boot time run of sysprepDecrypter.exe would occur and cause a continual loop of [...]]]></description>
		<wfw:commentRss>http://blog.laspina.ca/ubiquitous/vmware_image_customization_in_progress/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
