<?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>Cpu-Mask on BAFM</title><link>https://christian.blog.pakiheim.de/tags/cpu-mask/</link><description>Recent content in Cpu-Mask on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Sat, 16 Aug 2014 09:49:58 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/cpu-mask/index.xml" rel="self" type="application/rss+xml"/><item><title>Extending vMotion compatiblity</title><link>https://christian.blog.pakiheim.de/posts/2014-08-16_extending-vmotion-compatiblity/</link><pubDate>Sat, 16 Aug 2014 09:49:58 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=482</guid><description>&lt;p&gt;Today I did something horrible. I yet again noticed that I bought the wrong CPU&amp;rsquo;s (basically I bought Xeon DP&amp;rsquo;s with four cores). Those have apparently a feature called SSSE3, which makes vMotion with our old Xeon DP&amp;rsquo;s (dual cores) fail before even trying.&lt;/p&gt;
&lt;p&gt;But as we had a cooling outage today (basically &amp;lsquo;cause it broke), I needed to turn off some ESX servers. Thus leaving me with the new ones and one of the old ones. * &lt;strong&gt;yuck&lt;/strong&gt;*&lt;/p&gt;</description></item></channel></rss>