Skip to main content

Virtualization: Vista is a non-issue

Its Saturday and I have no time to ponder about this repeatedly slamdunked dead horse. Microsoft does not want people to run Vista on Virtualization. Why?
  • Vista is new to the market
  • It still has a reputation to build
  • Reputation: Lots of folks are testing lots of distros on Virtualization platforms and sure they will all complain that their Virtual Vista is running too slow. I might just need to run with some finely tuned sweet spots. So this is going to be a major cause of Vista's poor sales as it would get a lot of negative publicity like: "My Vista runs awfully slow!" Heck even people running Vista on a new hardware might be disappointed. Bottom line: Vista needs good reviews.
  • Virtualization is not new to the market and it certainly is not a new technology

For production machines and everyday usage, virtualization is a fairly new technology, and one that we think is not yet mature enough from a security perspective for broad consumer adoption. Today, customers using virtualization technology with Windows are primarily business customers addressing application compatibility needs or technology enthusiasts.

For that reason, Windows Vista Home Basic and Windows Vista Home Premium cannot be installed in any virtual machine technology, but Windows Vista Business and Windows Vista Ultimate can. This is regardless of the virtualization stack, applying equally to use with Microsoft's virtualization technology, Virtual PC, and third-party virtualization technology.

Each virtual installation of Windows requires a new license just as it did for Windows XP except for Windows Vista Enterprise Edition which includes four installations in a virtual machine as part of a single license. Microsoft is committed to working with the hardware and software industry to improve the security of virtualization technologies moving forward with new hardware and software innovations.


So it is not Virtualization but Vista that is new to the users out there. But anyways Microsoft does respond to it (If I remember I did see this rfesponse on the ZDnet Asia news, I guess a plain copy-n-paste PR response)





Read the rest on BetaNews...
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