From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 42635] PCIe passthrough broken with AMD iommu after s2disk / resume Date: Tue, 3 Apr 2012 07:27:43 GMT Message-ID: <201204030727.q337Rhj0024852@bugzilla.kernel.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To: kvm@vger.kernel.org Return-path: Received: from bugzilla.kernel.org ([198.145.19.204]:37944 "EHLO bugzilla.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750865Ab2DCH1o (ORCPT ); Tue, 3 Apr 2012 03:27:44 -0400 Received: from bugzilla.kernel.org (localhost [127.0.0.1]) by bugzilla.kernel.org (8.14.5/8.14.5) with ESMTP id q337Rh6Y024853 for ; Tue, 3 Apr 2012 07:27:43 GMT In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: https://bugzilla.kernel.org/show_bug.cgi?id=42635 --- Comment #3 from Klaus Mueller 2012-04-03 07:27:43 --- Meanwhile I detected, that using the boot option iommu=pt (or additional iommu=1) shows the same problem (regardless of suspend/resume). If the VM is started after the first virsh start / virsh shutdown cycle with virsh start again, the device is dead in the VM. Host must be rebooted to get it working again. If the options iommu=pt (or additional iommu=1) are not used at all, the VM can be restarted without any problem coming up. 1. Host booted w/ iommu=pt iommu=1 2. virsh start 3. virsh shutdown 4. virsh start 5. -> Passed through device in VM is dead. 1. Host booted w/o iommu=pt iommu=1 2. virsh start 3. virsh shutdown 4. virsh start 5. -> Passed through device in VM is fine. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.