From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [BUG] Hypervisor 4.3 fails to init Marvel SATA III when Vt-d is enabled in the BIOS (failed to IDENTIFY) Date: Tue, 15 Apr 2014 10:38:43 +0100 Message-ID: <534D1A430200007800008E34@nat28.tlf.novell.com> References: <006101cf585b$4ec18f90$ec44aeb0$@geekshake.com> <534CFE6D0200007800008CFE@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Rodger McIntosh , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >>> On 15.04.14 at 10:59, wrote: > I suppose there's no way we could add devices like this to a "quirks" > file, so that users don't have to figure this out on their own? We surely could, but I'd prefer such a list to not get added IDs one by one, but instead just the full list of affected ones. Which would require someone to collect such a list. And of course it would need to be clarified whether for some of the affected IDs revisions exist that have/don't have the issue. Jan