From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1828508 <1828508@bugs.launchpad.net>
Cc: fam@euphon.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1828508] [NEW] qemu-img created VMDK files lead to "Unsupported or invalid disk type 7"
Date: Wed, 15 May 2019 11:23:31 +0100 [thread overview]
Message-ID: <20190515102331.GC29507@stefanha-x1.localdomain> (raw)
In-Reply-To: <155746839267.15002.8138674450166661929.malonedeb@wampee.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
On Fri, May 10, 2019 at 06:06:32AM -0000, Jake Mikelson wrote:
> Public bug reported:
>
> Using qemu-img version 3.1.50 (v3.1.0-13607-geb2db0f7ba-dirty) on a
> Windows 10 machine.
>
> Converting a VHD to VMDK.
> qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic -p "c:\test\AppD-VM01.vmdk"
>
> I have also tried:
> qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic,hwversion=6 -p "c:\test\AppD-VM01.vmdk"
>
> Attaching the VMDK to a VM in VMware produces the following error when
> powering on.
>
> Power On virtual machine:Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
> Target: MyVM1
> vCenter Server: VCENTER
> Error Stack
> An error was received from the ESX host while powering on VM MyVM1.
> 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.
>
>
> If I do not specify the adapter type, it creates an IDE VMDK which works perfectly.
>
> ** Affects: qemu
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1828508
Which version of VMware are you running?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <1828508@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1828508] [NEW] qemu-img created VMDK files lead to "Unsupported or invalid disk type 7"
Date: Wed, 15 May 2019 10:23:31 -0000 [thread overview]
Message-ID: <20190515102331.GC29507@stefanha-x1.localdomain> (raw)
Message-ID: <20190515102331.wbwbpT3mZsEijKYKCGd_2vHWfywnkeF7xsrzwZXRfaA@z> (raw)
In-Reply-To: 155746839267.15002.8138674450166661929.malonedeb@wampee.canonical.com
On Fri, May 10, 2019 at 06:06:32AM -0000, Jake Mikelson wrote:
> Public bug reported:
>
> Using qemu-img version 3.1.50 (v3.1.0-13607-geb2db0f7ba-dirty) on a
> Windows 10 machine.
>
> Converting a VHD to VMDK.
> qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic -p "c:\test\AppD-VM01.vmdk"
>
> I have also tried:
> qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic,hwversion=6 -p "c:\test\AppD-VM01.vmdk"
>
> Attaching the VMDK to a VM in VMware produces the following error when
> powering on.
>
> Power On virtual machine:Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
> Target: MyVM1
> vCenter Server: VCENTER
> Error Stack
> An error was received from the ESX host while powering on VM MyVM1.
> 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.
>
>
> If I do not specify the adapter type, it creates an IDE VMDK which works perfectly.
>
> ** Affects: qemu
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1828508
Which version of VMware are you running?
Stefan
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828508
Title:
qemu-img created VMDK files lead to "Unsupported or invalid disk type
7"
Status in QEMU:
New
Bug description:
Using qemu-img version 3.1.50 (v3.1.0-13607-geb2db0f7ba-dirty) on a
Windows 10 machine.
Converting a VHD to VMDK.
qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic -p "c:\test\AppD-VM01.vmdk"
I have also tried:
qemu-img.exe convert "c:\test\AppD-VM01.vhd" -O vmdk -o adapter_type=buslogic,hwversion=6 -p "c:\test\AppD-VM01.vmdk"
Attaching the VMDK to a VM in VMware produces the following error when
powering on.
Power On virtual machine:Failed to open disk scsi0:1: Unsupported or invalid disk type 7. Ensure that the disk has been imported.
Target: MyVM1
vCenter Server: VCENTER
Error Stack
An error was received from the ESX host while powering on VM MyVM1.
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.
If I do not specify the adapter type, it creates an IDE VMDK which works perfectly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1828508/+subscriptions
next prev parent reply other threads:[~2019-05-15 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 6:06 [Qemu-devel] [Bug 1828508] [NEW] qemu-img created VMDK files lead to "Unsupported or invalid disk type 7" Jake Mikelson
2019-05-15 10:23 ` Stefan Hajnoczi [this message]
2019-05-15 10:23 ` Stefan Hajnoczi
2019-05-16 1:44 ` [Qemu-devel] [Bug 1828508] " Jake Mikelson
2021-04-22 6:14 ` Thomas Huth
2021-06-22 4:18 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190515102331.GC29507@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=1828508@bugs.launchpad.net \
--cc=fam@euphon.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.