Skip to main content

Virtualization : Slashdot discussion



"VMWare released a white paper detailing its concerns with license changes on Microsoft software that may limit the ability to move virtual-machine software around data centers to automate the management of computing work.


Some interesting and funny comments:

"We set out to partner with Microsoft," said Peter Levine, president of XenSource, "and VMware chose to compete with Microsoft."

Because partnering with Microsoft in a space they want to own has always been a workable strategy, right? Apparently Mr. Levine has been either been asleep for the last ten years, or is determined to be happy with whatever crumbs Microsoft throws him before the poison takes hold.


If Microsoft used the license agreement against Virtual Machines at the same time as releasing their own, they'd get into legal trouble. Legal trouble is a pain in the neck, so what they're doing is saying that "Virtual Machines are a security flaw" and banning them from the operating system. Then, later on, as a complete coincidence Microsoft is going to create "a Virtual Machine that is safe". Luckily for them, the coincidence that they have crafted doesn't involve any competitors!


Same old Microsoft. They can't invent crap anymore, so when a company such as VMware ...


But I wouldn't put too much faith into them being unable to detect whether they're running in a VM. We were trying to install SP2 to SQL Server 2005 last week on a machine that was runnig on VMWare ESX, and the install failed repeatedly. When we checked the logs there were entries that specifically stated that the SP couldn't...read more




Go and discuss it on Slashdot yourself!
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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...
Post a Comment
Read more