Skip to main content

My views on the upcoming VI3 book (based on the samples)

This will be updated by the time I am done reading all the 110 pages on the sample chapter, a good learning experience for me since I too am working on writing my own book out there:

  • Language: Guys, you need to reword this, I wouldn't use words like "Butt" in a hardcopy.
One thing about being in IT (that no one ever mentioned when I got into it), is
that licensing, not to mention the legalities of it, is one of the biggest pain in the
butt issues I deal with all the time. Every time a vendor comes out with a
feature, you get a new price and a new license model.


I should be done in a week (I know , I know, but I am way too busy to just go through the book only). Keep watching this space!!!

Thanks!

Tarry

Comments

  1. I also believe that their definitions of the VI3 versions are wrong. With the starter edition it comes with a license to use with VirtualCenter.

    I echo the comments about 'butt', etc. Granted this document is from some very well respected professionals in the field and they're allowed to write it any way they want. It just makes it sound a little rough around the edges.

    Hopefully the entire book will be available before VMworld.

    ReplyDelete

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

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...