From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../target_missing/host_missing/accel_missing/2086 | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/2086 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2086') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 new file mode 100644 index 000000000..ca7f72291 --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2086 @@ -0,0 +1,15 @@ +qemu-img created VMDK files lead to "Unsupported or invalid disk type 7" on ESXi +Description of problem: +Trying to start the VM using vmdk converted with qemu-img fails with + +Failed to start the virtual machine. +Module DevicePowerOn power on failed. +Unable to create virtual SCSI device for scsi0:1, '/vmfs/volumes/5cca0155-bdddf31d-2714-00215acbeb1e/AppD-VM01/AppDdisk1-VM01.vmdk' +Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported. +Steps to reproduce: +1. Convert booting OS (in both Qemu and VMWare with the help of drivers) to vmdk +2. Push vmdk file to ESXi datastore +3. Try to boot +![image](/uploads/68bea874d75b1a8f6ad7f89f28feb176/image.png) +Additional information: +ESXi seem to use a specific implementation of vmdk, with a *name*.vmdk file being the descriptor of the virtual disk and a *name*-flat.vmdk. -- cgit 1.4.1