diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
| commit | 3e4c5a6261770bced301b5e74233e7866166ea5b (patch) | |
| tree | 9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_missing/host_missing/accel_missing/2532 | |
| parent | e5634e2806195bee44407853c4bf8776f7abfa4f (diff) | |
| download | qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip | |
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2532')
| -rw-r--r-- | gitlab/issues_text/target_missing/host_missing/accel_missing/2532 | 40 |
1 files changed, 0 insertions, 40 deletions
diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 deleted file mode 100644 index b8d4e440d..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/2532 +++ /dev/null @@ -1,40 +0,0 @@ -empty vmdk disk created by qemu-img cann't import to vmware ESXi or Workstation -Description of problem: -qemu-img create empty vmdk file, and can't import to vmware workstation or ESXi. the ovftool - fail. the log: - -> ``` -> 2024-08-23T11:19:32.335+08:00 verbose OVFTool[4088548] [Originator@6876 sub=Default] Opening disk target empty-disk2.vmdk -> 2024-08-23T11:19:32.335+08:00 error OVFTool[4088548] [Originator@6876 sub=Default] Error on read, error: -1 -> 2024-08-23T11:19:32.336+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Exception thrown: N5boost16exception_detail10clone_implINS_17unknown_exceptionEEE(std::exception) -> 2024-08-23T11:19:32.337+08:00 verbose OVFTool[4088187] [Originator@6876 sub=Default] Backtrace: -> --> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-15722219, tag: OVFTool, cpu: x86_64, os: linux, buildType: release -> --> backtrace[00] libvmacore.so[0x003DD716] -> --> backtrace[01] libvmacore.so[0x001CF8DF]: Vmacore::System::Stacktrace::CaptureWork(unsigned int) -> --> backtrace[02] libvmacore.so[0x001B6EA9]: Vmacore::System::SystemFactory::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&) -> --> backtrace[03] libvmacore.so[0x0016CF2E]: Vmacore::Throwable::Throwable(std::string&&) -> --> backtrace[04] ovftool.bin[0x001C1F38] -> --> backtrace[05] ovftool.bin[0x002008D5] -> --> backtrace[06] ovftool.bin[0x00129EF0] -> --> backtrace[07] libc.so.6[0x00044E50] -> --> backtrace[08] libc.so.6[0x00044EFC] -> --> backtrace[09] ovftool.bin[0x00132D21] -> --> [backtrace end] -> ``` - -the log file: -[test.log](/uploads/174db2ace468bd9f0ec3ab14de524217/test.log) -Steps to reproduce: -1. create empty vmdk file - -./qemu-img create -f vmdk -o adapter_type=lsilogic,subformat=streamOptimized empty.vmdk 1G - -2. add empty file info to ovf file -<File ovf:href="empty.vmdk" ovf:id="file2"/> - -3. import it to vmware workstation -Additional information: -If i write some data to empty vmdk file, it can import successfully. The reson: qemu only write metadata for empty vmdk file, but the ovftool need read more data and it cann't read more. -we can write one sector zero data after the metadata, ovftool work well. -I submitted the patch: -https://patchew.org/QEMU/20240822105237.777-1-luzhipeng@cestc.cn/ |