AVTware version 3.2 available

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 at OpenVMS and Tru64 events

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.

vtAlpha version 3 available

This week we released version 3 of our Alpha and VAX virtualization product. Version 3 contains mainly updates at the vtAlpha side, like increased CPU performance by assigning more resources for Alpha virtualization.

vtAlpha now covers the full range of Alpha computer products, up to the Enterprise Class AlphaServer GS320.

Also added are the virtual equivalents of the EI1000 and DEGXA Gigabit Ethernet adapters that can be found in these bigger Alpha systems.

In version 3 we also introduce a new back-plane for the virtual AlphaServer 2000 and 4000 models to support older OpenVMS and Tru64 releases.

The vtMonitor management interface was modernized as well to support the new functions and reflect the importance of the changes in version 3.

For more information contact your local vtAlpha and vtVAX representative, they will be happy to update you about all the new features.

Virtualizing Alphas without stopping VMS

We recently completed a project to virtualize a large number of AlphaServers which for us is business as usual. However, during the virtualization process they had to be relocated to another site. And all without stopping the applications.

The virtualization was routine, but the non-stop aspect was kind of special. This is how we did it:

The starting point was to replace a number of ES45 clusters in the various regional offices of the customer. They wanted to get rid of the old Alpha hardware and move to more modern and standard equipment (x86). There are only two ways to do that: software migration or Alpha virtualization. First they explored the migration option, which caused major stomach-pains across the board. Virtualization was a much more elegant and less complicated way to achieve their goals.

They looked at the alternatives available and decided for vtAlpha: reliable, secure and fast. With HPE ProLiant Blade systems and 3PAR storage as host hardware. vtAlpha hides the architectural differences of the new host environment from the existing Alpha based software. This way they could use a modern 3PAR SAN, even though that isn’t supported by their OpenVMS version.

From big Alpha to smaller X86 with vtAlpha

As mentioned, the virtualization part is easy: install vtAlpha, copy the Alpha disk content to the new hosts, boot from the copied disks and continue to work. However, the regional systems were to be relocated to sites that were about 30 – 50 miles away and everything had to be done without stopping the applications. The customer operation had to continue, a non-stop transition!

The combination of vtAlpha and OpenVMS clustering allowed us to pull this off.

First, we installed vtAlpha on the (centralized) host system and created virtual equivalents of the AlphaServers to replace. Next we set up a (long-distance) network and FibreChannel link to marry the regional AlphaServers with the central virtual Alpha(s) in a cluster. The OpenVMS shadowing ensured the data was synchronized to the vtAlpha systems. When all data was duplicated, the regional cluster members were turned off and the vtAlpha cluster continued the operation.

We used HPE Fibre Channel over IP devices to ensure high data transfer speed levels during the shadowing operation, to avoid that user access during that operation would become sluggish because of the distance/latency. After all, an OpenVMS shadow disk operation is only completed when fully executed on all shadowset members, including the ones far, far away.

After some careful planning it was a smooth transition process that we managed to repeat for all the regional offices. The customer is currently running their operation of a fully virtualized vtAlpha environment without any problems. Another happy vtAlpha customer.

Contact us when you like to hear more about this kind of virtualization projects.

vtAlpha and vtVAX version 2.11 available

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.

VMware Certified

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.

VMware CertifiedSo 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

AVT VMSbook: OpenVMS on X86

AlphabookRemember the Alphabook that was released by Tadpole in 1996? The first OpenVMS Notebook, meant for the military market?

A great accomplishment at that time, hope for the future of VMS.
A ruggedized, heavy piece of equipment, (under)powered by an Alpha 21066 chip ( 233 Mhz), 128 MB memory and 1 GB disk.

Great at that time, but massively expensive so it didn’t really fly.

However, with vtAlpha you can make a laptop running OpenVMS only. After pressing the power button it opens up in the VMS session manager where you can log into VMS. How about that?

There is probably not a large market for it (Notebook, vtAlpha and OpenVMS licenses add up to quite a bill). OpenVMS developers who like to have such a gem probably don’t have the money for it.

However it could be done, so we did it, as a Proof of Concept. Not really a product but just for fun. An ordinary HP laptop, with vtAlpha installed and OpenVMS with hobbyist license.


It is on display at the OpenVMS Boot Camp 2015, Sept 28 – 30, Nashua

Visit us in the central Boot Camp Lounge and see for yourself.

VMSbook: the OpenVMS laptop

A wish of many OpenVMS users is to have a notebook that boots VMS instead of Windows/Linux. Something like that would be really great. Alphabook came the closest, but that product no longer exists. Besides it was heavy and  expensive.

Being present at the OpenVMS Boot Camp we decided to create just that and make it a prize at the Roundhouse dinner for one of the participants to win. We took a run-of-the-mill HP notebook, removed the Windows software and installed the vtAlpha product instead. We put OpenVMS 8.4 on it with a hobbyist license and configured it to boot up in the X-Windows screen for VMS.

Voila: your one and only personal VMSbook.

VMSbook winner Bootcamp 2014

We had it on display during the bootcamp and it drew a crowd. People really wanted to participate in the raffle because they could win this thing.

But there could be only one of course.

Contact us if you want to know more about this.


iSCSI and vtAlpha/vtVAX

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.

AVTware lets OpenVMS and Tru64 connect to iSCSI and other modern storage

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.

vtAlpha/vtVAX v2.9

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.

VLAN for Alpha and VAX

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.

Display of VLAN in vtAlpha

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.

VirtualBox support

vtAlpha/vtVAX supports the most frequently used Virtual Machine products: VMware, KVM, Xen and Hyper-V. Recently we received inquiries about the Oracle product VirtualBox for Windows, mainly from people who like to run vtAlpha on the Windows notebook they carry around. So, not for real production, just nice to have.

VirtualBox currently lacks support for an operation that is used by virtual Alpha’s. Fortunately there is a fix available that can be applied to VirtualBox, so you can run virtual Alpha’s in that environment too.

For VirtualBox in Windows, open a command window (cmd), go to the directory VirtualBox is installed in (e.g. cd \Program Files\Oracle\VirtualBox) and enter the following command:

VBoxManage setextradata global VBoxInternal/CPUM/CMPXCHG16B 1

That fixes the issue and from now on you should be able to run your virtual Alpha’s in that VM environment too.

Mix vtAlpha and vtVAX on the same host

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.

Mixed vtVAX and vtAlpha Bare Metal

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

OpenVMS and Tru64 Live Host Migration

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.

Springtime, the birth of a new vtAlpha version

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.


Portable Alpha in the news

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.

vtAlpha Prize winner Bootcamp 2013

Congratulations David!!

Tru64 Clustering with vtAlpha

Tru64OpenVMS clustering was already included in vtAlpha from the early beginning and with version 2.6 TruCluster support (Tru64 clustering) is added.

vtAlpha TruCluster support allows moving all Tru64 installations to a modern X86 host platform and form a cluster.  Modern storage products (e.g. 3PAR) are supported, without your Tru64 based software knowing about it. Upgrade your storage to the latest level!

vtAlpha supports clustering via  FibreChannel, SCSI and logical disks. Implementation examples:

  • Replacing a hardware Alpha in a running multi-node FibreChannel based cluster.  Mixed Cluster of physical and virtual Alphas
  • Replacing a Alpha cluster by a virtual equivalent running on HP Proliants.

When you would like to learn more about this we invite you to let us know (contact request page) so we can follow up on your request.

vtAlpha: a Green Machine

Aside from being a quick and easy way to prolong the life time of your Alpha applications, applying vtAlpha can be a serious contribution to lowering your energy consumption.

We ran a energy consumption measurement between an AlphaServer of average size and its vtAlpha equivalent. The results were significant.

A four CPU Alpha Server consumed 630 Watts. Its vtAlpha equivalent consumed only 230 Watts. 60% less energy consumption by using vtAlpha!

When you combine two of these Alpha’s on a single host, power consumption will drop from 1260 Watt to 290: 75% less!

Also, the energy candle burns on two ends: power consumption results in heat dissipation, which you have to cool down again, so the gain is x 2. When you have Green Goals to achieve vtAlpha will certainly help you.

And there is more.

We have developed the Eco App, allowing vtAlpha to cut energy consumption even further. Eco App shaves another 25% of your energy consumption. It is packaged with vtAlpha, you only have to add it to OpenVMS or activate it in a Tru64 installation. There are no downsides for its use, no performance loss or anything else, so we recommend to always activate it.

Green Machine

Please check your vtAlpha documentation, your vtAlpha support person, or ask us to contact you.


vtAlpha grows the Tru64 and OpenVMS installed base

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.

vtAlpha Virtual Network Switch

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.

vtAlpha, now with extra Fibre

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.

FibreChannel image

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

Alpha Security Matters

The Alpha computer was considered more secure and reliable than other environments. For this reason potential customers frowned upon running a virtual Alpha on top of a foreign operating system like Windows or Linux. This is perceived as not reliable/secure enough because the virtual Alpha running on it has in fact no control over that foreign environment.

To maintain the high level of reliability and security of the Alpha computers we designed vtAlpha from the ground up to control the host hardware itself. We refer to this as Bare Metal Installation. This is of course a lot more work for the developer but in the end of the day the results are much better for the customer.

Bare metal

AVTware includes the Operating System Functions and Peripheral Drivers and it fully controls the host environment it runs on. This is important to avoid the security holes of any underlying Operating System.

With AVTware Bare Metal the virtual Alpha itself is well protected, but since it runs in a company network we made sure other inroads are well secured too.

For example the network traffic that allows managing the virtual Alpha configurations as well as the host environment they run in (hardware, storage, network) needs to be protected as well.

By default vtAlpha opens up the following network ports only:

22350 vtAlpha license key
Which you can expand by enabling the following capabilities (disabled by default):
21 FTP
22 SSH
139/445 SMB (files sharing)

Use FTP and SMB wisely, having them active at all times is in fact a potential security risk.

vtAlpha offers extra protection for your console lines (OPA0). The management tool (vtMonitor) is only accessible via user-id/password. Everything is safeguarded by the highest levels of encryption of course. For good security you should always use HTTPS to handle the remote management via vtMonitor, to secure the information exchange between the system manager and the vtAlpha host system.

Contact us when you like to know more about this subject.

Alpha and VAX Blade systems

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.Alpha and VAX Blade

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.

6 Tips for a smooth vtAlpha installation on VMware

Installing vtAlpha on a Virtual Machine host (VMware, KVM, Hyper-V, Xen) requires some extra attention. You have to deal with VM defaults and organizational procedures that are in place. This list helps you to plan ahead and clear obstacles prior to the installation day.

  1. Define sufficient memory. VMware’s default for the virtual machine is 384 MB. vtAlpha requires the size of the virtual Alpha memory +25% + 1 GB.
  2. Virtual CPU definition. Every virtual Alpha CPU needs one host CPU + some overhead. As a rule of thumb we recommend to multiply the number of virtual Alpha CPU’s by 1.5 (and round upwards).
  3. Use DVD for installation. vtAlpha can be installed from DVD or USB stick, but not all virtual machine products or versions support USB. Booting a virtual machine from a USB-stick is often prohibited at all. Therefore we recommend to use DVD or an .iso image of that DVD to connect to the virtual machine and boot from that virtual DVD device. When using an iso-image make sure to deactivate the “connect to DVD at power on” or switch the VM settings back to physical DVD connect after installation, otherwise it will start the installation cycle again at next boot
  4. Ensure you have N+1 Ethernet adapters available in your virtual machine.  N for the number of adapters you need in your virtual Alpha(s) and 1 extra to manage the vtAlpha host.
  5. Preparation meetings. Other than installing on a physical machine where you are in more direct control of the host system and have direct access to it, virtual machine environments require more careful planning and preparation. You have likely no access to the physical host of the virtual machine and you have to honor the (sometimes very strict) policies and procedures regarding network access and authorizations. We recommend to discuss the vtAlpha installation and requirements with the virtual machine managers before installation.
  6. Ensure you have defined sufficient storage space: 20 GB + amount of GB for the data from the physical Alpha(s). Create a separate 20 GB disk wherein you install vtAlpha and keep it separate from your data disks. This way you can always upgrade or reinstall vtAlpha without affecting the Alpha data storage.

These suggestions also apply for vtAlpha installations on other Virtual Machine products.

We welcome other recommendations that make life easier.

The AVTware team.