Red Hat Bugzilla – Bug 801813
Virtual Machine Manager doesn't recognise VMDK images itself
Last modified: 2013-10-01 17:47:00 EDT
Description of problem:
I downloaded a VMWare image and imported it using the Virtual Machine Manager. I selected the .vmdk file as storage to import.
After the wizard finished creating the virtual machine, it booted, but it failed, because it couldn't find any boot device.
Manually changing the format from "raw" to "vmdk" fixed that.
I would have expected it to realise that I have a VMDK image.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
557107 tracks auto-managing storage with libvirt, which does this type of detection and will let us do the right thing here without having to play games with file extensions or similar
*** This bug has been marked as a duplicate of bug 557107 ***