Skip to main content

Welcome Home, Brian!



I'm speechless and overwhelmed with the birth of my Son. Welcome home, Son!

Brian, born on 15:56 (GMT+1) hours, 17th Feb 2006.

PS: On another note. It's gotta be an auspicious day for VMware as they choose the same day (17th Feb) to send out invitations for Beta testers (ESX 3.0/VC2.0) finally.:-)

Comments

  1. I'm a bit confused as to where VM ends and Brian begins. Am I right in thinking he's not virtual?

    Hearty congratulations - DaPi.

    ReplyDelete
  2. David,

    Indeed, he's all flesh and blood.

    It's just that the long awaited ESX 3.x beta invitations too got sent out on the same date ;-)

    Thanks again.

    Tarry

    ReplyDelete
  3. Tarry --

    Congratulations! Start him virtualizing early! :-)

    John

    ReplyDelete
  4. Hey John,

    Thanks a lot!

    We're looking at the future CEO VMware here..heh heh

    ReplyDelete
  5. I can't believe I missed this post. Congratulations papa! Hope everyone is fine.

    All the best,
    Bill

    ReplyDelete
  6. That's OK Bill,

    Thanks a lot! :-) Everyone is doing fine indeed.

    ReplyDelete
  7. congratulations... Tarry.
    I was just browsing your blog & found this post.
    Nice blog. Keep on posting...

    ReplyDelete
  8. Thanks pran,

    Appreciate your kind words.

    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...