Bug 434871 - adding scsi disk to qemu guest fails
adding scsi disk to qemu guest fails
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-25 17:15 EST by Cole Robinson
Modified: 2008-11-26 10:34 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-26 10:34:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Cole Robinson 2008-02-25 17:15:35 EST
Adding a scsi disk to a qemu based disk fails with the following error:

nable to complete install: 'Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/addhardware.py", line 513, in add_device
  File "/usr/share/virt-manager/virtManager/domain.py", line 724, in add_device
  File "/usr/share/virt-manager/virtManager/connection.py", line 446, in
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 601, in defineXML
    if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
libvirtError: virDomainDefineXML() failed Invalid harddisk device name: sda
Comment 1 Cole Robinson 2008-02-25 17:16:37 EST
Qemu guests can't seem to handle sd* disks, so I committed a patch to disable
the scsi disk option for non-xen hvm guests:

Comment 2 Daniel Berrange 2008-02-25 17:29:22 EST
Non-Xen based QEMU can handle SCSI disks since QEMU 0.9.1. It is simply libvirt
is not up2date enough to support it. Rather than disabling it in virt-manager we
should add SCSI support to libvirt.
Comment 3 Bug Zapper 2008-11-26 04:56:16 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 4 Cole Robinson 2008-11-26 10:34:56 EST
This particular error is fixed in F9, but won't be backported to F8. So, closing as CURRENTRELEASE.

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