<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Vsphere on BAFM</title><link>https://christian.blog.pakiheim.de/tags/vsphere/</link><description>Recent content in Vsphere on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Tue, 23 Feb 2010 18:24:01 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/vsphere/index.xml" rel="self" type="application/rss+xml"/><item><title>VMware vSphere: Safely remove network controller</title><link>https://christian.blog.pakiheim.de/posts/2010-02-23_vmware-vsphere-safely-remove-network-controller/</link><pubDate>Tue, 23 Feb 2010 18:24:01 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2996</guid><description>&lt;p&gt;Well, it&amp;rsquo;s another day another fight. As we started migrating our VM&amp;rsquo;s from the old VMware ESX farms to the new environment, and upgraded the hardware suddenly the network devices were hot-plug-able, thus they did turn up in the &amp;ldquo;Safely Remove&amp;rdquo; dialog.&lt;/p&gt;
&lt;p&gt;I myself don&amp;rsquo;t have any trouble with that. The trouble I do have is the people working with those VM&amp;rsquo;s and their possibly hazardous &amp;ldquo;uuuh, what&amp;rsquo;s this ? I don&amp;rsquo;t need this! &amp;lt;click-click, network-device unplugged&amp;gt;&amp;rdquo;&lt;/p&gt;</description></item><item><title>ESX: Query CDP information from the command line</title><link>https://christian.blog.pakiheim.de/posts/2009-10-29_esx-query-cdp-information-from-the-command-line/</link><pubDate>Thu, 29 Oct 2009 17:20:46 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2725</guid><description>&lt;p&gt;I&amp;rsquo;m just tracing some troubles I&amp;rsquo;m having with a backup server and two (independent) network adapter ports (as in two ports on two different dual-port nics). If I enable the port and set it to auto configuration, it&amp;rsquo;ll get 100MBit/Half-Duplex, but the Portgroup becomes unavailable.&lt;/p&gt;
&lt;p&gt;In order to get the connection back, I need to logon on the console (thank god even the backup server got an iLO2), and manually (as in esxcfg-nics -s 1000 -d full vmnic1) configure the adapter to 1GBit/s and full-duplex.&lt;/p&gt;</description></item><item><title>VMware vSphere and templates</title><link>https://christian.blog.pakiheim.de/posts/2009-07-31_vmware-vsphere-and-templates/</link><pubDate>Fri, 31 Jul 2009 13:51:01 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2486</guid><description>&lt;p&gt;I just converted one of my (old) templates, as I wanted to refresh the updates and the virus scanner. After converting, I was asked about the UUID (no clue why), and expected to be done with it. But after looking at the console, I got the following, completely cryptic message:&lt;/p&gt;
&lt;figure&gt;
&lt;img loading="lazy" src="https://christian.blog.pakiheim.de/uploads/2009/07/win-xp_template-error.png"
alt="Unable to connect to MKS" width="400"/&gt; &lt;figcaption&gt;
&lt;p&gt;Unable to connect to MKS&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;After digging a bit deeper (that is looking at the vmware.log of the virtual machine, since the message of the GUI is &lt;em&gt;&lt;strong&gt;real&lt;/strong&gt;&lt;/em&gt; cryptic), I&amp;rsquo;m a bit wiser:&lt;/p&gt;</description></item><item><title>Updating a Linux VM from Virtual Infrastructure to vSphere</title><link>https://christian.blog.pakiheim.de/posts/2009-07-08_updating-a-linux-vm-from-virtual-infrastructure-to-vsphere/</link><pubDate>Wed, 08 Jul 2009 13:51:50 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=2314</guid><description>&lt;p&gt;Well, if you&amp;rsquo;re gonna update a SLES10 (or even a SLES11) VM, you created with Virtual Infrastructure, you&amp;rsquo;re gonna run into a snag (like I do). Grub (or rather the kernel itself) is gonna barf.&lt;/p&gt;
&lt;p&gt;Now, I searched for a while and didn&amp;rsquo;t find anything specific on the net, so I&amp;rsquo;m gonna write it down. Up till 3.5U4 the maximal resolution you&amp;rsquo;d be able to enter within a virtual machine was vga=0x32d (at least for my 19&amp;quot; TFT&amp;rsquo;s at work). But now, after the upgrade to vSphere that isn&amp;rsquo;t working anymore.&lt;/p&gt;</description></item></channel></rss>