Bug 647241 - Unable to install from an iSCSI volume
Summary: Unable to install from an iSCSI volume
Alias: None
Product: Fedora
Classification: Fedora
Component: python-virtinst
Version: 13
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
: 652000 669935 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-10-27 16:48 UTC by Daniel Berrangé
Modified: 2011-04-16 20:58 UTC (History)
6 users (show)

Fixed In Version: python-virtinst-0.500.6-1.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-04-16 20:55:47 UTC
Type: ---

Attachments (Terms of Use)

Description Daniel Berrangé 2010-10-27 16:48:38 UTC
Description of problem:
I attempted to install a guest from virt-manager, selecting a volume from an iSCSI storage pool. This resulted in virtinst creating XML for the disk that looked like

    <disk type='block' device='disk'>
      <driver name='qemu' type='unknown'/>
      <source dev='/dev/disk/by-path/ip-'/>
      <target dev='vda' bus='virtio'/>

Note the type='unknown'.

What's going on is that VirtualDisk.py is copying the vol/target/format/@type field from the volume XML across to the guest XML.

It should only do this for volumes that report  type=file. For volumes of type=block, the format refers to the partition table format, so the guest XML should just get  type='raw'

One quick hack change I tried in VirtualDisk.py  set_driver() is:

        elif self.vol_object:
            fmt = None
            if self.type != VirtualDisk.TYPE_BLOCK:
                fmt = _util.get_xml_path(self.vol_object.XMLDesc(0),
            if drvname == self.DRIVER_QEMU:
                drvtype = _qemu_sanitize_drvtype(self.type, fmt)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Daniel Berrangé 2010-11-10 20:18:57 UTC
*** Bug 652000 has been marked as a duplicate of this bug. ***

Comment 2 Ferry Huberts 2010-11-10 20:38:58 UTC
sorry for the duplicate, i searched for isci in libvirt...

any idea when this will be fixed? now that rhel6 is out :-)
or should I just apply that hack?

Comment 3 Daniel Berrangé 2010-11-10 20:46:58 UTC
If you have a problem with this on RHEL6 too, please file a BZ directly against RHEL6 product rather than just Fedora.

Comment 4 Ferry Huberts 2010-11-10 20:56:56 UTC
no that's not what I meant. I meant that you might have some more time now that rhel6 is out :-)
haven't tried rhel6 yet, am a bit low on subscriptions :-)

Comment 5 Cole Robinson 2010-11-17 21:06:21 UTC
Thanks for the report, fixed upstream:


Comment 6 Cole Robinson 2011-03-23 21:29:31 UTC
*** Bug 669935 has been marked as a duplicate of this bug. ***

Comment 7 Fedora Update System 2011-03-31 14:13:04 UTC
python-virtinst-0.500.6-1.fc14 has been submitted as an update for Fedora 14.

Comment 8 Fedora Update System 2011-03-31 14:15:59 UTC
python-virtinst-0.500.4-2.fc13 has been submitted as an update for Fedora 13.

Comment 9 Fedora Update System 2011-04-01 18:26:41 UTC
Package python-virtinst-0.500.4-2.fc13:
* should fix your issue,
* was pushed to the Fedora 13 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-virtinst-0.500.4-2.fc13'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2011-04-16 20:55:12 UTC
python-virtinst-0.500.4-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2011-04-16 20:57:57 UTC
python-virtinst-0.500.6-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.