Version 3.2 of vtAlpha/vtVAX virtualization solution offers the following enhancements:
- Start-up of a virtual Alpha stops when detected that one of the configured console port-numbers is already allocated by another emulator.
- Virtual tapes for vtAlpha now supports the use of sub-directories
- MOP v3 and MOP v4 network boot now supported in vtAlpha
- Allocation of JIT-pages by vtAlpha is now completely auto-tuned, manual option is eliminated
- Virtual tape autoload and tape format options added in TapeMGR for vtVAX
- Latest security updates applied
- Full HTTPS access implemented
- Embedded webserver now refuses DES ciphers
- Support for LK463 French keyboard added
Ask your personal virtual Alpha and VAX expertise center for more information or contact us directly.
AVTware supports and joins the various OpenVMS en HPE related events across the globe.
We have been sponsoring the OpenVMS Bootcamp in Westford, Massachussetts:
participated in Oracle Tech Forums throughout USA, Europe and Australia;
as well as HPE Discover in Madrid:
Here we meet with Alpha and VAX owners, to help them protect their valuable OpenVMS and Tru64 applications.
When you like to hear more about the options we provide to prolong the life-time of your openVMS and Tru64 software, contact one of our local vtAlpha and vtVAX representatives close to you.
Release 2.11 offers the following new features:
- Virtual Fibre Channel Adapters allow the sharing of physical Fibre Channel adapters in the Host computer. Virtual Zoning supported.
- vtAlpha/vtVAX installable and bootable from SAN, allows diskless host systems.
- Support of the EI1000 Gigabit Ethernet adapter in vtAlpha.
- Asian Character Support for virtual AlphaStations (Chinese, Japanese, Korean fonts).
- Management of network License Servers added to the vtMonitor management tool.
- Dynamic volume expansion added to the management interface.
Contact us for more information about these new features.
From the early beginning vtAlpha and vtVAX were installable directly on the X86 hardware (Bare Metal), which was a great benefit of this product set. Using the included hypervisor vtServer it was possible to run multiple virtual Alphas and VAXes in parallel on that X86 host.
Support for Virtual Machine installations was also available. VMware, Hyper-V, KVM and Xen are the most popular ones. Our virtual Alpha and VAX products run well on these virtual host infrastructures.
One of our prospects asked if we were VMware certified. Since we didn’t even know such a thing existed we weren’t. So we applied, went through the procedures VMware has in place for this and obtained this certification without a problem.
So from now on we can proudly say: vtAlpha, vtVAX and vtServer are all VMware certified. We made no changes to the products, we only got the certification.
Find more about this here: OpenVMS and Tru64 on X86
iSCSI is a popular protocol to connect storage across the company LAN, creating a distributed storage infrastructure. vtAlpha and vtVAX already support SAN and NFS network based storage and has embedded iSCSI into its Bare Metal product.
No need to add extra software, everything you want is included in the product. You only have to identify the iSCSI targets that you want to connect to your virtual Alphas and VAXes making the network storage elements available to your virtual machines.
Your virtual Alpha and VAX do not need to be aware of all the modern types of storage. They still think they use MSCP, DSSI, SCSI or MSA/EVA, while in fact their files are stored on local disks of any kind or somewhere in the company network using SAN, NFS or iSCSI.
Let us know when you want to learn more about this capability.
Version 2.9 (released July 7, 2014) includes quite a few interesting new features, the most important items summarized here:
- vtVAX can now replace 5 and 6 CPU VAX6000 and VAX7000 systems, addressing the very high end segment of the VAX replacement market
- vtVAX already performed factors faster than the original VAX hardware, this version adds even more virtual CPU performance
- vtAlpha increased its Floating Point performance and added the DE600 Ethernet adapter to its virtual adapter list (= EIx device in OpenVMS).
- FibreChannel storage was already supported, this version adds autosensing of changes in a FibreChannel storage infrastructure. Adding and removing of devices is automatically detected and instantly available for the running virtual Alpha and VAX instances without having to stop/start them.
- Support for iSCSI storage is added in this version. Your virtual Alpha and VAX can use local storage of any kind of network based storage (NFS, SAN, iSCSI).
- vtAlpha resource monitoring. When a virtual Alpha frequently exhausts the CPU or memory resources it has available, the system manager is notified. Now more host resources can be allocated to ensure the virtual Alpha can work at the maximum speed.
- Multiple DNS servers. Support for up to 3 DNS addresses is included in this new version for maximum flexibility.
There are many more smaller improvements included in this release. If you want to know more about that, contact your local vtAlpha/vtVAX reseller. They will be happy to give you the information you need.
Or send us an email.
Virtual LAN (VLAN) is not something you will directly associate with Alpha and VAX systems, but in vtAlpha and vtVAX support for VLAN is embedded in the product. Now you can simply run your Alpha and VAX communication across your company VLAN infrastructure.
A VLAN carves up your physical network into multiple Virtual LANs. Each VLAN can run in parallel across the same physical infrastructure, remaining logically separated. Your OpenVMS or Tru64 software does not have to be made aware or suited to support this new technology, AVTware takes care of that for you.
For your software the network link remains a network link, regardless how it is physically organized.
And no extra software needs to be installed, just add a VLAN to your network link with the help of the vtMonitor management tool. You can now use that VLAN in your virtual Alpha or VAX configuration, easy does it.
Contact us when you want to hear more about this capability.
vtAlpha and vtVAX are created/supported by AVTware and Vere Technologies who work in close unison to bring virtualization to OpenVMS and Tru64 users to prolong the lifetime of their software.
vtAlpha started as Bare Metal, running Alpha virtualization without the need of a pre-installed operating system like Windows. vtVAX was originally developed on Windows since there was a high demand for that environment. Now vtVAX is also available in a Bare Metal version, able to run side-by-side with vtAlpha on the same host computer. The vtVAX Windows version remains available, updated and supported.
(click on the image to get a larger picture)
This image shows the vtMonitor management interface running a virtual Alpha DS10 and a VAX 4000-105 (marked green in the left hand pane) together on the same host system. The console on the right shows the VAX4000, the left one the DS10.
This shows that the vtVAX and vtAlpha products provide the best integration of virtual VAX and Alpha in the market.
Follow us on Twitter, Facebook or website to stay abreast of the latest developments in Alpha and VAX virtualization. Or contact us for more information.
During the HP event in Vienna I attended a presentation about HP’s project Odyssey and that looked like a very interesting development to me, especially for the owners of Tru64 and the older OpenVMS systems.
In fact this is a blade concept, supporting Itanium and Intel Xeon processor based blade boards that will be seamlessly integrated in one box.
“And what does that bring me?” you might say as owner of one of these retired Alpha or VAX systems.
When you consider the combination with vtAlpha and vtVAX it can bring you a lot. Your current Alpha and VAX-based systems got a more and more isolated position due to the retired status of that hardware, but now they can be brought back in a recent and company wide platform, without changing your software.
vtAlpha and vtVAX are thin layers on top of an x86 based host computer creating an Alpha or VAX environment wherein you can run the virtual equivalent of your hardware Alpha or VAX system.
It are actually Alpha and VAX hypervisors (or Virtual Machine Managers, if you like) creating multiple Alpha and VAX systems on top of the x86 host. And that x86-host can now be part of the Odyssey infrastructure.
This means that with project Odyssey and vtAlpha/vtVAX you can reunite your older OpenVMS and Tru64 systems with your other, more current Itanium-based, HP-UX, Linux, Non-stop and Integrity/VMS systems on the same platform.
Odyssey, Hypervisors, Virtualization, no this is not an episode of Star Trek. It is a real opportunity to update your retired Alpha and VAX installation to a more modern platform and (re-)combine it with the rest of your IT-infrastructure, with little effort.
Time to beam-up your existing Alpha or VAX installation?
We like to hear your opinion about this subject, Contact us.