Bug 795572 - Windows7 VM fails to boot when using spice due to sound hw issue
Summary: Windows7 VM fails to boot when using spice due to sound hw issue
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 16
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: 2012-02-20 23:11 UTC by drago01
Modified: 2012-02-28 21:17 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 21:17:34 UTC
Type: ---


Attachments (Terms of Use)
VM XML (2.29 KB, text/plain)
2012-02-20 23:11 UTC, drago01
no flags Details
qemu log (99.02 KB, text/plain)
2012-02-20 23:12 UTC, drago01
no flags Details

Description drago01 2012-02-20 23:11:46 UTC
Created attachment 564537 [details]
VM XML

After switching my Windows7 VM from VNC to spice I get:

---------
console log output: char device redirected to /dev/pts/0
do_spice_init: starting 0.10.1
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
qemu-kvm: -device intel-hda,id=sound0,bus=pci.0,addr=0x4: PCI: slot 4 function 0 not available for intel-hda, in use by virtio-blk-pci
qemu-kvm: -device intel-hda,id=sound0,bus=pci.0,addr=0x4: Device 'intel-hda' could not be initialized
---------

When trying to boot it. I am using libvirt-0.9.6-4.fc16.x86_64.

The XML of the VM is attached.

Comment 1 drago01 2012-02-20 23:12:16 UTC
Created attachment 564538 [details]
qemu log

Comment 2 drago01 2012-02-21 14:05:33 UTC
Switching the sound device to use a different pci-slot by hand seems to fix it i.e now it says:

<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>

Comment 3 Cole Robinson 2012-02-28 21:17:34 UTC
Ah I think I know the problem. Looks like you changed the disk bus from ide to virtio in virt-manager UI, which wasn't correctly unsetting disk target and address type. Upstream virt-manager properly warns about this case, and latest virt-manager in fedora should properly make the change. If you have any other guests similarly affected, you should be able to change disk bus from virtio->ide->virtio in latest virt-manager and it will fix them.

Closing as CURRENTRELEASE virt-manager


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