Skip to main content

Mike Neil drilled; competition, licensing, security discussed

The prevailing belief among observers is that Microsoft is way behind VMware. What do you say to the WSV-bashers?

At a high level, I disagree. Server virtualization is still a developing market and technology. Since, to a great degree, the utilization of virtualization has been in relatively confined areas, typically in large enterprises or infrastructure products like [VMware's] ESX Server, Microsoft will be able to have a much broader approach and make virtualization available to a wider swath of the industry.

Are you on track for a mid-2008 release of WSV? A lot of people are casting doubts after your spring roadmap adjustments.

We made the adjustments -- the deferral of some of the features -- so we could maintain our schedule and provide the technology with high quality on the timeline that we articulated: Windows Server 2008 plus 180 days. [The server is set to ship Feb. 27, 2008.]

Will the delayed WSV features be delivered in some fashion before the next release, which could be as many as four years away, given the server operating-system release cycle?

Windows Server Virtualization is coming out off the [server] cycle, and while we do plan to follow up with the deferred features in subsequent releases of the [operating system], we have not talked about specific timing. We are hoping to sync up with the cycle.


Read the rest.

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!