Skip to main content

VMware: A Classic from 2002



I'm a sucker of old nostalgic stuff. Just like that beautiful place in Japan (Kanokawa) which I visited in 1995. It always is such a pleasure to just run across some older versions and stories and visit the past (which held great promises of today, the future then).

This nice little explanation is one of those.

As for essence of imagination PC you expressed that there is the simultaneity. Other multiple boot technique never is not is quite the important function which cannot. When plural PC exist simultaneously, naturally as for exchanging the information of that PC that the problem which you say whether how it does happens. Because information interchange between each PC, it means that many of meaning of simultaneity are lost.

　If with VMware once it is the text data, it is possible to share between host OS, and each guest OS via the clipboard, but information interchange after all in earnest, probably there are no other things in network. Calling information interchange, because with special care plural PC can exist simultaneously, exceeding the dimension such as mere file sharing and data sharing, if you can verify network application and you can verify real client [sabashisutemu], how it probably is convenient.


While this might seem like "Hmmm..nice old times". I'm pretty sure many of you out there are running a lot older applications and OSs.( Heck, like I told you last, I found out myself of an old NT 4 sp5 servers running on a oldish PC in our production !, which was going to die quietly anytime). So get a free version of VMware and start testing today!

Read this nice article here (translated OR Japanese version)
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

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