Unable to import custom VMDK into Google Cloud
msh.deve...@gmail.com
I am trying to import a Red Hat 6 VMDK into Google Cloud. The documentation is straightforward and it appears to be working up until it is attempting to resize a "temp translation disk".
Specifically, is a Red Hat 6 VMDK Distribution, which is 64GB and is hosted in Google Cloud Storage. The account is a paid account and is also not on a trial basis, so if there were any trial restrictions, they shouldn't be there at this point.
Here is the command I run:
gcloud compute images import mshprs --source-file gs://mbucket/MY-VM-DISK.vmdk --os rhel-6The VM is copied, as expected, to the Google Cloud project instance and then I get the following error:
Daisy] Errors in one or more workflows:
import-and-translate: step "import" run error: step "wait-for-signal" run error: WaitForInstancesSignal FailureMatch found for "inst-importer-import-and-translate-import-nq26b": "ImportFailed: Failed to resize temp-translation-disk-nq26b to 237GB in projects/71352554514/zones/us-central1-f'"
ERROR
ERROR: build step 0 "gcr.io/compute-image-tools/daisy:release" failed: exit status 1I have not been able to get past this step even if after attempting to allocate it to different regions or simply try again.
Shan Kulandaivel
--
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/e992112b-2b55-4911-8d68-fc905ba918d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Mehdi (Cloud Platform Support)
On Wednesday, April 17, 2019 at 3:28:06 PM UTC-4, Shan Kulandaivel wrote:
I'll follow up with you offline to collect additional details so that we can investigate further. I'll post the resolution to the group for future reference.thanks
On Tue, Apr 16, 2019 at 11:50 AM <msh.deve...@gmail.com> wrote:
--I am trying to import a Red Hat 6 VMDK into Google Cloud. The documentation is straightforward and it appears to be working up until it is attempting to resize a "temp translation disk".
Specifically, is a Red Hat 6 VMDK Distribution, which is 64GB and is hosted in Google Cloud Storage. The account is a paid account and is also not on a trial basis, so if there were any trial restrictions, they shouldn't be there at this point.
Here is the command I run:
gcloud compute images import mshprs --source-file gs://mbucket/MY-VM-DISK.vmdk --os rhel-6
The VM is copied, as expected, to the Google Cloud project instance and then I get the following error:
Daisy] Errors in one or more workflows: import-and-translate: step "import" run error: step "wait-for-signal" run error: WaitForInstancesSignal FailureMatch found for "inst-importer-import-and-translate-import-nq26b": "ImportFailed: Failed to resize temp-translation-disk-nq26b to 237GB in projects/71352554514/zones/us-central1-f'" ERROR ERROR: build step 0 "gcr.io/compute-image-tools/daisy:release" failed: exit status 1
I have not been able to get past this step even if after attempting to allocate it to different regions or simply try again.
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.
Abhijit Roy
gcloud compute instances import cmr-instance --source-uri=gs://cmr-ova/ramr-9.6.2004.108.ova --os centos-6
[import-ovf]: 2020-05-27T23:39:20Z Error running workflow: step "translate" run error: step "translate-disk" run error: step "wait-for-translator" run error: WaitForInstancesSignal FailureMatch found for "inst-translator-import-ovf-translate-translate-disk-48430": "TranslateFailed: error: Verify that you have specified the correct operating system in the `--os` flag. If you are bringing your own license (BYOL), also verify that your subscription is eligible to be run on GCP."
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> detected_major_version:6
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> detected_minor_version:10
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> target-size-gb:100
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> source-size-gb:3
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> import-file-format:vmdk
[import-ovf]: 2020-05-27T23:39:20Z Serial-output value -> detected_distro:centos
On Friday, April 19, 2019 at 1:35:13 PM UTC-7, Mehdi (Cloud Platform Support) wrote:
Hello ,Thank you for posting this import issue here.First, please check if the virtual disk meet all the requisites to be imported. You have all the details in this documentation [1]. You can also use this Image Import Precheck Tool [2].If the previous verifications are all well, have a look at you disk quota [3] to see if you still have available disk quotas.Regards,Mehdi
On Wednesday, April 17, 2019 at 3:28:06 PM UTC-4, Shan Kulandaivel wrote:
I'll follow up with you offline to collect additional details so that we can investigate further. I'll post the resolution to the group for future reference.thanks
On Tue, Apr 16, 2019 at 11:50 AM <msh.dev...@gmail.com> wrote:
--I am trying to import a Red Hat 6 VMDK into Google Cloud. The documentation is straightforward and it appears to be working up until it is attempting to resize a "temp translation disk".
Specifically, is a Red Hat 6 VMDK Distribution, which is 64GB and is hosted in Google Cloud Storage. The account is a paid account and is also not on a trial basis, so if there were any trial restrictions, they shouldn't be there at this point.
Here is the command I run:
gcloud compute images import mshprs --source-file gs://mbucket/MY-VM-DISK.vmdk --os rhel-6
The VM is copied, as expected, to the Google Cloud project instance and then I get the following error:
Daisy] Errors in one or more workflows: import-and-translate: step "import" run error: step "wait-for-signal" run error: WaitForInstancesSignal FailureMatch found for "inst-importer-import-and-translate-import-nq26b": "ImportFailed: Failed to resize temp-translation-disk-nq26b to 237GB in projects/71352554514/zones/us-central1-f'" ERROR ERROR: build step 0 "gcr.io/compute-image-tools/daisy:release" failed: exit status 1
I have not been able to get past this step even if after attempting to allocate it to different regions or simply try again.
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-dis...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.
Md Mahboob Sayeed Khan
Hello Abhijit,
As per the error message, it looks like the import is having issues with translating the image. Please also look into the serial console if you noticed any packages are failing to install. There is a workaround using that we can avoid those errors by running the import command specifying the flag "--no-guest-environment" and then install the packages manually. However, this is only an hypothesis since I can not do the tests with the exact OVA file that you want to import. Additionally, there is a tool called “Image Import Precheck Tool” [1] that attempts to identify compatibility issues that will either cause import to fail or will cause potentially unexpected behavior post-import.
As a next step, I would suggest trying the Image Import Precheck Tool commented above, and if there are no issues with the OVA file, run the import command with the flag “--no-guest-environment” [2][3]. Adding the --no-guest-environment flag to your import command might avoid some unexpected errors.
Thanks
Mahboob
[1] https://github.com/GoogleCloudPlatform/compute-image-tools/tree/master/cli_tools/import_precheck/
[2] https://cloud.google.com/sdk/gcloud/reference/compute/images/import#GCLOUD-WIDE-FLAGS
[3] https://cloud.google.com/compute/docs/images/guest-environment
Abhijit Roy
gcloud compute instances import cmr-instance --source-uri=gs://cmr-ova/ramr-9.6.2004.108.ova --os centos-6 --no-guest-environment
[import-ovf] 2020-05-28T22:49:24Z step "translate" run error: step "translate-disk" run error: step "wait-for-translator" run error: WaitForInstancesSignal FailureMatch found for "inst-translator-import-ovf-translate-translate-disk-b3m95": "TranslateFailed: error: command: I: Executing /sbin/dracut -v -f 2.6.32-696.23.1.el6smp"
Hasanul Murad
Abhijit Roy
gcloud compute instances import cmr-instance --source-uri=gs://cmr-ova/image.ova --os centos-6 --no-guest-environment --verbosity=debug
[import-ovf]: 2020-06-04T03:08:34Z Error running workflow: step "translate" run error: step "translate-disk" run error: step "wait-for-translator" run error: WaitForInstancesSignal FailureMatch found for "inst-translator-import-ovf-translate-translate-disk-z2z7p": "TranslateFailed: error: command: I: Executing /sbin/dracut -v -f 2.6.32-696.23.1.el6smp"
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> target-size-gb:100
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> source-size-gb:4
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> import-file-format:vmdk
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> detected_distro:centos
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> detected_major_version:6
[import-ovf]: 2020-06-04T03:08:34Z Serial-output value -> detected_minor_version:10
[import-ovf]: 2020-06-04T03:08:34Z Workflow "import-ovf" cleaning up (this may take up to 2 minutes).
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: Reading GCS logfile: 416 (no new content; keep polling)
DEBUG: Reading GCS logfile: 206 (read 1481 bytes)
[import-ovf]: 2020-06-04T03:09:17Z Workflow "import-ovf" finished cleanup.
[import-ovf] 2020-06-04T03:09:17Z step "translate" run error: step "translate-disk" run error: step "wait-for-translator" run error: WaitForInstancesSignal FailureMatch found for "inst-translator-import-ovf-translate-translate-disk-z2z7p": "TranslateFailed: error: command: I: Executing /sbin/dracut -v -f 2.6.32-696.23.1.el6smp"
[import-ovf] 2020-06-04T03:09:17Z Cleaning up.
[import-ovf] 2020/06/04 03:09:17 Deleting content of: gs://switchmobility-ovf-import-bkt-us-central1/ovf-import-tvlv3/ovf/
[import-ovf] 2020-06-04T03:09:18Z Deleting gs://switchmobility-ovf-import-bkt-us-central1/ovf-import-tvlv3/ovf/image-disk1.vmdk
[import-ovf] 2020-06-04T03:09:18Z Deleting gs://switchmobility-ovf-import-bkt-us-central1/ovf-import-tvlv3/ovf/image.mf
[import-ovf] 2020-06-04T03:09:18Z Deleting gs://switchmobility-ovf-import-bkt-us-central1/ovf-import-tvlv3/ovf/image.ovf
[import-ovf] 2020/06/04 03:09:18 step "translate" run error: step "translate-disk" run error: step "wait-for-translator" run error: WaitForInstancesSignal FailureMatch found for "inst-translator-import-ovf-translate-translate-disk-z2z7p": "TranslateFailed: error: command: I: Executing /sbin/dracut -v -f 2.6.32-696.23.1.el6smp"
ERROR
ERROR: build step 0 "gcr.io/compute-image-tools/gce_ovf_import:release" failed: step exited with non-zero status: 1
DEBUG: (gcloud.compute.instances.import) build d2dd3a25-cfe9-42a2-aa57-a94254525b6e completed with status "FAILURE"
Traceback (most recent call last):
File "/Users/aroy/y/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", line 983, in Execute
resources = calliope_command.Run(cli=self, args=args)
File "/Users/aroy/y/google-cloud-sdk/lib/googlecloudsdk/calliope/backend.py", line 807, in Run
resources = command_instance.Run(args)
File "/Users/aroy/y/google-cloud-sdk/lib/surface/compute/instances/import.py", line 172, in Run
hostname=getattr(args, 'hostname', None)
File "/Users/aroy/y/google-cloud-sdk/lib/googlecloudsdk/api_lib/compute/daisy_utils.py", line 761, in RunOVFImportBuild
backoff=backoff)
File "/Users/aroy/y/google-cloud-sdk/lib/googlecloudsdk/api_lib/compute/daisy_utils.py", line 661, in _RunCloudBuild
raise FailedBuildException(build)
FailedBuildException: build d2dd3a25-cfe9-42a2-aa57-a94254525b6e completed with status "FAILURE"
ERROR: (gcloud.compute.instances.import) build d2dd3a25-cfe9-42a2-aa57-a94254525b6e completed with status "FAILURE"
Anthony Leo
- Virtual disks must be in VMDK or VHD formats.
- Virtual disks must be configured with MBR boot. UEFI is not supported.
- Virtual disks must not be encrypted.
- To verify that your VM meets the requirements, you can run the pre-check tool as it can provided useful information when debugging any issues you may encounter.
- For all Windows operating systems, PowerShell version 3 or later must be installed. PowerShell versions earlier than 3.0 can cause issues with the startup and shutdown scripts used during the import process.
- For all Linux distributions, the boot disk must have GRUB installed.
- The OVF files must provide Level 1 portability as described in the OVF specification document. Virtual appliances that meet Level 2 portability can be imported, but any custom extensions such as source hypervisor-specific details are ignored during the import process.
- The OVF file must contain only one VM. If more than one VM is present, only the first VM is imported.
- The first disk in the OVF file must be bootable.
Abhijit Roy
Boot Menu
[m [4;2H+-------------------------------------------------------------------------+ [5;2H| [5;76H| [6;2H| [6;76H| [7;2H| [7;76H| [8;2H| [8;76H| [9;2H| [9;76H| [10;2H| [10;76H| [11;2H| [11;76H| [12;2H| [12;76H| [13;2H| [13;76H| [14;2H| [14;76H| [15;2H| [15;76H| [16;2H| [16;76H| [17;2H+-------------------------------------------------------------------------+ [m
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected image, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command-line. [5;78H [m [7m [5;3H raserver 9.6.2004.109 #109-rel 2020-06-02 11:14:42 x86_64 builder@smr> [5;75H [m [m [6;3H raserver 9.6.2004.109 #109-rel 2020-06-02 11:14:42 x86_64 builder@smr> [6;75H [m [m [7;3H [7;75H [m [m [8;3H [8;75H [m [m [9;3H [9;75H [m [m [10;3H [10;75H [m [m [11;3H [11;75H [m [m [12;3H [12;75H [m [m [13;3H [13;75H [m [m [14;3H [14;75H [m [m [15;3H [15;75H [m [m [16;3H [16;75H [m [16;78H [5;75H [H [J
Booting: 'raserver 9.6.2004.109 #109-rel 2020-06-02 11:14:42 x86_64 builder@smr
-build1:942673'
�Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.32-696.23.1.el6smp raserver
Call Trace:
[<ffffffff8172d640>] ? panic+0xa7/0x179
[<ffffffff8109051e>] ? vprintk_default+0xe/0x10
[<ffffffff81e5f546>] ? mount_block_root+0x216/0x2cb
[<ffffffff81002930>] ? bstat+0x200/0x8d0
[<ffffffff81e5f69b>] ? mount_root+0xa0/0xa4
[<ffffffff81e5f80f>] ? prepare_namespace+0x170/0x1a9
[<ffffffff81e5eabd>] ? kernel_init+0x2e1/0x2f7
[<ffffffff8100968b>] ? __switch_to+0x6b/0x320
[<ffffffff8173a6fa>] ? child_rip+0xa/0x30
[<ffffffff81e5e7dc>] ? kernel_init+0x0/0x2f7
[<ffffffff8173a6f0>] ? child_rip+0x0/0x30
Rebooting in 10 seconds..
ACPI MEMORY or I/O RESET_REG.
SeaBIOS (version 1.8.2-20200506_125016-google)
Total RAM Size = 0x0000000100000000 = 4096 MiB
CPUs found: 4 Max CPUs supported: 4
Comparing RSDP and RSDP
Comparing RSDT and RSDT
Comparing FACP and FACP
Comparing FACS and FACS
return 0 for FACS vs FACS: SUCCESS
Comparing DSDT and DSDT
return 0 for DSDT vs DSDT: SUCCESS
return 0 for FACP vs FACP: SUCCESS
Comparing SRAT and SRAT
Diff at 8: 3, 1
Sending ACPI diff VM event for SRAT at 8. 0x3 vs 0x1
Diff at 9: 17, 19
Sending ACPI diff VM event for SRAT at 9. 0x17 vs 0x19
return 1 for SRAT vs SRAT: MEM_CMP FAILURE
Comparing APIC and APIC
Diff at 8: 5, 1
Sending ACPI diff VM event for APIC at 8. 0x5 vs 0x1
Diff at 9: f6, fa
Sending ACPI diff VM event for APIC at 9. 0xf6 vs 0xfa
return 1 for APIC vs APIC: MEM_CMP FAILURE
Comparing SSDT and SSDT
return 0 for SSDT vs SSDT: SUCCESS
Comparing WAET and WAET
return 0 for WAET vs WAET: SUCCESS
return 1 for RSDT vs RSDT: RSDT FAILURE
return 1 for RSDP vs RSDP: RSDP FAILURE
Sending ACPI diff VM event for ERR1 at 0. 0x0 vs 0x0
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=209715200 = 102400 MiB
drive 0x000f2300: PCHS=0/0/0 translation=lba LCHS=1024/255/63 s=209715200
Sending Seabios boot VM event.
Booting from Hard Disk 0...
On Friday, June 5, 2020 at 9:00:40 AM UTC-7, Anthony Leo wrote:
Hello,Based on what other members mentioned in this thread, I can see that you have already tried specifying the -os parameter in the command. However, what you can also check is to see if you meet the requirements in order to import your VM Instance; You must meet these necessary requirements for the Source VM instance and the OVF file in order to import your instance to GCP:Source VM requirements:1. The following requirements must be met by the VM that is used to create the OVF file:
- Virtual disks must be in VMDK or VHD formats.
- Virtual disks must be configured with MBR boot. UEFI is not supported.
- Virtual disks must not be encrypted.
- To verify that your VM meets the requirements, you can run the pre-check tool as it can provided useful information when debugging any issues you may encounter.
2. The operating system for the source VM should meet the following requirements:
- For all Windows operating systems, PowerShell version 3 or later must be installed. PowerShell versions earlier than 3.0 can cause issues with the startup and shutdown scripts used during the import process.
- For all Linux distributions, the boot disk must have GRUB installed.
OVF file requirements:1. The following requirements must be met by the OVF file:
- The OVF files must provide Level 1 portability as described in the OVF specification document. Virtual appliances that meet Level 2 portability can be imported, but any custom extensions such as source hypervisor-specific details are ignored during the import process.
- The OVF file must contain only one VM. If more than one VM is present, only the first VM is imported.
- The first disk in the OVF file must be bootable.
I hope this helps!Regards,Anthony
Hasanul Murad
Hello Abhijit,
I found this community thread, which might be helpful.