I'm trying to work out a way to install teradata express on GCP compute instance or any other GCP compute service?? any leads would be appreciated.. thank you..!!
Teradata Express for VMware Player is provided as a pre-configured VMware virtual machine based on SUSE Linux Enterprise Server 11 (SLES11). It supposes VMware Player or VMware Server as an execution environment.
Inside of the downloaded package there is a VMX file. This is the primary configuration file, which stores settings chosen in the New Virtual Machine Wizard or virtual machine settings editor. See VMware: What Files Make Up a Virtual Machine?
SLES version 11 is not supported on GCE so you can't install Teradata Express on GCP "as is". See Compute Engine > Documentation > Supported operating systems
If you really need to get the Teradata Express for VMware Player working on GCE you should upgrade the SLES11 VM to SLES12 or SLES15 on VMware Player, and then import this VM into GCE.
Updating and Upgrading SUSE Linux Enterprise › Upgrading SUSE Linux Enterprise
Upgrading to SUSE® Linux Enterprise 12 > SLE11 to SLE12 Migration
While upgrading from SLES11 to SLES12 you should keep in mind that UEFI bootloaders are not supported in GCE for imported disks.
Having got Teradata Express on SLES12, you can consider two ways for import.
1. Create a new VM instance on GCE and use a pre-configured virtual disk with Teradata on SLES12 for creation of a boot disk image. The import tool supports most virtual disk file formats, including VMDK, VHD, and RAW. For more information, see Compute Engine > Documentation > Importing virtual disks.
2. Import a VM in OVF format into Compute Engine accordingly with Compute Engine > Documentation > Importing virtual appliances. The source VM could be whether in an OVF package or in an OVA single file. To convert VMware VMX to OVF or OVA you can use Open Virtualization Format Tool (ovftool). Please see OVF Tool User Guide for more details.
Both of these methods look a bit more complicated when you consider that Google provides its own data warehouse solutions: you could consider migration from Teradata to BigQuery so that use native solution provided and (what's important) supported by Google.
BigQuery Data Transfer Service > Documentation > Migrating data from Teradata
Solutions > Migrating data warehouses to BigQuery
Yes, you can run Vantage Express on GCP using nested virtualization. Here is the official how-to document: https://quickstarts.teradata.com/vantage.express.gcp.html.
Related
I wanted to test vmdk files exported from google cloud with my vmware workstation 16 pro, however it doesn't seem to work, a cursor just blinks on the screen and there is no progress after that.
To export a vmdk file from Google cloud, I followed below steps:
https://cloud.google.com/compute/docs/images/export-image#exporting_an_image
And to boot from vmdk in vmware workstation, following steps were referred.
https://kb.vmware.com/s/article/2010196
Please help to get this resolved.
This seems to be a disk fragment issue while exporting a vmdk file. Hence it didn't work in vmware. I created a fresh vm instance in gcp and did an export, then it worked.
Windows:
Now, I want to install a VMWare Workstation on the Windows Google Cloud Platform instance and next install another OS on that VMWare Workstation.
But I get this BSOD.
Linux:
Now, I want to install a VMWare Workstation on the Linux Google Cloud Platform instance and next install another OS on that VMWare Workstation.
But I get this error.
This host supports intel VT-x. but the Intel VT-x implementation is incompatible.
This host does not support Intel EPT hardware assisted MMU virtualization.
Module "CPUIDEarly" power on failed.
Failed to start the virtual machine.
How can I do it?
I agree with Martin that you may not want to run VMware workstation, but you may need nested virtualization for other stuff like VMware ESXi/qemu.
GCE VMs do support nested virtualization please see Enabling Nested Virtualization for VM Instances on how to do it. This will enable VT-x support inside the VM.
It is rather useless to install a type 2 (hosted) hypervisor inside a GCE virtual machine.
There are a) other options for VMware hosting or b) migrate these containers with Velostrata.
c) That one error message (assuming you'd go the proposed nested virtualization route) might require monitor.allowLegacyCPU = "true" in file config.ini, because it seems the CPU is not supported by VMware Workstation 14 (this at least works for some elder Intel® Xeon® CPU).
I don't have ESXi inhouse, but am building a VM for a customer and they have two environments, an ESXi5.5 deployment and a 6.7.
At the moment I'm only able to export to an OVF/OVA format, which (for my customer) has worked in their 6.7 environment as I've downloaded the (Linux) version of Workstation 15 and am wondering how on earth I get to export the VM for ESX5.5. The VMware forums and online help don't seem to have been updated for Workstation 15 as they refer to a wizard which isn't available in the version of Workstation 15 that I have (only available in the paid version?)
I've also downloaded the VMware vCenter Converter (Windows version, standalone) as I was under the impression that that would be able to do convert anything to anything and therefore do what I needed, but it will only allow me to export to a 5.5 ESXi server within my environment, which I don't have.
What I'm looking at doing is building a VM that can be used in any ESXi environment, so I guess I should ask: what really is the best tool for me to be able to do that, considering that I don't have ESXi deployed here and am using VMWare Workstation and VirtualBox.
I had hoped that OVA/OVF would be a standard, and perhaps that's correct for newer VMWare Type I hypervisors?
My assumption is that you're running into an issue where the VM of a specific hardware version cannot be imported to the 5.5 environment. Each version of vSphere has a compatible hardware version, they're listed here: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html
To downgrade an existing VM's hardware, you can manually create a new (custom) VM in Workstation and when asked for the Virtual Disk, point to the existing disks you have already created. Additional information: https://kb.vmware.com/s/article/1028019
I downloaded a VM instance from the web and launched / modified it using it using VMware Workstation 12 Player
I would now like to transfer this image onto an ESXi host running VMware ESXi Version 5.5.0.
I have tried copying the working directory "C:\Users\xxxx\Downloads\Kali-Linux-2.0.0-vm-amd64\Kali-Linux-2.0.0-vm-amd64" to the ESXi datastore and have tried to import it using a couple of methods:
I tried browsing to the Datastore, right clicking the "Kali-Linux-2.0.0-vm-amd64.vmx" file and selecting "add to inventory"
I tried creating a virtual machine, selecting the option to use and existing disk and pointed it at the VMDK file.
Both methods allow me to create the machine, but fail with the following error when I try to power it up.
Failed to start the virtual machine.
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/4dc219c6-2eb825c6-0119-d8d3855f4a40/Kali-Linux-2.0.0-vm-amd64/Kali-Linux-2.0.0-vm-amd64.vmdk' or one of the snapshot disks it depends on.
The system cannot find the file specified
VMware ESX cannot find the virtual disk "/vmfs/volumes/4dc219c6-2eb825c6-0119-d8d3855f4a40/Kali-Linux-2.0.0-vm-amd64/Kali-Linux-2.0.0-vm-amd64.vmdk". Verify the path is valid and try again.
I have checked and I can see the VMDK file on the Datastore.
I don't know if it of any significance, but the files on my desktop are broken down into multiple VMDK files and when I copied it to the Datastore, it turned them into one large VMDK file.
It might be best to use vmware converter to import the vm into your esxi host and/or even try an export to OVF from workstation and then an import (deploy OVF) to ESXi host.
From the error generated it looks like the original VM may still have some snapshots. Try and remove any snapshots, then take note of the disk controller and disk type of the workstation vm and check that it is supported for ESXi vm (for example IDE etc.), ESXi likes SCSI.
I have changed hypervisor of my openstack(Grizzly) to vmware esxi.
When I create an Ibuntu in openstack dashboard, it works well and I can see the instance in esxi, but when I created a Windows 7 instance, 'blue screen' occurs.
Most likely disk driver issues. Go to your ESXi host directly, create a new Win7 VM (No need to install Windows, just the VM creation). Check the disk controller (LSI Logic???) and compare this to the VM that is created by Openstack.