Skip to main content

Microsoft's Virtualization platform too weak to deploy




This article talks about how Microsoft is trailing behind in its Virtualization adventure.

However, Microsoft does say that this technology is likely to be included in a Service Pack 1 release of the product, but this also raises questions about Microsoft's ability to produce the live migration capability on its architecture for WSV.

The knock-on effect of live migration not being in the first release of WSV is that Microsoft's System Center Virtual Machine Manager (SCVMM) product, due for release in the second half of 2007, will not be able to perform the live movement of VMs, which is a major reason why some customers would use SCVMM.

The second feature removed from the first release version of WSV is the ability to add storage, network, memory, or CPUs on-the-fly to running VMs This lack of this ability will restrict users from dynamically adjusting the resources to meet the current demands.


The rest of the article 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