Bug 761300
| Summary: | virt-manager: importing a vdi image should just work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Scott Tsai <scottt.tw> | ||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | berrange, crobinso, dougsland, dpierce, hbrock, jforbes, moez.roy, orcalon, virt-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | virt-manager-0.9.1-2.fc15 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-17 23:53:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Scott Tsai
2011-12-08 00:39:43 UTC
> file=/home/scottt/work/openrisc/OpenRISC_Ubuntu_2011-11-28.vdi,if=none,id=drive-virtio-disk0,format=raw
This bit is telling QEMU that the .vdi file is a raw image. I'm guessing from the file extension that it is in fact *NOT* a raw image, in which case you'd need to tell virt-manager what the format is.
(In reply to comment #1) > you'd need to tell virt-manager what the format is. I have two problems with this: 1. When creating a new VM from an existing disk image, virt-manager either should have either detected the disk format as correctly as "vdi" or allowed me to specify the format. 2. In the virt-manager GUI, the "Disk" -> "Advanced options" -> "Storage format" drop down doesn't offer the "vdi" format. (It offers "raw", "qcow2", "vmdk") I think creating VM's from existing VirtualBox disk images is worth supporting well because: 1. Upstream projects, like OpenRISC, distributes their Linux software in VM images partially to provide a ready for use configuration but also to side step the hardware compatibility issues of running Linux on real hardware. 2. VirtualBox being freely downloadable for all the major desktop OSes makes it a popular choice. That first issue of detecting the image format is a bit complex. There are plans to fix virt-manager to do this, but it's being tracked elsewhere: https://bugzilla.redhat.com/show_bug.cgi?id=557107 VDI not being in the default format list is now fixed upstream: http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=265e04205e4766f459d4ced516dbd784cf2ca57f But you can also manually enter 'vdi' in the combo box entry there and it should work in the interim. virt-manager-0.9.1-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/virt-manager-0.9.1-2.fc16 virt-manager-0.9.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/virt-manager-0.9.1-2.fc15 Package virt-manager-0.9.1-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virt-manager-0.9.1-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1671/virt-manager-0.9.1-2.fc16 then log in and leave karma (feedback). virt-manager-0.9.1-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. virt-manager-0.9.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. There is still a problem.
If I try to create a new VM from a .vdi image with 'customize configuration before install' checked, I can choose for Disk 1 under 'advanced options' for the vdi storage format.
Then 'Begin Installation', which ends in the following error:
Unable to complete install: 'internal error unknown disk format 'vdi' for /var/lib/libvirt/LedgerSMB-1.3/LedgerSMB-1.3.vdi'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1911, in do_install
guest.start_install(False, meter=meter)
File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1239, in start_install
noboot)
File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1307, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2077, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error unknown disk format 'vdi' for /var/lib/libvirt/LedgerSMB-1.3/LedgerSMB-1.3.vdi
If I try to setup the VM without the vdi storage format chosen (no 'customize configuration before install' checked), after creation the VM starts, but fails to mount its root partition.
Fedora 16
virt-manager-0.9.1-2.fc16.noarch
libvirt-0.9.6-5.fc16.x86_64
qemu-kvm-0.15.1
|