vtAlpha Alpha virtualization runs Bare Metal (directly on top of the host computer) and on a Virtual Machine (VMware, KVM, Xen, Hyper-V) delivering the broadest choice in host environments. We even deliver the vtAlpha product as a VM appliance that you can easily import in your VM so you can start using vtAlpha without going through installation and configuration. Easy does it.
Virtual Machine products can offer live host migration (e.g. VMware vMotion). It allows to migrate a running Virtual Machine from one host computer to another. This is a feature that we like to support and offer to our (virtual) OpenVMS and Tru64 customers for improved resilience. We were pretty sure we could make vtAlpha survive such a live host transition, but what about OpenVMS and Tru64? These were not designed with such functionality in mind, so how would they survive the time lapse that is involved with such a host transition?
We can report that we managed to mask such an event from these older operating systems so any running vtAlpha can be transitioned from one host to another using this VMware capability. We have posted a short video showing such a transition here: vtAlpha host migration.
This capability enables you to build virtual Alpha installations with a disaster resiliency that can be better than with the original Alpha equipment. OpenVMS and Tru64 enthousiasts thought things couldn’t get better than with these operating systems. Guess what: they just did!
Proof is good, but customer confirmation is better. We have multiple customers using this capability and JCC, USA recently reported their positive experience on Twitter,
Check it out and let us know when you want to hear more about this capability.
On April 3, 2013 AVTware gave birth to vtAlpha v2.7.
Additional characteristics of this brand new vtAlpha family member:
- Support for legacy storage types (MSCP, DSSI, IDE and RAID).
- Network File Storage (NFS) included. Interesting for “on the fly” off-host backups.
- vtAlpha full system partition backup and restore.
- Email alerts to notify system management of critical issues.
- Virtual PBXDA (Serial Line Adapter) enhancements.
- Full VMware Vmotion support (migrate a running OpenVMS/Tru64 system from one host to another)
- Various improvements in the management tool.
With this new version vtAlpha shows its constant growth in functionality, again including many requests we receive from our customers.
We encourage you to keep us on the edge, improving the product by telling our local representatives about your desires and requirements for vtAlpha.
Let us know what you like to see in the next version.
OpenVMS Bootcamp 2013, in Bedford MA. An important gathering of openVMS experts from all over the world. Four days full of OpenVMS information exchange and knowledge sharing between the participants. Lecture rooms and hallways buzzing with VMS news and facts.
The OpenVMS operating system and community, 35 years of age and still extremely vivid.
In the evenings there is some time for letting your hair down, although always with a business undercurrent. The Roundhouse is a very good example. A buffet dinner on one of the evenings where the dining table are combined with information tables where OpenVMS partners are present to discuss matters with the attendees.
This event is traditionally concluded with a raffle where people can win OpenVMS related prizes. AVT and Vere offered a free Alpha on a stick, which was won by David Bartz of Quest Diagnostics. Allowing him to run a virtual DS10 on any x86 computer or virtual machine he can lay his hands on.
Tractebel in Brussels, Belgium developed Tru64 and OpenVMS applications for which there is demand outside the current installed base. Using refurbished Alpha hardware for these new installations was not an available option.
Hence they looked at Alpha virtualization that enables them to run the existing Tru64 and OpenVMS software on top of regular x86-type host systems. Multiple Alpha virtualization products were investigated and vtAlpha is their preferred choice.
HP provided the brand new OpenVMS / Tru64 licenses for this installation and everything works like a charm
It shows that with the help of vtAlpha it is still possible to expand the Tru64/OpenVMS customer base, using regular x86 equipment as the host platform.
You too can move your existing Alpha installation to x86-based equipment and prolong its life-time with the help of vtAlpha.
Contact us when you want to know more about this.
Customers who are running multiple virtual Alphas on a single host like to share high speed Ethernet links by multiple virtual Alpha’s. Especially when running on Blade systems that most often only have very few Ethernet connections. For these customers, and the ones with many Ethernet links, we have developed the Virtual Ethernet Switch.
The system manager can create one or more Virtual Ethernet Switches that can serve multiple purposes:
- Allow multiple virtual Ethernet adapters to share a single host adapter
- Assign multiple physical Ethernet adapters to a Virtual Switch for fail-over capability
- Interconnect multiple virtual Alphas in one host without the need for a physical Ethernet link.
Depending on the line load and the capacity of the host links, many virtual Ethernet adapters can share a single host connection.
Creating Virtual Switches, adding/removing host adapters and managing these things can be simply done from the Toolbox/Network tab in vtMonitor.
Contact us when you want to learn more about this feature.
With version 2.4 vtAlpha gets stronger in two different ways:
– performance increase (appr. 30%)
– the full implementation of virtual FibreChannel support.
You can now connect virtual Alpha’s with a FibreChannel SAN. The principle is simple: first we added support for FibreChannel (hardware) adapters to the vtAlpha host environment (vtAlpha v2.3), allowing you to connect the vtAlpha host to the FibreChannel SAN. As the next step we created the virtual FibreChannel adapter (KGPSA) that you can add to the virtual Alpha configurations you are using.
Image 1 shows the vtAlpha FibreChannel architecture and the capabilities it offers. You have vtAlpha changing your x86 system into an Alpha environment, where in this case you have two virtual Alpha’s running, a virtual ES40 and a virtual AlphaServer 4000. Both virtual Alpha’s have (virtual) KGPSA FibreChannel storage adapters included, like you would have in a hardware Alpha (visualized by the physical DS25 at the right hand side).
vtAlpha includes the drivers that handle the traffic with the FibreChannel adapters (FCA) in the vtAlpha host. Which on their turn are connected to a FibreChannel switch that interconnects all FibreChannel elements in your company storage architecture.
This setup leaves all options open for you, from only using the company SAN as a storage provider up to more complex Clusters based on FibreChannel. The latter you can (continue to) organize from your OpenVMS or Tru64 environment.
Image 1 could present a FibreChannel Cluster between two virtual and one physical Alpha (or Integrity, if you like). Or it could be three independent Alpha’s, connected to the Company SAN. Or anything in between.
With the full virtual FibreChannel adapter implementation vtAlpha stands out from all other solutions in the market. vtAlpha does not require any special (and expensive) hardware for the host computer, or a special precautions at the software side.
This is more work for our developers, but it is easier and better for the customers. And a lot less expensive too.
Want to know more? Let us know and click here
The idea of replacing an AlphaServer by a virtual Alpha running on a modern and more common host computer is welcomed by most IT managers. The concept of computer virtualization is a functional and financial very attractive solution. The main advantages are that Alpha virtualization is a very quick and inexpensive way to move your existing applications to a newer platform.
It lets you prolong the lifetime of valuable and important applications by replacing the supporting hardware platform. Not having to change your delicate and expensive software is a very important benefit.
The importance of their applications makes people very wary when they hear that potential solutions run on a foreign operating system like Windows or sometimes Linux. The main concerns focus around security and reliability.
Alphas and VAXes are known to run uninterrupted for years in a row, so their successor faces the same expectations. A foreign host operating system is a reliability risk since the virtual Alpha has no control over it. Changes made to the host operating system are outside the scope and influence of the virtual Alpha. Bug-fix or service pack updates of these host operating systems sometimes cause compatibility problems with the execution of the virtual Alpha. This can result in undesired down-time for the virtual Alpha system(s).
vtAlpha addresses these concerns by running the Alpha virtualization native on a standard x86-type host.
Bare Metal Approach
vtAlpha can run directly on the x86 host. The product includes a Host Hardware Manager that supports a broad range of peripheral devices. This ensures the support of most available x86 related peripherals.
It is an x86-based Alpha, a unique proposition.
vtAlpha also runs on virtual machines. Virtual machines are increasingly becoming the IT infrastructure of choice with our potential users, therefore our solution is designed to support that environment.
In fact vtAlpha has the broadest range of host system support available:
- It will run directly on the physical host hardware
- It will run on virtual machines
Read more about the vtAlpha Bare Metal capability on the website.
When replacing your physical Alpha by its virtual equivalent in vtAlpha you will cut down your energy bill quite some since the Alpha computers were not exactly ‘Green Machines’. You can cut the energy bill even more by combining multiple virtual Alpha’s on a single host system.
To further cut down the energy consumption we developed the vtAlpha Eco App (Energy Conservation Application).
The vtAlpha Eco App (freeware) detects inactivity in the virtual Alpha CPU-usage and releases the host CPU(s) when this is the case. This downsizes the energy consumption (power, fans, cooling, heat dissipation) a great deal. Running the Eco App has no negative side effects and we recommend to install and activate it at all times.
Other virtual Alpha products run the Host CPU at full throttle, consuming lots of energy and wearing down the physical host fast, forcing early replacement. Using the Eco App on vtAlpha prevents this from happening.
The installation and activation method depends on the type and version of the guest operating system (OpenVMS/Tru64). For Tru64 v5 installations the Eco App can be activated by executing the ‘set ecoapp‘ command in console mode. For OpenVMS we developed a client package that needs to be installed in OpenVMS. A similar client for pre-v5 Tru64 versions will become available in the near future.
Ask your vtAlpha provider for the vtAlpha Eco App or contact our support people for more details.
Welcome to the Virtualization Weblog (Vlog) that we will maintain on our site.
With the help of this Vlog we want to keep you abreast of all kind of news related to the world of Alpha and VAX virtualization we operate in.
We will publish relevant articles or share articles we are aware of with you. But foremost we would like to use this Vlog as one of the ways to communicate with you.
Learn from your feedback and use it to improve ourselves.
We are looking forward to meet you on this Vlog.
The AVTware Team