On Wed, 2011-09-21 at 10:23 -0700, Erik Flister wrote:
> i posted this to virt-tools but got no replies, hoping you guys can help me. :)
>
> >>>AMD
> phenom II X6 1075T proc
> >>>ASUS M4A87TD mobo
Google says this is an AMD 870 chipset, so you do not have AMD IOMMU
(AMD-Vi) support :(
> >>>> lspci
> >>>
> >>>02:06.0 Unassigned class [ff00]: National Instruments PCI-6110
> >>>02:07.0 Serial controller: NetMos Technology PCI 9865 Multi-I/O Controller
> >>>02:07.1 Serial controller: NetMos Technology PCI 9865 Multi-I/O Controller
> >>>02:07.2 Parallel controller: NetMos Technology PCI 9865 Multi-I/O Controller
> >>>
> >>>> lspci -n
> >>>
> >>>02:06.0 ff00: 1093:14e0
> >>>02:07.0 0700: 9710:9865
> >>>02:07.1 0700: 9710:9865
> >>>02:07.2 0701: 9710:9865
> >>>
> >>>> virsh nodedev-list | grep pci
> >>>
> >>>pci_0000_02_06_0
> >>>pci_0000_02_07_0
> >>>pci_0000_02_07_1
> >>>pci_0000_02_07_2
> >>>
> >>>> sudo virsh
> nodedev-dettach
> pci_0000_02_06_0
> >>>Device pci_0000_02_06_0 dettached
> >>>
> >>>
> >>>but then, after adding it to the guest and trying to boot it, i get:
> >>>
> >>>Error starting domain: this function is not supported by the
> >>>connection driver: Unable to reset PCI device 0000:02:06.0: this
> >>>function is not supported by the connection driver: Active
> >>>0000:02:07.0 devices on bus with 0000:02:06.0, not doing bus reset
This is probably telling you that the device you want to assign doesn't
support a reset mechanism (FLR or D3hot), so it wants to do a secondary
bus reset, but there are other devices on the same bus.
> >>>if i disable the other devices on bus 02 and add them to the guest:
> >>>> sudo virsh nodedev-dettach pci_0000_02_07_0
> >>>Device pci_0000_02_07_0 dettached
> >>>
> >>>> sudo virsh nodedev-dettach pci_0000_02_07_1
> >>>Device pci_0000_02_07_1 dettached
> >>>
> >>>> sudo virsh nodedev-dettach pci_0000_02_07_2
> >>>Device pci_0000_02_07_2 dettached
> >>>
> >>>i then get this error on booting the guest (but with the same stack
> >>>trace as above):
> >>>
> >>>Error starting domain: cannot send monitor command
> >>>'{"execute":"qmp_capabilities"}': Connection reset by peer
> >>>
> >>>and then networking fails on the host until i reboot, and fedora won't
> >>>even shutdown all the way (i have to do a hard reboot by holding down
> >>>the power button).
> >>>
> >>>any idea how i can fix this? why isn't detaching the device
> >>>automatically done when it is added to the guest? even if i get this
> >>>working, it seems i will
> have to detach stuff every time i reboot the
> >>>host? finally, in this case, i actually do want to give everything on
> >>>bus 02 to the guest, but what if i didn't?
Getting it working seems like it's going to require new hardware since
you don't have a device assignment capable IOMMU. Thanks,
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
