Skip to main content

Citrix XenServer CTO, Simon Crosby, interviewed

The Syscon guys RSS me all the time so we will linkback to the guys with this post ;-)

Virtualization Journal: Starting at 35,000 ft…where does the Xen hypervisor fit in the virtualization universe?
Simon Crosby: The Xen hypervisor is the industry’s most strategic code base for virtualization. Why? First, it is a tiny, optimized, open source reference standard hypervisor for a wide range of CPU architectures, with extensive support for high performance virtualization-enhanced CPUs and I/O subsystems. Because it has multiple routes to market in any given year, the hardware manufacturers ensure that Xen has “first and best” support for the latest hardware, ensuring that it always leads the industry in scalability and performance. In addition:
  • It is collaboratively built by the industry’s leading IT vendors, led by Citrix and including Intel, AMD, IBM, HP, Novell, Red Hat, Sun, VA Linux and many others.
  • The Xen security architecture is contributed by the security community, including researchers, IBM’s secure hypervisor project, the NSA and DoD.
  • Xen is used in the world’s largest virtualization deployments, for example by Amazon, with a deployment of thousands of servers virtualized using Xen.
  • The Microsoft Hyper-V hypervisor is in fact an implementation of the Xen reference architecture, built by Microsoft, and compatible with Citrix XenServer.
Virtualization Journal: The first public release of Xen was made available in 2003, how long did it take for you and your Cambridge collaborators to get it to that stage?
Crosby: The Xen code base has been in development now for seven years. When we started XenSource, we had released Xen 2.5, and were working on Xen 3.0.


More here...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!