Bug 768367 - Device 'sb16' can't go on a PCI bus
Summary: Device 'sb16' can't go on a PCI bus
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-16 13:15 UTC by Jaromír Cápík
Modified: 2016-02-01 01:55 UTC (History)
8 users (show)

Fixed In Version: virt-manager-0.9.1-1.fc15
Clone Of:
Environment:
Last Closed: 2012-02-14 08:56:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jaromír Cápík 2011-12-16 13:15:02 UTC
Description of problem:
When I select 'sb16' as soundcard in the machine settings and start the machine, the following message appears:

qemu-kvm: -device sb16,id=sound0,bus=pci.0,addr=0x4: Device 'sb16' can't go on a PCI bus


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/engine.py", line 959, in asyncfunc
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1128, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 330, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: vnitřní chyba Process exited while reading console log output: char device redirected to /dev/pts/2
qemu-kvm: -device sb16,id=sound0,bus=pci.0,addr=0x4: Device 'sb16' can't go on a PCI bus


Version-Release number of selected component (if applicable):
virt-manager-0.8.7-6.fc15.noarch
libvirt-0.8.8-7.fc15.x86_64

How reproducible:
always
  
Actual results:
1.) Error message displayed.
2.) Machine doesn't start.

Expected results:
1.) No errors.
2.) Machine starts.
3.) 'sb16' emulation works correctly.

Comment 1 Cole Robinson 2012-01-29 20:46:32 UTC
Fixed upstream:

http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=680f44ec93086ac8ecf688852fd63193da717932

You can fix the existing device by changing the device model to something else, like es1370, clicking apply, changing back to sb16, clicking apply again.

Comment 2 Fedora Update System 2012-02-01 18:23:51 UTC
virt-manager-0.9.1-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/virt-manager-0.9.1-1.fc15

Comment 3 Fedora Update System 2012-02-02 17:23:18 UTC
Package virt-manager-0.9.1-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 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-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1173/virt-manager-0.9.1-1.fc15
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-02-14 08:56:11 UTC
virt-manager-0.9.1-1.fc15 has been pushed to the Fedora 15 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.