Public bug reported:

A restarted kvm client with a passthough pci device does not work
anymore (properly) with that device. The device does not seem to be re-
set properly.

If the KVM host is re-started the client one time starts properly with a
correctly functioning pci device, when the client is re-started (without
re-starting the kvm host) the pci device is not working properly.

Seen on device:
   USB device with linux client (USB controller: ASMedia Technology Inc. 
ASM1042 SuperSpeed USB Host Controller)
  The device is implemented with MSI-X, as a test a keyboard is connected.

First boot client (on fresh start of KVM host):
The client is presented the pci USB device (usb 2.0 and usb 3.0) and the 
keyboard is presented as well. The keyboard properly works.

Reboot:
The client is presented the pci USB device (usb 2.0 and usb 3.0), but no 
keyboard is presented (it is plugged in). Disconnecting and re-connecting the 
usb keyboard is not helping. Unregistering and re-registering with it's driver 
(xhci_hcd) did not help. Trying to reset through "echo 1 > reset" within 
/sys/devices/ did not help. Trying to use pci-config -s 03:00.0 -S and 
pci-config -s 03:00.0 -W did not help.

I've been looking for a solution to get this working properly, but
failed so far to find a solution.

package used to start the client: libvirt (virsh and virt-manager)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: kvm 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.2
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Thu Oct 11 20:03:16 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic 
root=UUID=2583ca5d-0a8a-46bc-b0c3-d8468dc2a421 ro quiet splash iommu=pt 
vt.handoff=7
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1102
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

** Affects: qemu-kvm (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065628

Title:
  pci device not reset (passthrough)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to