• View Communities
    • Citrix Developer Network
      The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
    • Citrix Ready Community Verified
      Does it work with Citrix? Application compatibility questions are a thing of the past with the new Citrix Community Verified site.
    • Blogs
      Learn the latest from the Citrix employees who are building application delivery infrastructure technologies.
    • Blogosphere
      The Citrix Blogosphere is a window into the thousands of conversations taking place about Citrix and Application Delivery.
  •  Sign In
The Citrix Blog
Personal Blog
Simon Crosby
Related Tags
Version 1 by Simon Crosby
on Feb 19, 2008 14:21.


 
compared with
Current by Simon Crosby
on Feb 19, 2008 14:21.


 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 2 changes. View first change.

 With both my Citrix XenServer and Xen community hats on at once, I have to salute another piece of creative writing from the VMware competitive misinformation department.  This time it's about CPU architectures and live relocation (which we call XenMotion, just because we can).  The piece states that we [don't check CPU compatibility on migration of a VM between servers.|http://mikedatl.typepad.com/mikedvirtualization/2008/02/migrating-from.html|More Mike Misinformation]   This is ridiculous, because if we didn't VMs would be crashing about our ears when we do live relocations.  Both in XenServer and in open source Xen, we require a match on CPU processor vendor, family and stepping before a migration can be performed. 
  
 I'm beginning to understand why this blog is called "A *{_}little{_}* truth...".  While I'm all for competitive intelligence in general, when the code is available in open source for everyone to review, it's just not possible to pull the wool over everyone's eyes like this.
  I'm beginning to understand why the VMware blog is called "A *{_}little{_}* truth...".  While I'm all for competitive intelligence in general, when the code is available in open source for everyone to review, it's just not possible to pull the wool over everyone's eyes like this.
  
 And though I know this has hit the wires before, I keep hearing from VMware customers that are buying XenServer why they love the simplicity and robustness of our product and of Xen: The total number of *patches shipped to date for XenServer: 0*.  Total hot fixes and [*patches shipped last year for VMware VI3/ESX alone: 68*|http://www.virtualization.info/2007/12/patch-tuesday-for-vmware.html|Do they check if it works before shipping?]*\!* of which *17 were critical*.  Silly me\! Those were probably only "feature enhancements".  \\
  And though I know this has hit the wires before, I keep hearing from VMware customers that are buying XenServer why they love the simplicity and robustness of our product and of Xen: The total number of *patches shipped to date for XenServer: 0*.  Total hot fixes and [*patches shipped last year for VMware VI3/ESX alone: 68*|http://www.virtualization.info/2007/12/patch-tuesday-for-vmware.html|Do they check if it works before shipping?]\*\!\* of which *17 were critical*.  Silly me\! Those were probably only "feature enhancements". 
 \\