<?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>Technolab 2.0 &#187; VMware</title> <atom:link href="http://www.virtlab.biz/category/vmware/feed" rel="self" type="application/rss+xml" /><link>http://www.virtlab.biz</link> <description>...playing around with technology</description> <lastBuildDate>Sun, 22 Jan 2012 00:33:47 +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>Memory hotplug in Linux</title><link>http://www.virtlab.biz/vmware/471</link> <comments>http://www.virtlab.biz/vmware/471#comments</comments> <pubDate>Sat, 21 Jan 2012 21:25:48 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[Linux]]></category> <category><![CDATA[VMware]]></category> <category><![CDATA[hacks]]></category> <category><![CDATA[linux]]></category> <category><![CDATA[vmware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=471</guid> <description><![CDATA[VMware has a nice feature where you can add memory and CPUs on the fly without rebooting the server. It works like a charm in Windows, but it did not work out of the box in Linux. The trick is to load the module acpi_memhotplug so that the Linux kernel discovers the new memory that &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/471">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/471/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>VMware ESXi 5.0</title><link>http://www.virtlab.biz/vmware/431</link> <comments>http://www.virtlab.biz/vmware/431#comments</comments> <pubDate>Mon, 22 Aug 2011 20:46:44 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <category><![CDATA[5.0]]></category> <category><![CDATA[esxi]]></category> <category><![CDATA[vmware]]></category> <category><![CDATA[vsphere]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=431</guid> <description><![CDATA[A few brief notes on the new VMware ESXi 5.0 release that are probably not covered elsewhere yet. My Asus P8H67-I mini-ITX board is fully supported in 5.0 (it was supported in 4.x as well) Realtek RTL8111E is supported out of the box. I have not yet tried it (I am using an Intel Pro/1000 &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/431">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/431/feed</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Installing ESXi 4.1 from an USB stick</title><link>http://www.virtlab.biz/vmware/295</link> <comments>http://www.virtlab.biz/vmware/295#comments</comments> <pubDate>Sat, 06 Aug 2011 22:33:56 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <category><![CDATA[boot]]></category> <category><![CDATA[esxi]]></category> <category><![CDATA[kickstart]]></category> <category><![CDATA[usb]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=295</guid> <description><![CDATA[As I wrote in the previous post, I recently bought a mini-iTX card with an Intel Core i3 to replace my aging firewall/router. It so happens that it fully supports VMware ESXi as well, so I loaded it up and are running the router/firewall as a virtual machine. Now, installing VMware ESXi 4.1 from an &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/295">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/295/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Whitebox ESXi</title><link>http://www.virtlab.biz/vmware/292</link> <comments>http://www.virtlab.biz/vmware/292#comments</comments> <pubDate>Sat, 06 Aug 2011 22:13:18 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[VMware]]></category> <category><![CDATA[asus]]></category> <category><![CDATA[esxi]]></category> <category><![CDATA[hardware]]></category> <category><![CDATA[mini-itx]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=292</guid> <description><![CDATA[I remember the first time I got my hands on VMware ESXi. It was the 3.5 version and it quickly became apparent to me that this was the feature. Long gone was the chubby ESX COS which I used before. Of course, having a full COS (Linux) had its benefits, but it did little to &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/292">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/292/feed</wfw:commentRss> <slash:comments>11</slash:comments> </item> <item><title>Breaking the VMware Update Manager</title><link>http://www.virtlab.biz/vmware/273</link> <comments>http://www.virtlab.biz/vmware/273#comments</comments> <pubDate>Wed, 01 Jul 2009 02:12:28 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=273</guid> <description><![CDATA[You should believe that the VMware Update Manager was capable of handling missing files. But no, it does not. I removed a couple of files from the repository by simply pressing delete on them. These files were part of a host upgrade baseline and were no longer needed. After the delete operation, I can no &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/273">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/273/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Performance monitoring problem</title><link>http://www.virtlab.biz/vmware/257</link> <comments>http://www.virtlab.biz/vmware/257#comments</comments> <pubDate>Fri, 19 Jun 2009 23:16:12 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=257</guid> <description><![CDATA[My new R710 running ESXi 4.0 has one problem: When the CPU load comes close to maximum, all performance monitoring for the host failes. Only a few, random monitoring requests comes through, making the resource graphs in vCenter look pretty ugly. As you can see from the attached image, a lot of data is missing. &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/257">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/257/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Automatic installation of ESX 4.0</title><link>http://www.virtlab.biz/vmware/252</link> <comments>http://www.virtlab.biz/vmware/252#comments</comments> <pubDate>Fri, 19 Jun 2009 22:22:27 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=252</guid> <description><![CDATA[Mike La Spina has written a nice post about automatic installation of ESX 4.0 hosts utilizing PXE, kickstart and a lot of scripts. Mike has done a nice job creating configuration scripts, making it easy to copy his ideas for use in your own environment. Auto installation becomes necessary if you need to deploy a &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/252">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/252/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Feature requests, take two</title><link>http://www.virtlab.biz/vmware/209</link> <comments>http://www.virtlab.biz/vmware/209#comments</comments> <pubDate>Wed, 10 Jun 2009 15:29:32 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=209</guid> <description><![CDATA[It&#8217;s been nearly 11 months since I wrote the feature request post where I asked for some features currently missing in VMware. Now, it&#8217;s time to see how it went: Live Cloning or backup: Live cloning to either a template or a new VM was added in ESXi 3.5 U2. Storage VMotion GUI integration: New &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/209">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/209/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Changing host name and IP address of a vCenter server</title><link>http://www.virtlab.biz/vmware/198</link> <comments>http://www.virtlab.biz/vmware/198#comments</comments> <pubDate>Wed, 10 Jun 2009 13:35:16 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=198</guid> <description><![CDATA[I recently had the pleasure of trying to change the host name and IP address of the vCenter server. The old host has two networking interfaces. NIC1 was connected to the Internet while NIC2 was connected to an internal network with IP address 192.168.30.0/24. The vCenter and the plugins were configured to use the internal &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/198">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/198/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Dell PowerEdge R200 and ESXi 4.0</title><link>http://www.virtlab.biz/vmware/193</link> <comments>http://www.virtlab.biz/vmware/193#comments</comments> <pubDate>Wed, 10 Jun 2009 12:58:10 +0000</pubDate> <dc:creator>Frode Sandholtbråten</dc:creator> <category><![CDATA[Hardware]]></category> <category><![CDATA[VMware]]></category> <guid
isPermaLink="false">http://www.virtlab.biz/?p=193</guid> <description><![CDATA[I promised some more details on the R200 and ESXi 4.0. Full hardware spec: Server: Dell PowerEdge R200 Processors: 1x Intel Xeon X3320 2.5GHz Quad Core Memory: 6GiB, DDR2 667MHz ECC Disk space: 1x640GB SATA + 1x80GB SATA Storage controller: Intel ICH9 NIC: 2x Broadcom BCM5721, 1x Intel PRO/1000PT PCI-E Dual Port OS: VMware ESXi &#8230;</p><p><a
class="more-link block-button" href="http://www.virtlab.biz/vmware/193">Continue reading &#187;</a>]]></description> <wfw:commentRss>http://www.virtlab.biz/vmware/193/feed</wfw:commentRss> <slash:comments>3</slash:comments> </item> </channel> </rss>
